You keep track of the score with a game attribute such as game.Score (type integer or index). Each time the player answers correctly, do Change Attribute game.Score to game.Score+[button value].

3) Check the table value against the guess that was inputted. You have to create an attribute to temporarily store the guess that was made (e.g. "gold"). You can do this with a tex

--Attribute (self.DistanceFromMaster) < 100

And start the attribute on -1

It would start as -1, on 1st touch it would change to 0, 2nd to 1, 3rd to 2, 4th to 3 and then repeat. So if you changed the main rule to activate when the game attribute equalled 3 that would work

(Quote)

Basically the percentage used in the way @MarkOnTheIron suggested means the change attribute will cycle between a pre-defined number of options.

Make a self integer attribute called touchtime, and say every 1 second, change attribute touchtime to touchtime+1, and if touch is pressed, change attribute touchtime to 0.

I have an actor and a crosshair (ok, that's another actor, but I'm differentiating them for you!). I am trying to set it up so that when you click on the crosshair it's X and Y will constrain to the

Oh yes, I would send a bug report, but I don't think it's a bug. Some of the attributes aren't meant to be changeable during runtime, and that's intentionally that way.

The way around this is to set the attribute at 1 to begin with.

Something like that. However to avoid confusion it would be better to run the rule when the attribute reaches 0. For example in my example above the attribute will reach 3 and then revert back to 0 ev

Use a game attribute, it will start on 0, it then counts 1, 2, 3 and 4 and resets back to 0. Run your rule once the value = 4.

If you want other actor to see it then use a game.attribute instead of a self.attribute.

1. Create an integer attribute (it can also be a self attribute if all your rules will be on a single actor)

Yeh 1 line would work fine in fairness, I was saying use 2 as that second attribute could be a game attribute, therefore you may want to trigger multiple actions across multiple actors.

What attributes do I need to add and where?

You'll need to setup some attributes to count whats going on. Theres 2 ways, 1 spawner spawning all 4 corners or have a spawner in each corner (simplest way and wont make much difference on performanc

You'd need two attributes;

Example: lets says i want my integer attribute to say "every interval of 5 do xyz." Its not the xyz portion thats the problem, its the interval that i'm stuck on.