Create a game attribute called player and one called scene.

Create an integer attribute called score.

@joelloyd Are you saying that you want something to happen every time the attribute is a multiple of 2 and something else to happen every time the attribute is a multiple of 3 and so on for 4 and 5?

change attribute tableCellValue(yourTableHere, What you called the row here, 1)

Use a Change Attribute behaviour . . .

That will depend on how you are currently changing the invisible player to the selected character - for example, if you are using a game attribute to change the invisible actor's image then all you'd

I'd imagine you'd have to use game attributes,

-Change attribute self.position x to 0 - self.size width/2

Seriously GameSalad is Great... But what I am truly waiting for is custom collisions, If they add that feature in a month or two with a price, I would surely pay those extra bucks.

really need both those timers . . . the change attribute behaviour (random toss to (1,3)) could be moved into the second timer like this (screenshot below) . . .

That's what I've been trying to say for a while, when performing calculations on an attribute you are not limited to whole number values, even if the value you are dragging through some calculation/eq

Attributes only define how values are stored they have no bearing on how an actor moves or how a value is interpolated or constrained or otherwise operated on by a calculation - I've given real world

(Quote)

The pro behavior tab could be changed to an attribute tab so you can change actor attributes without the need to actually open them first (comparable to the windows creator). :O

Just downloaded 0.13.30 but I don't see the Pro tab under Library anymore. Also, is that where I can expect the "Game Center" attribute to be located? Thanks!

* Fixed issue with decimals being removed from attribute values if region format was set to use commas instead of decimals

My attribute is saved as this in the Display text actor of total items like this - Total_items = Total_items+Items_Collected

then in the prototype of the white one change attribute position x and position y to 100

The answer above will give you a precise division of 100 ( going on your idea of using a REAL attribute to store distance), the version below quantizes point scoring to 10s, so at the very centre you

remove the constraints and variables I told you about