I've just thought of a solution - I'll make a quick project and post it here - but basically we just need to copy the angle-of-contact value into another attribute to save it - so when we destroy the

If you do this then the offset (the attribute called 'angle-of-contact') will jump to 0 when the first satellite is destroyed - which will make the replacement satellite suddenly jump to a new positio

For instance... Change attribute: self.Size.Width to game.Screen.Size.Width

Here's the same file with Move replacing Constrain Attribute.

I have an attribute that counts the seconds and when it gets to every 10th interval, it advances the day. The same process can be completed by clicking on a "next" button. These fu

"The only solution i can think of is to make a self.attribute on the 2nd digit actor (integer) value, and constrain the self.image to that instead of the equation, then constrain the self.att

Could this be an issue with an attribute?

The only solution i can think of is to make a self.attribute on the 2nd digit actor (integer) value, and constrain the self.image to that instead of the equation, then constrain the self.attribute to

That's strange. I replaced your constrain behaviors with Move behaviors (move 0 direction 300 speed; move 180 direction 300 speed) and saw no gaps. But if you have it working, that's the important t

thx for the answer! helped me a lot - and i now i also know that it isnt the best way to use constrain attributes (Image)

It is easy to use random(min,max) in the equation editor. Then you can just hook it up with an attribute and then some rules that tell the actor to do certain things when that atribute is equal to any

Yeah.. you want to be careful with using 'Constrain Attribute' behaviors that reference themselves, as these can be glitchy and you can create glitchy loops.

Constrain Attribute: self.Position.X to (where ever you want it to land on screen, I did 500) +self.Size.Width /2- self.Size.Width

for the third digit (hundred) im using constrain self.image to (floor(( game.Score )/100))..".png"

Constrain Attribute self.position.X to self.position.X-10 seems like a really strange and unreliable way to move an actor. Why not just use a Move behavior?

constrain attribute

Change the constrain x behavior

Constrain the origin y will sort it out.

One method would be to have Global Attributes, let's call them left and right.

Sounds to me like @tatiang is almost there with what he wants. You would do like he said with each block having a rule inside where when the ball is on it it changes the game attribute to tell the ima