Designing behaviour

All developers using Stencyl to make games from scratch starts with creating behaviors or events that have already attached to the scene of actors. 

Basics: 

When created :: initialisation

When drawing :: HUDs for example, player HP and even checking where bug comes from. 

When updating :: do every frame , can substitute time. 

Time, 

After N seconds :: can be substituted by When created

Every N seconds :: can be substituted by When updating

Input 

keyboard - Require controls. 

mouse - click >> can be used to substitute mouse - on actor

mouse - on actor 

Actors 

Created or Dies :: score gained, drop loots, 

collision :: ammo hits player

Advanced. 

Custom event: can substitute just about everything EXCEPT drawing and Global Custom blocks. Custom events can form loops (requires 2 or more). 

They can also form loops without using while loops. 

They are public function without parameters

They can be split or merged. 

Custom blocks: 

public function that can substitute just about everything EXCEPT drawing and Global Custom blocks. They are basically custom events with parameters and able to return value. 

Global Custom Blocks.  

public static function cannot use attributes. 

They are mainly used to determine base values and XP tables, and other calculations. Possibly used to cheat math exams in a manner that it produce full steps. 

custom code: 

custom import: attribute types that is not provided by Stencyl. If you are an experienced flash game developer without Stencyl, you know this very well.