i have a rule for my ball actor to constrain self position to hole position when overlapping with the hole and also when velocity is less than 300, so when the ball is going from left to right and top

You mentioned create boolean attribute called itemcollect, but then you say itemcollect01, (whats the 01)?

you are mentioning, do i need to make an attribute called level01?

For the save attribute...if you use in level01 in the save attribute key: ItemCollect01 you must use in your load attribute for the same level the same key: ItemCollect01.

sorry but how do I add level 1 in an attribute?

You could constrain a bigger invisible actor to the ball and have all your rules in that. Then use those game attributes to reference from the ball to figure out what to do

Set an universal boolean attribute called ItemCollect or something. Then You make a new actor called ItemCollect.

Then have a change attribute to change self.position to -100 (offscreen)

You'll need a game attribute (boolean) and call it dead for instance.

When touched is pressed change attribute .... to true

Couldn't you just spawn the swiping actors and constrain them to the car actors? Individual swiping actors for each individual car would work.

1. Spawn and destroy can cause a hit on performance. Why not use the change attribute on your background's x coordinate? I think you can also change attribute self.velocity.x or y instead of using t

FYI, I have... Constrain Attribute: self.position.x TO 28+(self.size.width)/2)

Constrain self position x to where you want it to stay.

What about that?

constrain self.position.x to device.mouse.position.x

optimized to the point where we don't need attribute workarounds and with optimal RAM usage. I'm sure the experienced users ALSO want the RAM usage optimized... but they can still release their game

BPM is a real attribute, since whole numbers are not precise enough.

The debugger lets you view attributes in real time. It doesnt really mattter what actor its in as long as that actor has access to the attribute you want to see. Then whenever you want to view it and

i'm inside an actor, and i want to spawn another actor, dependent on how quickly another actor was tapped. so, if i go to rule-->attribute, i only see the actor that i'm currently in. is ther