If your on the Mac creator use an index attribute they don't go negative.

Without seeing your rules, it's impossible to know why something isn't working right. Here's what I suggest: in the ball actor, have a Change Attribute behavior to change game.ballCount (integer) to

(Quote)

You can't change the moveable attribute at runtime.

create teo attribute in the actor start x and y in the actor put two change attribute that change start x and y to his position after create two constrain attribute that constrain start x and y to the

It will be more helpful if it is more specific..how to constrain their position??.Pls help me

You need to constrain them to their position until the player actor collides with them.

Replicate and constrain mostly driven by sin/cos + vector to angle + magnitude, and that's about it ! No tables or hundreds of attributes or anything like that, it's actually reasonably straightforwar

Or you could use it at the end of the game to record the score . . . simply copy it into a an attribute (let's say a game attribute called 'FinalScore') . . .

To make the game.timer do the 0.000 would I change it to real attribute and not integer ?

At the start of the swipe record the finger position into two attributes (start X and start Y).

Anyway, after struggling for a while trying to get a simple solution I ended up using an Index attribute, as Index attributes can only store positive values you can throw a sine wave at it and it will

I have 2 real attributes game.characterX and a game.characterY.

Hi, what are your settings in the Constrain Attributes for the shadow (its x and y)? you need offsets on the x and y to see the shadow....

(Quote)

Hi @AtomicFX Off the top of my head, make the actor that moves back and forth across the x spawn only the character actor; then have the character actor spawn its own shadow actor behind it - which i

when enemy1 is destroyed change attribute game.count to game cont+1

Just have a single attribute, let's call it ZKill.

I want to have a scoring system for my game where every three enemies destroyed = 1 point. I've played around by having two attributes game.zombiesKilled and game.killpoints I had a rule that says:

CHANGE ATTRIBUTE: self.ButtonOrder TO self.ButtonOrder-1