My event won't run.

[Mr. Detective]

Hi guys,

For some reason, my autorun event won't run at all, even though I already set the switch on. I am not sure what I missed, since all the other events are similar to this and they work just fine.

These are two different events.

 

[StoneLegendEntertainment]

Where is Self Switch A on?

 

[servantb7]

I noticed that both events have another page after the one you showed. Is it possible the conditions for the last page is fulfilled so it never even checks for the next-to-last page?

 

[Mr. Detective]

There is nothing on the two next pages.

 

[StoneLegendEntertainment]

Remove the Switch of page 3 and 4 and try that.

 

[Mr. Detective]

Nope. Still doesn't work.

 

[Andar]

Please provide full data - which means screenshots of the beginning of those events, and screenshots on the first pages, and screenshots of the events that turn ON the switch 18 that is needed to activate the events.


One more tip: change the grafics of the events, so that every event page has a different picture, and then check which page is really active by comparing which picture is shown ingame.

 

[Mr. Detective]

After this, the player will be transported to another map with the other events. Then, after a conversation, the player will be transported back to the previous map for this event to occur.

Normally, this is only an event that tells the players they can go in this room.

Did that help?

 

[servantb7]

In your first event (the one with 4 pages) you use self-switch A for two different things, and it is making it so that page 4 always comes up instead of page 3.  You should activate Self-switch B on page 3 and have self-switch B as the condition on page 4 (instead of self-switch A).

 

[Andar]

Did that help?

Only partially, because you still did not give the full event...
servantb7 already pointed out the logic error in the first event - because that event's self-switch A is already ON when the second condition (switch 19;going home) is triggered, the page 3 will never be executed.


But we still need to see the full content to understand the rest of your logic.


In the screenshots of the first and third page of the first event, and in the screenshot of the second page of the second event, the beginning of the content is missing - you'll need several screenshots with the scrollbar scrolled to different positions to show us the entire content instead of only the last lines.


We still don't see the code where switch 17 is turned ON...

 

[Mr. Detective]

In your first event (the one with 4 pages) you use self-switch A for two different things, and it is making it so that page 4 always comes up instead of page 3.  You should activate Self-switch B on page 3 and have self-switch B as the condition on page 4 (instead of self-switch A).

Thanks, it works now. Though, I still don't quite understand how the other ones worked, but this one didn't. I thought if I used a new switch, it'll be fine. So, the next time I use this same event for another cutscene, I would have to turn on self-switch C?

That's not right.

Only partially, because you still did not give the full event...

servantb7 already pointed out the logic error in the first event - because that event's self-switch A is already ON when the second condition (switch 19;going home) is triggered, the page 3 will never be executed.

But we still need to see the full content to understand the rest of your logic.

In the screenshots of the first and third page of the first event, and in the screenshot of the second page of the second event, the beginning of the content is missing - you'll need several screenshots with the scrollbar scrolled to different positions to show us the entire content instead of only the last lines.

We still don't see the code where switch 17 is turned ON...

Switch 17 is on another map, and the event on page 1 works, so there's no need to show that. And the beginning is just a bunch of dialogue, nothing more.

 

[servantb7]

Glad it works In the future just remember that self-switches stay on indefinitely, so yes, as a general rule you shouldn't use the same self-switch as a condition for more than one page within an event. Good luck!

 

[Andar]

Thanks, it works now. Though, I still don't quite understand how the other ones worked, but this one didn't. I thought if I used a new switch, it'll be fine. So, the next time I use this same event for another cutscene, I would have to turn on self-switch C?


That's not right.

yes, what you're doing is problematical.
Regularly, you use ONE controlling event for ONE cutscene.


If you want another cutscene, you use another, different event.


Mixing the controlling sequences of different cutscenes into the same event will only cause you have logic complications.


The general rule/advice to use one event for controlling one cutscene is there to prevent the users to spread the content sequences of a single cutscene into several events - it never said that you would have to place the content for every cutscene into one single event, because that will cause logic problems like the one you have just solved...