Make a game attribute - boolean - call it "climb"

(you could instead do a changeAttribute: self.Name or even add a new attribute

First you need game level attributes to track when a combo happens so say you have an attribute (integer) Game_Combo and have the events that trigger it add to it. So for instance a rule that says whe

Seems like the object wont be picked up now. Should the tags "pickedUp" etc be created as attributes first and if so what type? Never worked with tags in rules before except for coll

--changeAttribute: self.Tags To: pickedUp

the condition of the boomAttribute in that tutorial triggers action/event … as Tshirtbooth explains in the video

change attribute: self.stop += 1 // direction is no longer 0 "

Constrain the actor's X position to . . . AAA*cos((game.time+0.2)*BBB)+CCC

Well , since your actor(x) movement is based on constrains and its rely on a game clock , i don't think you can .. cause the constrain will override every change you make ..

You need to use the change scene attribute in the replay button and have a rule when touch is pressed go to scene game and also put a change attribute score to 0. For the last part you should have an

You need to make a self attribute "self.Move Now"

Constrain self.rotation TO Game.time*DDD

(Constrain the actor's X position to . . . AAA*cos(self.time*BBB)+CCC

change attribute: self.stop += 1 // direction is no longer 0

is your jump attribute is boolean type?

i have an attribute set so that when the backround is clicked the "jump" attribute will be set to 1 and when tis set to 1 the player will accelerate up. When it hits any platform jum

in my game you collect things with a ship, so for the first levels i just one thing on screen to collect at the same time. So i made an boolean attribute and if this is false i spawn an actor and set

What i mean, is how do I make a box that when you click, it starts one corner of the box, and it expands to the mouse position. When you let go of the mouse the box selects whatever was inside it. I g

It might be possible to do two updates. In update number one you create a game attribute called game.AlreadyBought. Then have a rule that checks the real device time (date actually) and if the device

Attribute: self.Position.X (or Y) ≤ 1