So as I Said before, there are some functions that I don't quite get. When you used Constrain Attribute for B1 (the orbiting actor), your equation was:

Then if column 1 is not equal to zero then change and check next column. Then if it gets to the 26 column (which there isn't, but the attribute will display 26) then do action I want. That way I shoul

Hmm, looks like formatting got messed up a bit in my previous post, but to clarify, Rule 1 of Loop and Rule 2 of Loop are inside Rule: when attribute self.Trigger is true

Rule: When mouse is pressed and inside, change attribute self.Trigger to true

Not if your changing scenes. The scene will restart when you go back. You need to have a Boolean that when true change the bottles alpha to 0 and in the touch is pressed rule add when attribute self.c

(Quote)

i never used the constrain attribute behavior before... its a great think !

Right off the bat it sounds like you're going to need more general math for the collisions to work properly.

Yep, constrain is your best option.

Just constrain the X and Y to the others actors X and Y. Hope this helps. I've attached a demo file for you.

The timeStamp loop requires two rules, one to check the time and one to check the iteration status. If you wrap both rules in another rule (e.g. when attribute game.startLoop is true), and then add a

created a big square actor and constrain the small blocks to the big square actor, but when i rotate it the big square block seems to rotate but the constrained small red blocks dont rotate at all.

You can use the move to command but you will need to constrain the main character X & Y position to a real attribute so the enemy knows where to go.

You need first to make two 'real' Game attributes . .

Tables are good indeed, but it should also work with save attribute, just make sure you didn't copy the previous save attribute (don't duplicate the attribute) instead drag a new one from the behavior

@chirpingames if you place a constrain for the cam origin in the rule that fires the pause. It doesn't fix it while the pause is on but it does get it to reset the origin back when you unpause.

I'm having an incredibly frustrating problem with the Load Attribute function.

Hi @whompy A more detailed explanation: the Every in the Timer isn't constrainable as such, so you need to retrigger the random rule a different way. So try something like:

Store the current score in an attribute - let's call it 'LastRecordedScore'.

! Yeah i saw the demo and its awesome! Ill constrain it to 2 at a time ! Im currently fidgeting with what tatiang said about the actors.