In each of the enemies i added a constrain selfx to abs( game.HeroX - game.Enemy1X ) then when punch or kick is pressed check the distance is within a certain range you would also need to make sure th

Other than that, I don't really think about what my first attribute is going to be before I add it.

I'm learning to do a game.score or game.primaryrules attribute first.

I've just discovered a great way manage the alpha on a lot of my buttons. Previously I'd put a 'hide me' change alpha attribute in each of my button actors, that I would overlay on top of my flattened

     Change Attribute game.bulletCount to game.bulletCount+1

Not sure if this is want you want - make two integer attributes - game.ammo1, and game.ammo2.

in the end i just had to make a Save and load attribute on the home menu but theres 36 of them and it gets tricky no lag surprisingly but i would still like a table system, its just going to take me s

Just doing some experiments and I've come across a weird behavior where I've Constrained the X and Y coordinates of the Weapon to that of the Character Actor, but at a certain consistent point in the

platform game, but without tile maps and tile collisions it becomes far more complex and time consuming than it should and you end up with so many collision objects - which is terribly inefficient.

Change Attribute "average" to (tableCellValue( game.My_table ,1,1)+tableCellValue( game.My_Table ,2,1)+tableCellValue( game.My_Table ,3,1))/3

(Quote)

-- Change Attribute: [self.Rotation] To: [90]

Change Attribute self.color.Alpha=0

Put an attribute in your spawn rule that says when enemy count is < the max amount spawn actor and also count them as @tatiang describes and it will stop spawning when the count goes to the max

It sounds like what you want is When game.enemyCount < game.EnemiesForThisLevel, then spawn a new enemy. In your enemy actor, have Change Attribute game.enemyCount to game.enemyCount+1. You d

that says When game.spawning is true, change attribute self.instance (boolean) to true. In the spawner actor, after the actor(s) spawn, change game.spawning to false. Finally, in the prototype acto

P.S. I know it is a program flaw and have tried to fix it with attribute math but cannot

at the beginning of the game into the high score attribute you created. You can do this either with a table or a save behavior. Then on the end game scene have your button to reset game and inside th

Is there a reason that you're using tables for this? If you just need to compare the current level to the number of levels completed, you'd want to use an integer attribute instead of a whole table.

Actually, what would make it even easier for us is an improved particle behavior with its own gravity, collisions, and some other things I'm sure you already know about. (Image)