You will also need a global attribute to tell each actor they need to be destroyed. Basically have a boolean, say destroyHatMenu, that when true causes each actor to run a destroy routine.

called 'player y,' which you would use a constrain behavior to make it track the player's y value. Then, create a rule for the 'enemy' that if it collided with 'player,' then the player would die. (Y

I have an attribute and I want the value to always either be one or two. So say it's player one's turn and he finishes his turn then you add one to the attribute then player two goes and finishes his

ok...any hints on how to even begin to conquer this problem? I've already followed the advice I could find...unchecking preload art, unchecking movable where possible, don't really use constrain attr

-Attribute: self.Color.Red =1

--Change attribute self.Red to (self.Red+1)%2

--Change attribute self.Red to (self.Red+1)%2

And when I try, it doesn't work. I tried many ways (by using otherwise stuff, I also found here a video to explain a kind of "On/OFF" with attribute but doesn't work neither, etc.) a

thank you @Manto1 for the Tic Tac Toe template. i tried to go through your template but i cannot understand how you change attribute Self-image to X.png,, and O.png. Where are X.png and O.png refered

gameAttribute: unlockedLevels … index type … should start with 1 (change the zero)

You can make it by checking game.attribute is empty or not ?

Let's make this straight - you have one attribute, and it works like this:

in game , i have one attribute called unlock its a integer attribute and on number 1

You should have an attribute for each level, and change it to true when the level is unlocked. And remember to save, and load them - so player keeps levels opened, when he restarts the game.

I am using keyboard entry for the first time, and I am changing the value of a game.attribute when I have entered text.

My IAP is not consumable. Should I publish the game as it is and hope that Apple will save the attribute? Or should I wait for the problem to be solved?

You still need to save if you write to a table. As for what to use, it really depends on your use case. If you have many attributes that you save doing it with a table will save you a bunch of load/sa

I haven't used 93 yet because of the few horror stories I read here, but am I right by saying that if you write an attribute (example is a score) to a table, you don't need to save attribute/load attr

use changeAttribute: self.Image … rather than changeImage behavior

*keep global attributes as low as you can. use either scene attributes or self attributes where possible. one trick is to use a table for storing data that needs to be globally accessed then in any ac