It's going through the first rule, which changes the attribute to 1. That makes the second rule true and therefor adds another one.

Basically, I am trying to set up a buy button, which then changes to upgrade. The buy/upgrade button changes an attribute, another actor then changes an image depending on that attribute. The attribut

You'll need to get its current position, store in attributes, and constrain its position.

Change attribute self.physics.moveable to false

Change Attribute self.randomRow to random(1,tableRowCount(tableName))

I'd recommend constrain and rotate if your dealing with pixels, It just eases the whole situation!

Use the change attribute behavior to change the attribute you want to be change. Then change it to the tablecellvalue(table,row,col)

hi guys...i still cant figure this out...seems like it might be a bug? the image attribute of the actor is the correct image, and in the scene view it has the correct image, its only in the preview th

Without a custom keyboard, a better way than what you explained is to make a single text attribute with all possible answers separated by a character:

Not that I know of. However, expressions that have self attributes can be transfered, but global attributes cannot. Self attributes (ones already found when you create an actor) are always the same, w

You'll definitely be much happier if you change the image and/or animate the image rather than constraining a weapon to the main actor.

Whoa, thanks. Only thing that confuses me is the two equations for constraining position X and position Y:

If not I'm thinking I'll try to add both to my game and have an attribute randomly select the ad provider after each round so the GS community can see a side by side comparison of the two services.

Hey everyone quick question. Im working on a 2d platformer. The problem is that i have these NPCs that are supposed to follow the main character. I want it so that when an NPC hits a wall It will atte

If you are able to use a different actor for each type of actor that spawns, then you don't need to worry about instance attributes at all. You just do:

i need to access attributes of the collided instance, here is an example:

(Quote)

There is an attribute which says when tutorial number =1 display first instructions

To do this, you will need a boolean attribute that checks for collisions. True if the actor collides with a higher layered actor, and False otherwise.

Create two new Boolean attributes called button 1 and 2