MASON_WHEELER'S PROFILE

After a bunch of testing and trying to narrow down and isolate different factors, it seems the the thing that makes the difference is the page's "Trigger" attribute: its event script will only be aborted if it's a Parallel Process.

Still not sure where the relevant code for that is, but that appears to be the determining factor.

No, Kory, you still don't understand.

I'm not trying to change the behavior here. I'm trying to figure out what's causing it.

author=kory_toombs
This is not scripting, this is event processing.

You tinted the screen prior to transferring.
You want the tint to return to normal?

No.

I'm not 100% sure what your trying to do, so this is just an assumption.

I'm trying to figure out why in the one case, changing active pages while the event is in progress causes the event processing to abort, and in the other case, it doesn't and the whole thing plays through to completion. If the behavior was consistent, I'd expect the teleport to never occur, because the Wait that gets called in the Tint operation yields control back to whatever processing is causing the other event script to abort. But the teleport does occur, and I'd like to understand why we get inconsistent behavior between the two scenarios.

(This was originally posted as a 2k question, but someone suggested looking at the VX Ace implementation, and I discovered the behavior is the same. Unfortunately, I can't find the reason for it! I'm trying to reverse-engineer a particularly annoying discrepancy, and any help tracking down what's going on would be greatly appreciated.)

I've got two scenarios here with what seems to be contradictory behavior, and I'm trying to figure out how it works.

First:

Two events on the map. One is a parallel process, that looks like this:

Page 1:
Conditions: none
Script:
Loop:
Play SFX(whatever)
Wait(30)
Loop End

Page 2:
Conditions: Switch 1 is ON
Script: none


The second is an object that's activated on player touch, that turns Switch 1 on. When I activate this event, the sound loop stops playing, suggesting that when the active page on the second event changed, it aborted the script it was currently playing. So far, so good.

Second scenario:

Two maps. First map has an event on it that activates on player touch.

Page 1:
Conditions: none
Script:
Set Switch 1 ON
Screen Tint: Sepia (60 frames)
Teleport to Map 2
Image: some image

Page 2:
Conditions: Switch 1 is ON
Script: none
Image: none

When you hit the event, it vanishes immediately, showing that the active page changed right away. And yet, after the fade, the teleport takes place, which means that the script did not abort when the active page changed.

I can't find anything in the code to account for this discrepancy. The implementation of the Screen Tint command (command_223 in Game_Interpreter) calls the same wait() method that the Wait command (command_230) does, and there's nothing particularly special in the implementation of the loop (command_112 and command_413).

Does anyone know what it is that causes a script in progress to abort in some cases but not others when the event it's on changes its active page?

author=Yukinose
That's an interesting project. Is there a reason you're not examining VXA's or MV's codebase? Perhaps they'd give insight into how RM parses through the event commands on an event page.

That's a good idea. I'll have a look.