"Movement" = event killer

[thelegendaryX]

Another shot in the dark from yours truly.

I'm trying to make it to where my character moves to another part of a building (castle) in the big middle of an "event". I know it won't read any code from one event after the "Movement" command, and that "Warp" isn't very tough to work around. But is there any way I can make a script keep truckin along after moving to another part of the screen?

I even tried placing a "Touch" event right where I set him to move to, but it just ignores it until I move the character.

(Yes, I know I can just make a second castle that looks the exact same and fake it. But I'm also trying to save space.)

[Lausen]

Re: "Movement" = event killer

Before the movment command have an add mode command. Make that second mode be auto. Anything you want to happen after the move play it in the second mode. This spares you from having to use two events.

[thelegendaryX]

Re: "Movement" = event killer

Ok, but how do I switch it to that second mode so it'll automatically play after the move? Or are you saying that I can do it this way..

1. Add Mode
2. Modify Mode
3. Movement

..and it won't kick off the newly added auto-event before movement?

[Lausen]

Re: "Movement" = event killer

Kind of. You don't need both Add Mode and Modify Mode. It should look something like this.

Name the event whatever.
Mode 1/2

1. blah...
2. blah...
3. etc... until the switch.
4. Add mode to 2/2
5. Movement

Mode 2/2 (Auto)
1. blah
2. blah

They will play smoothly. You won't even notice the switch.

[thelegendaryX]

Re: "Movement" = event killer

Okay, I'll try that. Thanks Lausen!

[thelegendaryX]

Re: "Movement" = event killer

I got it. I never could get "Add Mode" started, though, because it didn't give me a place to type the event code? So I used "Modify Mode" instead.

You were right about not noticing the change. That's what I like. I can't stand having the screen "blink" as it does when you change something. (I think "Display On" is my biggest obstacle)