[RM2K] [SCRIPTING] WHAT CAUSES AN EVENT SCRIPT IN PROGRESS TO CANCEL AND CHANGE PAGES?

whatever the exact reason is, it means RM does the "should this event change pages?" check at both the end of an event page, and also at the end of a loop's body.

author=Mason_Wheeler
"Checking page conditions at the end of the loop body" is one thing I actually know for sure is not true, because in this particular script, the end of the loop body is never hit. All paths end in a GOTO that sends execution back up to the top of the loop. (Don't ask why; I have no idea.)

For reasons I can never seem to remember for more than a day, GOTO is preferable in rm2k(3) over the Loop command, so for whatever you're referencing it makes perfect sense that it used GOTO.

As for the actual topic, I've never looked into this question before, but it would make sense that "checking page conditions" occurs at the end of the page, loop, or the GOTO command. If you wanted to check, just throw in a message box or event move after a switch command to see what still triggers when.

First of all, I wouldn't use loops. There always seems to be something screwy with them. You can get the same results from

label 1
code you want to loop
wait 0, or above
jump to label 1

It gives you much more control. You can put in condition branches to break out of the loop or even jump to other loops by creating label 2, and putting a jump to label 2 in a branch.

(to break out of this loop)
label 1
code you want to loop
wait 0, or above
IF (switch0001 is ON)
\\jump to label 100
jump to label 1
label 100

However, why do you have a page 2 on an event where you want a loop to keep going on page 1? If the loop is meant to keep going, then it should be on it's own event and that page 2 on a different event. Only 1 page of an event can process at one time, and the page on the right will take priority. That seems like it's working as designed.

When you activate a switch to enable another page or event, the code will continue to process to the end, then not repeat. Which is why you can teleport after turning on the switch. I think after you teleport, if you go to another map, the event on the previous map that started the teleport will stop processing(not 100% sure on this). In that case you could do something like, use a common event so it doesn't matter which map you're on and where you teleport to.

I usually don't put anything after a teleport, then on the destination map create an autorun event to finish up whatever code needs to be there, then turn itself off when done(or do a call of a common event). But it all depends on the situation, how other events are set up, and whatever nuances comes up from the engine.

Oh, yeah, you won't get many answers here. There's maybe 3 people I can think of that could help you. Kazesui, Wolfcoder and Cherry. I think Pepsi_Otaku knows a bit from his work with dynRPG, but very few people know how the engine works deep inside. Maybe a few other users who I've seen discussing the nitty gritty of the engine. Others who are making engines that run RM games. OpenRPG I think is one.

I would recommend that you explain your goal when asking these kinds of questions, to avoid getting unhelpful responses. I wouldn't have bothered to reply since I don't know why code works the way it does. Just how to work with it so it doesn't break, heh.