Something I forgot before: I would never simply constrain everything in my scene. What about a rule that only constrains them when they get out of position? So if their x or y changes from their start

The constrain approach works, and runs fine on my iPad Mini 2, so I think I'm gonna go with it, even if it's not the most performant!

120 instructions a second, every second (60 times a second constrain X / 60 times a second constrain constrain Y)

I’ve always thought that if I utilize “self.Tags” within “Change Attribute” to modify a behavior of an actor, it would only affect that single actor I’m applying to but I’ve just noticed by accident t

I'd imagine it'd be fairly easy to rework it to use a pause scene instead - perhaps using a game attribute which is changed on the pause scene to indicate if the ad delivers or not, and then triggers

You can change the space (offset) between the actors by changing the offset attribute in each actor.

I'v noticed the 40 in front of the sin with constrain that's set to the tile width seems to have somewhat of an effect i just cant seem to get it to the degree i'm after, when i increase or decrease t

Timeleft game attribute is a real number, yes. In the table the column "target time" is an integer. I haven't had any problems in updating the timeleft game attribute's initial value

(Quote)

Well that literally fixes everything. I just had to take the game.health attribute OUT of the timer so that when the player got destroyed it instantly returns the health back to 100 while giving it 2

(Quote)

Change attribute: game.health - game.health+90

* Images are case sensitive so you need to make sure the image text attribute matches the image name or else the graphics will be invisible, Example , Actor was called Hero and i replaced the image He

Can you tell me where in the video he has the rule where if the health attribute goes below 20 the player is killed ? I had a quick scan through the video but couldn't see anything ?

(Quote)

For the random generation, the room changes an attribute to random (1,4), with 1 being up and 4 being left (clockwise). I have 4 rules set up for each direction, saying that if the corresponding grid

. . . ok, the game attribute 'health' goes down 80, 70, 60, 50, 40, 30, 20, 10 . . . .

Change attribute: game.playerDead is True

change attribute money - 100

Multiply your y constrain sin function with -1