Change Attribute game.enemyCount (integer) to game.enemyCount + 1

What I have is a game level "all enemy destroyed" boolean attribute, a Hero with a rule if that attribute is true then go to Victory scene and Enemy actors with a change "al

(Quote)

@Agent Argyle Did you go into each file manually? You can do that change in less than a minute using Dreamweaver and ctrl+f, select the "folder" option, and just put the appropriate

If your file can't open from there, you could try opening from an early version like 13.40, BUT make sure you are not using any new features from 1.23.1 and above such as custom collisions, as the fil

(Quote)

Beside the numerous bug fixes, the last few weeks have brought HTML5 authoring, polygonal/custom collisions and an app store based GameSalad Viewer (Google Play already up, Amazon/iTunes on the way)

Basically: I have a call to Network Get Table at the start of my game that has no problems. I have a call to Network Send Table at the end of the game that seems to never run, despite the block/timer

If you don't use custom collisions there's not likely to be a problem. But just back the file up first and you're safe anyway.

(Quote)

saying that any time you've changed the physics attribute directly, they'd be automatically updating that. It would be when you change friction at runtime that you'd be affected. So if you have a rul

(Quote)

Sure. Make a game level attribute integer attribute "player" set it to 1 as a default. Wrap the move rules for each actor in a rule inside them.

Make a self attribute in the actor self.row and put the number of the first row in it.

The change attribute will only fire once. Use a loop behavior inside the rule instead of another rule.

--------------- Change attribute enemiesSpawned to enemiesSpawned+1

(Quote)

Thank you @Lost_Oasis_Games after i save attribute and load it everything works fine but now i have another problem with Consumable when i buy its must give me 3k coins but its give me 16k coins look

a loop will keep firing. So putting a change attribute in say a loop the change att will fire every cycle unlike a rule where it will only fire once when the condition changes.

(Quote)