Move Route Troubles.

[FishStickMystic]

And here I thought move routes were simple... sigh.

Here's my problem. I need this kid to leave right after you talk to him. However, all he does is look right and stay still. I have no idea why this is not working.

Here's the "main" event that makes everything go:

Spoiler: Thing

• After you step on a 1 tag, the short exchange is supposed to begin. The variables are called boulder because I'm just recycling.
• Everything up to the "kid goes" switch works.

Here's the kid's event:

Spoiler: Kid

• Ignore page 4. I got rid of it and the problem occurs with and without it. It was just an extra I didn't need.
• As you can see, he's on 'Through,' so nothing should make him stop.
• The 'RIP' switch on page 1 just makes him pop up after a previous cutscene.

Here's the event that controls the kid's movement:

Spoiler: Movement

• Is the move route too long or something?

I don't think it's because of the number of parallel processes since I had much more running at one earlier point.
And because I am using Yanfly's Move Restrict Region script, I made sure to leave the restrict tags out of the kid's way.
Also, there are no other parallel processes actively going, unless Erase Event means nothing when tinting the screen, heh...

So... what am I doing wrong? Is there a simpler way of doing this?

Thanks!

 

[TheoAllen]

I usually hate diagnosing a long eventing, but ...

You have move route with parallel process, and you didn't put wait for completion there, nor an event command to exterminate it either by erasing the event, or switch it to different page that is not from event route, I know you put switch ON, but back at the first reason.

So, I guess it's because the parallel process keep looping it without a thing that stops it.

 

[FishStickMystic]

I can't believe.
Moving that Switch On.
Out of the move route.
Fixed all of this.
And I never figured, "Maybe doing that would be a bad idea."

Sigh... Thanks @TheoAllen . Sorry for wasting your time. e_e

 

[TheoAllen]

No prob. I ran into similar problem before lol

 

[Andar]

@S0NICFan111
An other big mistake is splitting the cutscenes over different events and event pages controlled by switches. You should never use such a structure unless it is something esotheric that you know exactly why to use.

Regulär cutscenes should have one controlling event with one page containing every command. The NPC placeholder should always be action button and never contain a single command, neither autonomous movement nor in the content area.
Instead, the main controlling event should remotely control the NPC by targeted move route - you wouldn't need a single switch that way.

 

[Kes]

[closed]IgnoreMe[/closed]