Tables are more efficient, but saving attributes works as well if you just want to use them for a few things.

(Quote)

If you have 15 actors in a scene ONLY using the Move behavior, I wouldn't think that's too much for the engine to handle but again, if you have other behaviors that I mentioned (e.g. constrain, etc.)

sleep option you can keep things moveable for collisions and such. They will be out of the physics until interacted with and then after sometime go back to sleep. Much has changed with the engine as

(Quote)

I mainly use Move, interpolate, Animation, constrain.

I mainly use Move, interpolate, Animation, constrain.

If you look at @Socks' gif above, you can click on a color in the color wheel or the crayon tab or whatever you prefer. Then, click on the color sliders tab (it's one of the five small buttons above

I am wanting to change the background colour of a scene for the sky to various colours depending on what is selected. I have clouds moving over it. I have an attribute backgroundcolour. When backgro

Then divide the integer value by a constant. So your change attribute values would be something like this:

Depending on how PE handles them, you might be able to make one large sprite sheet, auto generate the collision data, and the separate the collisions out individually. Not sure on that though.

(Quote)

Anything that loops quickly, such as a Timer or Constrain behavior will affect performance. There's no set amount that I can quote such as "only use two timers in a scene" but it's

I have a system where when you are in the line of sight, your player spawns an actor called "chase" that the enemies move to. Getting on the LOS enables a game attribute called Enemy

When I said you have to troubleshoot game.Word, I meant that that's the attribute that isn't getting the value you expect. Since game.Word is built from other attributes (e.g. game.Bullet), you might

hmm think i fixed my problem i did this:in player actor i put a timer below the spawn actor,and put a for x seconds constrain shoot to false..

(Quote)

I see you issue in the touchweapon rule. You are using the else section which means when touch is released it turns to false. Does it have to stay touched for the sword to stay active? If not, remove

result. I wouldn't recommend changing an attribute to a search for that attribute as you're doing here... use a different attribute for the result:

(Quote)