to add a "PlayerIsTeleporting" attribute that only allows teleporting to begin if it is 0 or false, set it to 1 or true while teleporting is going on, and then back to 0 or false on

If you used "Save Attribute" and "Load Attribute" then it should still be there when the user updated but only if you saved it to the same Key in both versions

Since I will have upwards of 12-15 digits in the scene at once, I'm concerned about the performance hit from so many Constrains. So, I am attempting to wrap the counting routine inside a Rule, as foll

create a global attribute called 'jump' (integer), set it to 0, create a rule on your character that when actor is touched change the 'jump' attribute to 'jump'+1. On you character make a rule that wh

Constrain the player's X and Y position to new attributes (integer) - PlayerX and PlayerY

If you respawn a killed actor after you hit it (and destroy it), why do you care to decrement the actor count by one then? Or are you decrementing it from some large "that-type-of-actor-coun

A word of warning, using custom font digits like that requires a Constrain Attribute behavior for each digit.

constrain

alpha to 0. then i make rules to pass a boolean attribute, closeupVisible, from the small window to the invisible close-up that change the alpha attribute from 0 to 1. I can't get this working thou

thank you so much for the quick reply, would those game attribute happen to be boolean? integer? or real? thanks again!

Then, did he change it depending on a game attribute using math functions? For example, if the total value is "83", would "digit-2" be something like "f

constrain motionX =0

No problem, I do understand Spawning and Attributes...just not sure where to add the game.CameraX with the spawning..tried numerous things.

To do this, create the two actors and place them in the scene. Create an attribute (boolean) called 'right'.

Personally, I would create a global attribute (boolean) called 'shake'.

You need to constrain the X and Y of the platform to the platform's original position. Create two attributes in the platform, origX and origY. Set those to Position.X and Position.Y

I think the movable attribute can stay unchecked and also uncheck the fixed rotation attribute.

imagine you have an actor that is jumping on a platform. You don't want this platform to fall down because of the actor jumping on it. So you would deactivate the movable attribute for the platform ac

-----Constrain self.Position.X To: Mouse.X

Create a custom game attribute called "screen-is-touched" or something. A boolean variable set to "false" initially. Create another actor attribute called &quot