Understanding the Events
Understanding events, conditions, actions, and functions
Events are the foundation of your Clickteam Fusion 2.5 applications. Each event consists of one or more conditions, actions, and sometimes functions that you define in the Event Editor. Each event waits for a specific condition to occur in your application and then executes the associated actions.
Conditions are tests within your applications that trigger actions. All actions depend upon Clickteam Fusion 2.5 detecting a condition and then executing the actions associated with it. Collisions, movement, and visibility are all examples of conditions. For example, two objects colliding, an object beginning to bounce, or the user clicking the mouse are all conditions that can trigger an action.
Actions are triggered when a condition becomes true in an application. Once a particular condition is detected, the associated action(s) take place. Movement, visibility, and jumping to a new frame are all examples of actions. For example, an object can stop moving, become invisible, or jump to the last frame in the application as a result of a condition.
An example of the interaction between an object’s events, conditions, and actions is a collision between a spaceship and a meteorite resulting in the destruction of the spaceship. The event is the combination of the condition (the collision between the spaceship and the meteorite), and the action (the destruction of the spaceship).
Functions let you retrieve data from one object for use by another object or for use in an action. For example, if you want to display the number of lives that Player 3 has left in the Score object, you can use the Player object function Current number of lives to retrieve the number of lives in the Lives object for display in the Score object.
Spread the word!
You can share this document using the following buttons.