When designing your characters try and keep them as square or as round as possible it make the collisions more accurate. If you look at my character (profile picture) you will notice he is almost rect

The main problem is creating the Custom attribute in part 4 which starts at 04:10 & then linking it to the moving platform upto 07:15

I have up to 5 targets on screen with self attributes of 1-5 - however if say number 3 and 4 were destroyed this would only leave targets 1,2 and 5 available (LIVE)

and while those positions change the rule will re fire and recheck every time it changes. you have access to every actors x and y position as an attribute in each actor. you have to use the expression

What you will want to do is Constrain the camera origin to a certain number of pixels ahead of your actor position.

Then just remove the timer from the above screenshot and wrap those Change Attribute behaviors in a When Touch is Pressed rule. If that doesn't work, is your actor present on the first scene?

Part of the actor can't be collidable. You'd need to either constrain the sword to stay near the guy, or wait until gamesalad gets joints at some point.

is what got re-sized) is correctly detecting collisions at the new size. The bullet object, however, may only detect collisions with the targets *original* size. This means if you make the target o

Change attribute: self.randomRowNumber to random(1,26)

menu, so certain actors pressed just change attributes, and other actors pressed change an attribute, THEN change the scene. The problem is that once you press one actor (button), the game thinks yo

Should I constrain player bottom and enemy bottom to their y positions. So player dies on collision when playerbottom < enemybottom

When the user swipes, change a game attribute like Swiped to true. When actor lands, change Swiped to false. Only allow a swipe when attribute Swiped = false.

Also, Is it recomended to store this total (coins) in a table in stead of a general attribute?

Create a self.attribute in the actor and name CanTouch or something and change it to true. Then create a rule that says:

That way, as the self. (or game.) loop counter attribute increases, the table row number increases and the loop spawns an actor at each table row's x and y values. The y position field just has the s

pause everything for a second, this changes an attribute. As that attribute changes back to zero again, they start respawning.

Couldn't you just make a game.attribute called last time or something. Maybe constrain it to the real time. Then when the game is reloaded just do an equation like current time - last time. Then you

Do I create a global attribute and insert the loop counter? I never used loop before, so no idea where to apply it?

One work around is to constrain the position of a rectangle to that of the character in your game, and make it a little smaller and use that as the collider, and not the character itself.

(Quote)