change attribute self.motion. linear velocity.X to something

(Quote)

it looks like you have the behaviors change attribute position x and y to 0 so check the behaviors in the attribute and if there is something like change attribute self.position.x (and y) to 0 then d

Knowing which attributes can and can't be changed at runtime is something I really should be able to know. Even an official list on the cookbook should be minimum, if it isn't implemented as a tiny ic

Change attribute / rotation / to 0.

You'll need to freeze all actors with physics applied to them otherwise they will continue moving a fraction before the pause fully kicks in. I had the same problem with mine. I achieved it by storing

The otherwise section (of the laser beam actor) would just need the constrain that you said you already have working:

Constrain Laser.Y to Enemy.Y(Quote)

I have set up my code so my game will work on iPhone 5 (In the XCode simulator), legacy iPhone and iPad by just changing the platform in Project Info and one attribute value in Attributes. I would hat

@vincentw if the load/save key is the same and you've checked, then you may want to try and force the load attribute to fire.

5) constrain the height of the laser beam (instead of the y-position)

--Change Attribute: self.difference To: game.EnemyY - self.Position.Y

1. Made self (real) attribute in laser beam called 'difference'

@vincentW Would it be feasible in your project to save the score to a table? On your home screen, you would load the attribute with the table value. If using nightly builds, you wouldn't need to use

Yes there's a display text actor to display the high score, and that one loads the attribute.

@vincentW have you also made sure to LOAD the attribute upon game launch or scene launch?

I have set a high score attribute that is being saved everytime it gets changed or is being loaded. Throughout my game, the high score stays the same, so theres no problem. But, when I'm testing with

I created a table with the attributes that I would like to change with each scene. Than I created a round rules actor to change the attribute to match the scene. .... My problem is that the round ru

-Don't use a constrain attribute repeatedly if this can be avoided

The attribute won't exist, you'd have to add it. You want one to store whether or not the character has died and/or one for when the game is over. You can use index/integer attributes with modulo oper