Autorun events don't work after map transition?

Allow me to explain. Basically, I had two auto-run events set up in different maps. one transferred over to the other. They used to work fine, but now, depending on what I change, the second auto-run either doesn't go at all, or it just loops the first page over and over and over again. Here are the related event pages:





So, any ideas? Do you need to know more?

Thanks in advance for any help I receive. :)

Put the switch before the change BGM. Or even before the transfer.


Events don't run across maps.

If what Shaz said doesn't fix the problem (or all of the problems), there may be something else going on on the tabs that you didn't post of the second event. If you still have a problem we may need to see those to figure it out.

Shaz's solution didn't work. The second event still refuses to start up. It's like it doesn't even register that it's an auto run event.

What's on the other tabs of the second event? What are the conditions?


When deciding which page to make active, the engine starts at the highest-numbered tab and works its way back to 1. If any of those have conditions that are met (or no conditions at all), THEY will be active, not tab 1.

Generally I almost never have a tab without a condition unless its a constant, such as a random NPC or a shop. Same here.. My pages are ordered chronologically of when they are supposed to happen over the game, and that's always worked for me in the past. As for what happens in the pages, it's basically just dialogue, sound effects and screen flashes. (It's a pretty long page, so...)

It's still better if you show us each of those tabs so we could help you determine what the problem was...

Okay, here you are. just so you know, the first of these images is cut off about midway-ish. Also, tabs 4 and 6 are blank, save for their conditions. they are also action buttons, so they likely aren't the issue, I would think. Tab five gets cut off partway through as well, but it is pretty similar to the first image.

Are you sure none of those other tabs have their conditions already ON? Because as Shaz said, event pages are processed from the highest numbered page so if any of those higher pages have their conditions already ON, that would cause a problem.


Also since Page 2 is autorun and supposed to run right after the first page, why not simply do everything on page 1?


And lastly, do you have any script that modifies how event pages work?

The trigger doesn't matter. The condition does. It doesn't need to be an autorun event to be active. If your action button page has a higher number than your autorun page and your action button page's conditions are met, it will be active - whether there are commands or not.


So play to the new page, hit F9 to debug, and see which, if any, of those switches conditioning pages 2-6 are turned on.

So, for some reason... three other switches are on when they shouldn't at the start. Why? I don't know. I honestly have no clue. They shouldn't be, as these are literally the first things to happen in the game. This is the intro.

You might have some script using those 3 switches or something... or you had an event that begins earlier that turns them on that you used for testing purposes. Or u are using a saved file where those switches are already ON

Yeah, I bet you have installed one or more scripts and not gone through and set them up properly. Several of them use switches and/or variables, and you are meant to allocate unique switches/variables for their use - naming them in your switch/variable list so they don't get accidentally used for something else, and then editing the script to tell it which ones you've allocated.


Yami's Overlay map is one that does this, and people commonly have this issue because they haven't taken the time to read/understand the instructions and set it up. But there are many more.


On the bright side, it's good that you discovered this NOW, as it would have had you pulling your hair out if you'd gotten much further into development and it started happening.

I feel like a dumb. My overlay mapping script was causing it. >.< I totally forgot I had that (Experimented with it, never used it). Well, whatever the case, the issue is fixed. Thanks!