and use something like a Move behavior with an attribute (game.Speed) as the speed and just change that attribute when you need to.

Unlock an actor on the scene and you'll see scene attributes among the normal list of attributes when you do a change/constrain behavior. Camera origin will be there.

The start of the game might not give enough time for everything to load. It is like it didn't load some rule or attribute fully.

When touch is pressed change attribute (game.test-tb, 1, 1) to

rule: attribute: game.roll= true do: animate(roll antimation)

constrain attribute

Hi Timo, I can't add anything more to what @pHghost wrote other than to underline the fact that there's no access to scene attributes or attributes belonging to another actor via the Rules section in

2)its just as easy to set up, all it takes is an extra attribute and one extra rule which everything els fits into.

I usually always make a game attribute but now ai have a lot that I cant fins them anymore so I thought it was easier to make a scene attribute.

Prototypes don't have access to scene attributes, only unlocked instances do. That might be your culprit right there, but hard to say.

Its an integer attribute and starts with zero.

Attributes

what kind of attribute should I use?

hat you would do is create an integer attribute called baddies_killed then you would add a rule to your baddies stating when baddie overlaps or collides with actor of type weapon to change attribute g

the way i would go about this is creating a real attribute called checkpoint_1

Yeah, agreed, intuitively you'd think 'index' would only return integers, but it's really the interpolate behaviour that's doing the work here, you're not actually incrementing the 'index' attribute,

Apologies for the late reply, very helpful thanks, wouldn't think I would have had to do that with an index attribute though.

a monster in a specific spot, it would change an attribute to a specific range around where the monster spawned. The next monster to spawn would not spawn within that range. When it did, it would set

Why are you copying a rule to place in a Prototype? and the original actor you drag out (in this test example do you unlock it before you put the Rotate attribute change in?

You can see my rules in the video (EDIT: I now see you cant really read them but for the story it doesnt matter) and I am not constraining anything. I am sure my rule is working fine as it also does i