We are finally returning for Event Triggers Part 2! (It appears “Next Friday” is more fluid than I was thinking).

In Event Triggers Part 1, I covered the simpler Event Triggers: Action Button, Player Touch, and Event Touch. These three can be grouped together as Interaction Triggers. They trigger when the player character interacts with them in some way.

Today, we will look at the other two event triggers, which I will call the Automation Triggers. The reason I call them this is that these events activate independently of direct interaction with the player characters. These two triggers are Autorun and Parallel Process.

Autorun

How it works: The Autorun trigger will start whenever the conditions are met. If the event page conditions are met, and you are on the same map as the event, it triggers. It will loop indefinitely until the conditions are no longer met.

What is this used for: Autorun triggers are used most often with cutscenes that start the moment you walk onto a map. You can also use it to reset a puzzle in a room, or set any conditions that need to be set when certain conditions are met.

Things to keep in mind: The biggest thing to keep in mind with autorun triggers is that as long as they are running, the player will not be able to do anything, and that until you end them, they will repeat forever. If something needs to happen every time you enter a map, you can use erase event after it runs through. If something needs to happen once and then never happen again, you will need to use some form of switch/self switch condition on a second page to stop it from occurring again.

Parallel Process

How it works: Parallel Process triggers work similar to autorun triggers in that they start whenever the conditions are met, but instead of stopping player action, they run in the background allowing the player character to continue on while the process is working. They also, as with Autorun Triggered events, repeat indefinitely as long as conditions for them are met.

What is this used for: Parallel Process triggers can be used for anything where you need to constantly check for certain conditions. Examples of use include: Keeping track of the state of a timer, checking for a button press by the player, keeping track of the coordinates of the player or certain events, having a flash of lightning occur at certain intervals, etc. It can also be used in a lot of timed events, such as farming systems.

Things to keep in mind: As with autorun events, you will need to keep in mind that to stop it from repeating, you will need to end the process in some way. Another thing though to keep in mind with parallel process triggers is that you do not want to run too many at a time. The more of these events you have running, the more chance you will encounter a drop in your FPS.

And that covers all of the event triggers. A lot of systems can be made with only events without ever touching scripts, and mastering triggers is a huge part of eventing. Can you think of more uses for each trigger?

One of the many things that may be a bit tricky for beginner’s is how to start events. Some triggers are easy, but some you may start wondering “what’s the difference here?” or “what do I use this for?”

To make things easy, I’m going to go over all the event triggers. This week we will go over the simpler triggers: Action Button, Player Touch, and Event Touch. Next Friday, we will explore Parallel Process and Autorun events.

Action Button

How it works: When the player presses the action button while in the proper position (when on the same tile for events that are above or below the characters, when adjacent and facing the event for events that are at the same level as the characters) the event starts.

What is this used for: This is probably the most common type of event trigger. Any time you want the player to activate the event, you should probably use Action Button triggers. Examples of use include talking to NPCs, flipping a lever, opening a treasure chest, or any other situation where the player should be in control of whether to start the event or not.

Things to keep in mind: There generally isn’t any special considerations with Action Button events. The only thing that occurs to me to keep in mind is that facing doesn’t matter on above or below level events, so if your scene will need the character facing a certain way, make sure to use a Set Move Route command so they are facing the direction you want them to.

Player Touch

How it works: This is also a relatively simple trigger. The moment the character moves into contact with the event (either bumps into it for events that are set to the same level as characters, or moves into the same square as the event for those set below or above the characters) the event starts.

What is this used for: Player Touch events are also incredibly common. Any time that you want something to happen when the player is in a specific location, regardless of whether they start it themselves, you use Player touch. Examples of use include depression switches on floors, all types of transfer events (stairs, edge of town, etc.), and starting cutscenes.

Things to keep in mind: The biggest thing to keep in mind when dealing with Player Touch events is that it comes into effect only when the player moves INTO the event. If the player is standing still and the event bumps into him, it will not activate.

Event Touch

How it works: This works a lot like Player Touch, except it activates whether you touch the event, or the event touches you.

What is this used for: The main use for this is anything that MOVES that should affect the player. Examples of use include wandering monsters, flames, and moving blades.

Things to keep in mind: Remember that unlike Player Touch, this activates whether the player touches the event or the event touches the player. Also, if the event does not move, this operates identically to Player Touch.

Tune in next week when we cover the two more complicated event triggers: Autorun and Parallel Process.