Actions occur as a result of the conditions in your applications. Once a particular condition is detected, the associated action(s) take place.
Each object type has its own set of actions that can occur when Clickteam Fusion 2.5 detects a condition. For example

• Lives objects can be gained or lost.
• Score objects can be increased or decreased.
• Storyboard objects can cause a jump to the next frame, cause a jump to the previous frame, restart the current frame, and end the application.
• Active objects can be moved, animated, or destroyed.

You can access the object actions in the Event editor. Along the top line in the Event editor is a series of object icons representing the available action types. These icons differ depending on which objects you have included in your application. You can enter your actions by right-clicking a grid box under an icon and choosing an action from the pop-up menu.

Ordering the actions within an event
The order in which actions are added to an event determines the order in which those actions are executed when the condition of that event becomes true. The order of actions can be very important. For example, if your event has two conditions, one to increment a counter and another to select an item from a list which corresponds to the value of the counter, the order is very important. If the counter is currently at 1 and you increment it by 1, your event will select the second item in the list. However, if you perform the actions in the reverse order, the first item in the list is selected.

To modify the order of the actions in an event after you’ve entered them, you can right-click the number of the event and select Edit the Actions. This opens the Event List Editor which displays only the actions for the selected event. You can drag and drop the actions in the list to change the order in which they are executed.