Main Menu

[RESOLVED] "Wait for move's completion" not working correctly!

Started by Mjustin, September 01, 2008, 10:49:33 PM

0 Members and 1 Guest are viewing this topic.

Mjustin

For some reason when I put a "wait for move's completion" command in my events it won't work if the move route is more than one move long. It stopped working all of a sudden for no apparent reason.

I was making an Autorun event that looks like this:

@>Set move route: Player
:              : $>Move up
:              : $>1 Step Backward
@>Show Animation: This event, [Axe]
@>Wait for Move's Completion


and repeat.

This worked perfectly, and I was very happy with the result. I then went on adding more things to my game. I added Slipknot's Letter by Letter Message Window script, and the event still worked perfectly when I tested it. Then I added some dialogue in another map and that's when my events started going haywire. Now I have to make the event like this:

@>Set move route: Player
:              : $>Move up
@>Show Animation: This event, [Axe]
@>Wait for Move's Completion
@>Set move route: Player
:              : $>1 Step Backward
@>Wait for Move's Completion


and repeat. Anyone know why? I didn't add any extra scripts, and the event started going all screwy when I added a big event on an entirely different map. Thanks!

Mjustin

Does no one want to help me? :'( Or does no one know how to fix my problem? ???

modern algebra

It's likely because it is a parallel process/autorun (maybe) event, and the event is rerunning itself, causing the character to repeat the first action continuously. Well, that's the usual problem with Move Routes - you didn't actually say what was going wrong with your events, so any help I can offer is based on a guess that the problem is that the characters are repeating the first entry of the move event. If that's not what is happening, then please give some more detail.

And I put maybe next to autorun because it's been a while since I've used RMXP and so I don't remember if the problem happens with autorun as well or not.

Mjustin

You were right; it was a parallel process event and I fixed it. Thanks!