This is one way of making Behaviors reusable.įor example, consider a Behavior called Jump that has been designed with customization in mind. Although the Attribute might start out with a value of 5, if the character takes damage, your Behavior will change this value to something lower.īehavior designers can choose to expose Attributes, which allows them (or other game developers) to customize these values in the Actor Editor. Depending on what happens during the game, however, you will want the value to change.Ĭonsider the Health Attribute mentioned above. When you first create an Attribute, you'll assign it a default value. (In fact, in many cases you don't want them to.) Two of the defining features of Behavior Attributes are that they are changeable and that they can be made customizable.īehavior Attributes don't have to keep the original values you set for them. In total, there are 16 different Attribute types, which are described here. For example:Īn Attribute called Health might have a value of 5 and the type Number.Īn Attribute called Shirt Color might have a value of Blue and the type Color.Īn Attribute called Hero’s Name might have a value of Link and the type Text. They enable Behaviors to keep track of dynamic parts of a game and make it possible for developers to customize Behaviors without editing them directly.Įvery Attribute has both a value and an associated type. For cases like these, we’ll use values called Attributes.Īttributes are changeable values that are used within Stencyl's Behaviors. Many of these are things that we, as developers, want to keep track of. Most games are very dynamic characters move around, players press buttons, and properties like health and score change.

Stencyl dialog