yeah thats what i did, i duplicated a actor in the creator, so in my second copy i deleted this self attribute that i did not need, so when i click play my whole game got a mess, i went back to check

hi all, i create a actor and created like 20 self attributes on it, each will change a game.atribute to self attribute, for ex.

2) Scoring! Let's say I know how to display Scores as a game attribute set as integer. The question is how to put that score again after every level? You know something like a Report Scene after each

No, constrain the 1pxl boundary to the specified 'custom collision' you want; there's not specific number for that, it completely depends per actor (not its size, but where in it you want the boundary

(Quote)

(Quote)

Those pink lines are where the collisions are taking affect, not the white lines by GS. The problem witht his is that the pink boundaries have to be constrained, and when there are a lot of them, it t

(Quote)

You have to constrain some custom 1-pixel wide 'custom collision' boundaries, so that they can get hit within the zone of your custom shape. Does this sound clear? If not I can elaborate; it's much le

2. Then if distance is < Constrain self.rotation to

Thanks, and I'm thinking you could set random attributes for these rules if you want a computer opponent?

Constrain mouse.self.position.x.y to lightsaber.self.position.x.y

Seriously though, can anyone give me an example of attribute rules please?

My guess is i have to do a rule that will constrain the camera somehow.

First i make 2 actors. Then i make 2 attributes in the scene to actor 1's X and Y.

Thanks! What type of attribute should I use?

well.. you just use a change attribute behavior and then say change attribute self.color.(red/green/blue) to x amount.

Edit: Thanks anonymous moderator. What you didn't know was that I set up a rule so that when actor receives event 'title' 'is changed', then change boolean attribute 'startWorldDomination' to true! &a

260 game attributes .. May of been better doing that in a table!

My guess is i have to do a rule that will constrain the camera somehow.