Great. I need to make one thing different from your tutorial - instead of when touch is clicked, when game.attribute%2=0. However, I do not know how to type game.attribute%2 in the first blank space (

(Image)

Thank you but I cant really get it how to make game.success%2 since when I put an rule - attribute I can only choose in first blank place, editable is the second one.

I don't think apple sends down the local symbol. we were going to add a new device attribute to allow you to get the language code.

make control camera to 2nd player..and make 2nd player constrain to 1sr player x, y positions. then hide the 2nd player....thats it...

The work around I have found that works for this is have a self attribute in the button and change that self.att to true when [purchased] then run a rule that triggers the timer and do what you want t

Have one game attribute, called game_speed, which starts at 0.

Change attribute self.movement to self.movement +200

lets say im already logged in to gamecenter. If i call the login attribute at the begining of my game would that show the login widow again? or would it cancel showing the widow bc im already logged

Is it necessary to use the "login" attribute when incorporating game center leaderboards in your app?

Anyway, if you don't want to use game.time, use your own timer. Set an attribute to 30 and then do a timer that lowers it by 1 every second. That way you will also go into minus, so times over 30 seco

This only seems to be an issue if you use that expression in conjunction with Display Text. If you create a game attribute (integer) and run the same expression and then have an actor display the game

Does the actor jump at all? If not you can constrain the Y position.

Hello to GS Community,

This one has true polygonal collisions too ! It's actually not the sort of project where you would particularly need polygonal collisions, but it just happens to be a side effect of the method used to

If we were going to start voting on some of the aforementioned suggestions, before a new stable release is finalised, I'd go along with these:

@adent42‌

Use the Change Attribute behaviour not the Constrain Attribute.

(Quote)

Then I'd build my UI so that if it's sitting in the corners of the screen, it will detect screen size and move the UI elements (via a Set Attribute action). So if the screen has a smaller apsect rati