Just create a attribute called MinValue

At the moment, collision detection is only with square or circle (selected in the actor's Attributes > Physics > Collision Shape > Rectangle-or-Circle). We might be given the opti

I posted at the same time you did. Yes that's it but move the Change Attribute below all your spawn rules so it is the last thing the timer does. Things get lost in translation sometimes, glad you got

Attribute game.iTimingSwitch = 1

Any ideas of a workaround? Using a fake object and constrain two halves of the original object to that fake object? Still probably having collision shape issues (needs to be sphere)?

Below all the rules and everything else in the Spawn Ball (Timer) add Change Attribute iTimerSwitch To 1 (Now the rule above will fire again because the condition has changed)

1. I set timer change attribute for every 0.1 sec, change attribute game.iTimerSwitch to 1. (It makes it impossible going 0/ or off)

Your timer is fine this is to do with your rule not firing. Create a game level attribute iTimerSwitch or type integer.

You could do this by creating a new integer attribute call it something like iTimerSwitch and use it as a rule condition "When iTimerSwitch = 1". Once you have set your time in the r

Explanation: this function shows a logic which every ball touches the ground will deduct 0.1 secs/value from attribute "game.Timer"

nonono, not that. That is my own created attribute for item which I want to use when number"Random" appear.

It looks like you need a Change Attribute game.Random To random(1,?) the "?" is for however many options you have. Place it in your timer above the first rule.

I tried to use attribute for value in expression editor, it worked. However, when the value of the attribute started changing IN-GAME, the function still running the "old/first value&quot

So I placed the attributes as you noted, but it didn't even get to the second plot point, the 510/570. Then, I took the MoveTo: 510,570 attribute out of the When position.X rule, and it did move over

Create a Game Attribute (integer) called deviceSize (for example)

If iphone 5 -> change attribute -> self.position.X = 123 & self.position.Y = 123

change attribute scene.camera.size.width to 378

Using Move To creates this weird loop that brings him back to the starting point if I use more than two Move To attributes in sequence. I’ve tried to add a rule where self.position.x equals the last x

Constrain Attribute: [ self.Position.X ] To: [ scene.Camera.Origin.X + game.Mouse.Position.X ]

(Quote)