Ow i figure that later out but now with the ball and start button i placed the otherwise attribute but now it goes slowly down?

you need to make a rule so when the ball reaches the finish line reset the drop ball attribute to false so when it goes to the other scene it wont drop

change attribute self.originalX to self.position.X

I realy need save/load template's to explain me the save & load attribute .

If you need to move a group of actors, you could have those actors check a game attribute for a certain value and then create a rule to move the actor 100 pixels if that attribute condition is true.

create a new actor (a white box), drag it into the scene, open it up, apply a constrain attribute self.Position.X to mouse.Position.X and self.Position.Y to mouse.Position.Y

Why would the newly spawned actor/player be immune to collisions with any other actors onscreen at them time of death/spawn? All are part of the same layer and spawned relative to that layer in the s

@uptimistik didn't work. Constrain attribute? that behavior?

(Image)

I have used an attribute to keep the position x and y (+ a bit to get in corner) & rotation to big box

The concatenate function is ".." (without the quotes) between two strings. You could manually combine the rows by doing Change Attribute game.typing to tableCellValue(game.Table,1,1

@RP You will need an attribute that sets that ball's action (that button press) back to zero/false each time you reset, or start that scene. Otherwise the memory and logic will think, "okay t

@gyroscope - But wouldn't you have to know in advance which word was in which position? I still don't see a way to compare text attributes without having a way to parse text such as firstLetter(game.

You will need an attribute that sets that ball's action (that button press) back to zero/false each time you reset, or start that scene. Otherwise the memory and logic will think, "okay time

Hi, as @tatiang says, there's no way to do this with text attributes alone; you'd have to use more attributes. You could use a table as well, I'm thinking.

Certan behaviors like interpolate or a constrain to mouse will over ride collisions this may be you're problem.

* physics collisions occurring between objects that have no collision rules or [collide] behaviour

One way of limiting the max size would be to create two new attributes (maxHeight, maxWidth). Then at the top of the behavior list, use two change attribute behaviors to specify the the maximum. (For

I`m testing that:

Create a self boolean attribute called "Stop".