breaks everything, instead of it just missing a attribute or 2 like it was

work, but it doesn't, then try to change one attribute, or rule, or anything, and then change it back to the same thing you had it on, sometimes this will fix the problem, thats really all i can say.

i pretty much have an actor that i have moving around, and i want to set boundries for my game, so i made walls and said bounce with collision, the probul is i cant have the actor bounce when it hits…

Call me stupid but can some explain to me what attributes actually do and they're used for. Especially in terms of making rules with the attribute browser.

set an attribute in the game attributes so it can be switched, then make a rule in your actor based on that attribute

Make 2 real attributes call them positionX positionY or whatever you want.

Constrain self.Rotation to vectorToAngle(self.Motion.Linear Velocity.X,self.Motion.Linear Velocity.Y)

Constrain self.Rotation to vectorToAngle(self.Motion.Linear Velocity.X,self.Motion.Linear Velocity.Y)

If it's an actor attribute, it can only be altered and used by the actor. If it's a game attribute, it can be altered and used by any actor. I usually use actor attributes when I'm going to spawn mu

When working with attributes, does it entirely matter whether I make them a game attribute or an actor attribute?

Attribute: GameTimer = 10

Hey I have been trying to work something similar out for a long time. Will this work to constrain a couple actors to the bottom two corners of an actor like tires on a car?

I've multiple instances of the same actor on my scene. I wish to change single instance attribute (color or rotation) when I click on it.

If canMove = true move to .... if overlaps or collides with block change attribute canMove to false.

Try having a rule when the actor collides with the obstacle change attribute self motion linear x to 0 and self motion linear y to 0

Try having a rule when the actor collides with the obstacle change attribute self motion linear x to 0 and self motion linear y to 0

thing. I guess I would have to make a boolean attribute for every orb and save if it's been taken or not. Any easier solution?

You can setup a game Attribute will say move and in all of your movement rules make game.move being true required and then setup in your character when overlap collide with obstacle Change attribute g

add a game attribute in the scene inspector/game/attributes

Change attribute (in behaviours)