yeah it still doesn't work. I made it to where if the attribute = 1, collide w/platform.

Instead of using a rule where a key is held down, make that rule (above) change the value of an attribute -- say an integer or a boolean -- and then make a separate rule that collides based on the val

to hold. I'm thinking something with a boolean attribute..

@Two.E touched on this idea too, but @Toque’s extra advice makes his tip a worthy winner too. Hiding actors can be super helpful, but it can be a nightmare to find them again while working on your sce

(Quote)

Here is just one example of how to use it, although it works anywhere where you use the expression editor - like in a Change Attribute behavior.

Im thinking have an attribute for each floor and a path to follow to that floor. Or if player is above enemy move to nearest ladder.

Ah, okay, yes I've done this before to constrain a health bar above an enemy actor's head. I ended up using an Every 0 seconds timer.

Well yeah, you could do that with a timer but the more important question is: why do you want to constrain a table cell value? The only time they get changed is if you use a Change Table Value behavi

Similar to how game or self attributes with the constrain attribute behavior, how could a value in a table be constrained?

The Arrow actor has two change attribute behaviours and two interpolate behaviours. As well as two 'real' attributes. Target X and Target Y

I agree that there's definitely a place for global variables, there are many many situations where global attributes are definitely the better approach, but where absolute efficiency is concerned loca

Where X is an attribute and starts out as 0 or 1, repeatedly changing X to 1-X toggles X between 1 and 0, which is really useful for things like flashing lights . . .

Sometimes I had many commands overlapping when I only wanted them to happen at certain times, so I added a game.Action attribute. Imagine making a slot machine...

Q2. The music will stop when I set change attribute "Device>Sound>0".

layer 2 - actor collisions etc

Already mentioned above but unlocking of actors in a scene unless needed is a massive no no as this always causes issues so if you do need to create an instance (an unlocked actor) then leave yourself

Don't unlock actors in a scene unless you have a good reason for doing so. Unlocking an actor creates an "instance" that can have different rules (and even attribute values) than th

* You can make any actor Invisible by changing the self.Alpha Attribute to 0 (zero).

I am using contrain attribute so it doesn't go pass 100, also I use replicate for the bar, so whenever mana is added the bar moves up one. The issue is when the mana resets, the bar doesn't. It either