@Hypnorabbit That's the one issue with it currently. The attributes in the Inspector won't display until you add a new attribute (which you can then delete).

For the first part, use an integer attribute to alternate values:

(Quote)

any way to Constrain sounds

- First pass of tighter UI elements (affecting behaviors, lists in the library, attributes, etc)

Make an index game attribute called actor_recycle, set to 0.

thanks @Metallo for the explanation. I'm having difficulty understanding how you said that it changes the attribute once the player gets half way. It says in the rule "when .. is 725 etc.&

I am trying to consolidate some of the behaviours in my game into one Actor that i do not need to edit the rules of in each scene. i am trying to use Go To Scene and use a table cell value to drive th

You can edit attribute values without unlocking the actor. As shown in the attached demo.

2nd place: Don't unlock actors in a scene unless you have a good reason for doing so. Unlocking an actor creates an "instance" that can have different rules (and even attribute value

1) adding a health attribute, so players can get hit by more than one enemy instead of dying from a single hit

Just checked the tutorial and it is easy, the player has the control of the camera, everytime the player is jumping to the half of the screen the game attribute isHalfway is true, otherwise is false.

I agree @Icebox, @Two.E. I am determined to make one small game with it before deciding if its worth the cost. Alternatives. I don't hate it, don't love it.

* Cant use custom collisions/fonts.

For the touch controls i used Constrain Attribute as follows;

If you want to keep the actor non moveable ,you can constrain self.rotation to self.rotation + 2(or any number) to get a counter clock wise rotation or -2 to get a clockwise rotation , but it will pr

Thanks for the help but one last question,I managed to constrain them but now I want to spawn them randomly on the scene but not when actor is touched but with a set timer for spawning.

@Two.E I was struggling to constrain when I have 4 actors, can you tell me how to do it with more than 2 actors

The demo showed you how to constrain to a main actor when they are placed on screen. Which means you already know, before the game starts, the distance difference between the main actor, and the one t

because 'precision' first needs to convert the attribute it is rounding to text, perform the operation, then convert it back to a number, whereas round/roundTo performs its operation directly on the