This got fixed for me in a later update, where the reading in of table data and attribute data seemed to be fixed. All good now, cheers.

5. Turn every attribute under the physics tab in the actor editor to 0 on actors who do not need it.

5. Turn every attribute under the physics tab in the actor editor to 0 on actors who do not need it.

EDIT: I narrowed my problem down and it is definitely the load attribute that fires at the start of the game that changes the boolean to true. Because when I turn the rule off my boolean stays false w

create a reset (BOOL) attribute, than when you pressed reset button change attribute ->yes, if reset attribute yes, spawn actor

In this case, yes it would be one attribute for all. But you could do it with one each in a pretty similar manner, more logic would be needed however.

@natzuur for this to work they need to all be under one attribute? lol because i made one for each character before and starting to think thats not how ur method works.

When attribute ≠ (does not equal) id interpolate away.

i have on the button to select which character you want a attribute with (slidecharacter+1)%2 so ill change the 2. then the characters have when attribute =1 interpolate... so how can i write them to

Not sure what rule sets your using, I would just create a index attribute (we'll call it characterID) and use the mod function to cycle the numbers. So each char has its own Id (1,2,3,etc).

Are you resetting the attributes game.ballonscreen to false before the change scene or right at the start (simple as a change attribute to zero with no rules placed on the scene)? Also the bottom rule

after 5 seconds change attribute

(Quote)

it means collisions are only available for shapes that are rectangular or circles.

Got it working. For those wondering, Joshiwu is partially correct in referencing the pos. Y, but that was not enough. I had to reference an additional attribute before fit worked. In my case, I had a

1. the volume knob spins all the way around in a circle, how do I constrain it to a min/max?

he basically makes a attribute that when you touch it it moves a actor from x to another x position

Change attribute

Change Attribute: game.Switch = (game.Switch + 1)%2

Since I spent almost a day hunting for the mysterious "%" to find out what it means and how to use it, I thought I share this super helpful explanation by @firemaplegames with all …