So I would question whether the attribute values you are using are exceeding the range of your table (or becoming ≤ 0).

no problem. the basic concept is within the moving platform have a change attribute at the start to set the linear velocity x to whatever speed you want to move (- speed if moving left to start). then

In the 10 second video below, you see how I select a Change Attribute while the Layers is open. Of course, the actor that contains this behavior is selected in Layers. When I want to delete this behav

@Japster's right but if you're not wanting to do that, you could Loop over Table and add the indexed cell to a sum attribute.

same conditions as in the other thread to stop your player moving. eg. have an integer attribute called levelState and assign values for before starting, game on, level fail, level finish. set the rul

You'll want to make your own timer. Google custom timer gamesalad and you'll see many examples and videos. You can round the time to milliseconds attribute by using roundTo(game.attribute,3).

have you set the volume to the right attribute?

Add a global attribute called whatever you want to. Say the player can move and jump only if that attribute is 0. If the player touches the gem, set that attribute to 1.

     Change attribute self.position.Y to self.position.Y+100

To make things simple, i have 2 squares. One is a player and the other is just a square platform which the player jumps on. How do i make my player teleport, say, 100 pixels up if attribute player col

* Reduce the usage of constrains, timers, and loops that happen often and concurrently ( this one isn't as bad as it used to be).

There are many way to do it, I can give you one which might not be the best practice but, you can constrain the player X and Y to public attributes PlayerX and PlayerY , then create 2 invisible actors

No, it doesn't matter. If you prefer, you can just use an integer whenever you need a boolean. It can just as easily be 0 or 1. And you can use the expression 1-game.attribute to toggle the value sinc

is still false, store that value in an index-attribute rowIncorrectAnswer1 or whatever and then change the cell value of that false boolean cell to true and repeat the process, until attr.rowIncorrec

change attribute PlayerWidth to the width of the player actor

2) ? change the image’s attribute self position x

Create a boolean attribute called game.touchingWall. Then, in the player actor, have these rules:

[Case2]The alternative is picking a random row out of 5000 and changing table cell values of 10 columns and setting multiple attributes for each question answered during runtime, which should in theor

game.actorDestroyed is false by default, so at the start of the game as well. And you're right, as it is, once an actor is destroyed it sets the attribute to true and keeps it like that.

Make sure you're selecting the attribute (game.PlayerId) from the attribute browser menu instead of just typing in its name.