Give the prototype actor an attribute (e.g. boolean) and a rule that checks to see if that value has changed. Ten have a rule that changes that attribute when a key is pressed. If you need the trigg

Hello in my game i have it where when a actor collides with another actor -1 of an attribute called lose. Lose is st to 3 and when it gets 0 I interpenetrate the camera to go up. How ever i have anoth

I'm not going to rotate the actor so yes I could simply constrain to a global X & Y....i'm just wondering if there is a more efficient thing to do or is that the most efficient. Thanks for you

Holy Mary! For a more calculated and smoother change attribute process Barbara would have to interpolate into Tony or vice versa.

Otherwise . . . Just make two game level attributes, Master X and Master Y, and constrain everything to them.

. . . for exactly this kind of thing, but I think 18 constrains might start to get a little cumbersome ?

**(actually 'change attribute' has also just become free, he was killed by one of those robot spider things, may 'change attribute' rest in peace)***

around, what is the most code efficient way to constrain the position of all actors to one set of shifting X & Y real points. Thoughts? Ideas? Is there a way for me to snap some actors to ot

(Quote)

(Quote)

Change Attribute: game.enemychallenge to 0. In other words, I had to reset this attribute so it will begin to spawn again, since I have a Rule - > Change Attribute: game.enemychallenge <

My code is not working, and I have isolated the problem. It seems that this rule is not working: [if (self.rotation) > 0] I wondering if the attribute self.rotation is relative to the actor ins

Ok, so every 5 seconds this attribute is changed to a random number between 1 and 3.(Quote)

That's causing the problem, the change size attribute seems to stop collisions being detected.

If mod(game.attribute,2) = 0

If game.attribute%2 = 0 then trueDivisible by 3:

I've attached a demo file where I've stripped the timer/every method down to its basics, relieved it of all its chores, attributes and as much code as possible, so it can run as unhindered as possible

I'll do a long version but quickly. It does use a few self attributes, but it makes it pretty dynamic.

If you want to stick with the constrain:

If you have the time (I know you are busy) could you post an example of what you mean by ". . . counter attribute with a Timer behavior with 1/FPS for the every timer . . . " ?(Quote