@HappyKat78 Well what about just a rule that says (same as above...) when actor collides with [crosshair] AND actor collides with [enemy] then timer every 0.2 seconds change attribute self.health to s

It's constrain-heavy for sure, but it works!

Um, it's far from impossible. It's just a pain because you have to constrain a bar actor with its own unique ID that matches the ID of the enemy. Fortunately, tables make this a lot easier than in t

number of them) I can't use a game (global) attribute, I need to keep it to the instance. As it's the enemy's health that is being depleted then I'll need to have the enemy know when there is a mult

How will the enemy know? He'll know because the crosshair actor will have a rule that says when actor collides with [crosshair] AND actor collides with [enemy] then Change Attribute game.multiplier t

I also created a global attribute called Monsters as an integer with a value of zero.

Use Change Attributes for each of the game attributes, to reset them. And also use the reset scene attribute.

do - change attribute game.up to true

(Quote)

As far as work arounds, I wouldnt use them for moving objects. For stationary things, you can get away with combining a lot of objects to make complex ones. But I've seen objects using the Constrain s

The only thing to do is wait i suppose. I have put off a couple games until they come out with polygon collisions. No point in doing a ton of work to have the features that makes it simple come out in

I've got multiple instances of soldiers with associated crosshairs. When an enemy walks over a crosshair his health depletes by 2 every 0.2 seconds the enemy is overlapping the crosshair. However, i

We would need a better idea of what you are dealing with. It's nearly impossible to replicate what is going on without knowing how you set up your character or your collisions.

You also can't change the Movable attribute during runtime (although you can make a custom Boolean called Movable and have that turned on and off)

Sometimes save/load doesn't work for me, but when I remove save/load behavour and and add it again with the same key/attribute it works.

Im working on Mac, publishing to Mac to test that if save and load attributes work or not. Just an easy yes / no - answer would be enough, thanks! All the code part is in that youtube video. Basicall

Change Attribute scene.Fuel to 100

If I collide with a pod. That pod adds that many units to fuel attribute.

Hi @Yadda As @jamie_c said; and to add, you can't change the visibility attribute during runtime.

But I was wandering if there's a way to play with the visibility attribute ;-)