RESIDENT EVIL SHOOTING SYSTEM FATAL SCRIPT ERROR (GAME HANGS IN BALANCE)

so dramatic

Change the line it references (Line 58 in Interpreter 2) to read just

enabled = $game_temp.hit

(Personally, I changed it as follows:
enabled = $game_temp.hit #and $game_map.events.face
in the event I figured out what that function was supposed to do and could correct it, but I haven't found anywhere for that yet.)

As I don't know the intention of the original developer, I don't know what that particular function does so I can't correct it to their original ideas (I expect it took into account which way the zombie was facing to determine if you actually hit or not). It appears to work at that point, but I don't know if the knife is actually able to kill a zombie because they kill me faster than the knife lets me attack (but the game lets you keep playing after a knife hit with that change).

author=bulmabriefs144
Get rid of the script. Period. You could do a better one with coding and basic knowledge of variables, that wouldn't cause any error.

Also, knife attack is a short range attack. You're building this on what, VX Ace (I didn't download, because I didn't want crap on my computer)? Make a Touch event (with a If Action is used condition) for each monster if equipped with the knife. Make a simple battle animation, and change the sprite of the character to an attack pose. If you don't use the action in time, the attack misses and the enemy hurts you.

And you wonder why you got rejected when rather than fixing things "I'm just going to recommend people in the game not to use the knife as it will rarely hit." Someone will use it anyway. Fixing the problem, unless you've hired a bugtester, is your responsibility.

Why are you acting so hostile? Seriously fixing script errors with event systems is only a thing you do in rm2k(3) not in the later versions of the makers. Next to that not everybody knows basic variables and such. I can understand when somebody downloads a script or system he expect it to work without bugs.

author=obsorber
She's got a good point though. However not all of us are competent scripters or event(ers)

not all of us are competent scripters or event(ers)...yet. Scripting and eventing are simply skills you learn and can learn. There isn't any, say, genetic predestination that specifies that Person A is a scripter (it's in his DNA!) and Person B cannot script.

If there is a game crashing bug, you should really fix it.

The script was purposefully designed to use the knife only as a last resort - it's clear from looking at the script it's designed to be difficult to fight with because hey, it's like a six inch blade being used against brain-hungry zombies. It's not meant to hit as often, or to be used as such - only when you get trapped and have no other option (and you'll die if you don't get one or two lucky hits in).

I actually think that, on average, the change I mentioned to the script would increase the average hit rate of the knife, and even then it's still 'abyssmal' (in testing, one in three or one in four button presses result in a hit - and that seems to be because the animation is actually taken into account for how often it counts button presses and when it 'hits'; if the zombie moved during the animation, it won't hit, because the zombie isn't there anymore).

Also, people need to damn well learn to read - it says right in the first post what maker is being used. There's no game crashing bug anymore, just design on a weapon that could be a lot better but makes sense being as crappy as it is. That said, the original script is rather clunky in play - I'm not sure why the original scripter chose the keys they did - and could majorly use an update to fix bugs - it's about three years without one now.

(Also, the damned thing contains so, so much terrible commenting and terrible conventions that it's nearly impossible to trace through it and fix stuff without knowing before hand what's going on...)

I'm not saying that's no reason to try but there isn't anything wrong with asking for help or for some sense of direction.

author=Trujin
Why are you acting so hostile? Seriously fixing script errors with event systems is only a thing you do in rm2k(3) not in the later versions of the makers. Next to that not everybody knows basic variables and such. I can understand when somebody downloads a script or system he expect it to work without bugs.

I beg alot off of plugins from people. Mainly Cherry. But they're usually things that either:

1. I know would take thousands of lines of code due to the fact that they've gotta be implemented through the somewhat flawed handlers of rpgmaker. I wanna get the same effect with a simple comment.
2. Rpgmaker won't do under normal circumstances, even though it has the technical power (such as system menus)
3. Is not actually part of rpgmaker (like pure C++ code, using arrays or file streams)

A good game (I don't care if it's 2k3, or vxace, or whatever people use (if any) after vxace) uses a combination of at least basic understanding of coding, and the ability to script.

OP appears to have neither. This is still forgivable.

author=OP
Just tried out what you said thanks never mind about the removing stuff i'm just going to recommend people in the game not to use the knife as it will rarely hit

Say what, now? It sounded like rather than even giving an attempt to fix the problem, he acted like the knife rarely hits and that's the problem.

Having sucky skills is forgivable. Lying and covering up a fatal error is not. Suppose I were to decide to play his game, and it was a much worse error that fried my computer. I was out of ammo, and needed to use the knife.



"But I warned you that the knife rarely hits." Sorry, but might there be a case for speaking about personal responsibility? If you can't bugtest, hire someone who can.

Also, seriously, knife code does not need much in variables, scripts or anything of the sort.

Settinh the monster hp.

The monster itself.

I've looked at VX Ace or whatever system code, I'm fairly certain that they have something similar. And before anyone says, "but monsters need to be right next to you," I've attacked monsters right as they were stepping into the adjacent spot (so it's actually closer to 1 1/2 spaces, which is plenty for a knife). What I'm advising him to do is simply cut out the knife part, since it's simple enough that he can figure it out.

Politeness does no good if it doesn't help people learn and grow, or if it disguises things that should be said (if even one girl I tried to date told me, "I'm still in love with X" before I got too close, I'd be a ton less screwed up). Something that should be said, I have said, it's extremely poor form to lie about mistakes to users.

"I'm currently fixing it, don't use it" is okay. Not knowing about it is okay. Knowing and acting like nothing is wrong... ummmm... not so much.

author=kentona
If there is a game crashing bug, you should really fix it.

Yes!