Another way you could do it, if you didn't want to unlock any instances is to put a change attribute: game.gas to game.gas+1 on the prototype for the petrol tank

attribute: self position.Y = 720 (you can use = to or less than, or greather than etc)

Make an attribute gas (integer)

Create a game attribute called RandomNumber (integer type).

Use a global bolean attribute called game.Disappear and use this rule in the player actor.

create a game attribute, you can make it a integer and call it disappear or whatever you want

But A1 is attribute that contain text, and I want to show the content of the attribute A1.

I'm trying to apply varius friction to each object but they seem to be unstoppable (the go really slow but don't stop). Where attribute i must modify for make object stop after they bounce with walls/

Create a game attribute (integer) and call it PowerUpOn

I'm using parallax scrolling in my game with constrain attribute to scene.Camera.Origin.X and when I put any multiplier or divider to set the scroll speed GS preview just hangs. When I uncheck this ru

Create a game attribute (integer) and call it PowerUpOn

I have attribute named game.RandomPick of type text that contain a random name of a attribute.

I made a self attribute for my enemy hitpoints=10 and a rule: If actor collides or overlaps with bullet change att self.hitpoints to hitpoints-5. Then if self hitpoints is less than or equal to ) des

Change attribute scene.NextMove to 1

Create invisible, or visible walls. Go into the wall prototype and add the collide attribute. Then select actor of type: then choose the actors name from the dropdown box. Tell me if that works.

One way to make the character move by pressing a button is to first get the character moving. Then above where images go, look for where it says game. Click it. Then click attributes. Create a new att

Create two Game attributes. Call them (whatever)X and (whatever)Y.

i have an actor that runs constantly and when i jump the actor does not change to the image i set it to change. my jump rule is to jump when game.jump is true and change attribute self.motion.linear v

No, I am avoiding using constraints because it slows down performance so I made my own algorithm to keep an actor on an actor. I am wondering if i should use the "MoveTo" Attribute

If you want an actor to stay in the same place with another actor, should you used the Move to attribute or make a rule? And Which option will give you better performance?