Is it possible to make custom collisions work with Html5? Or are they working and I am simply doing it wrong?

Make a Boolean attribute,

(Quote)

(Quote)

     Change Attribute game.animate to true

(Quote)

To compare sequences (correct vs. player inputted), I think I used tableMergeValues and a string attribute with something like game.playerSequence..game.playerChoice. So if the player chose 4 and the

1. My game has 10 buttons. Each button is controlled by touch, or can also be controlled via a game attribute.

Edit: keep in mind, each 'trigger' actor in the scenes have a custom actor attribute that is used to read data from the correct row of the table. The attribute is named Row and you need to double clic

2' actor and a second 'pick my location 2' attribute group in the hero actor, both which point to the new table, however its like the coordinates i've set seem to not work and the actor could end up

The phase of the game you can set by a game level phase attribute. Then change the phase from e.g. "desert" to "ocean" when all enemies are defeated. You can even h

Constrain self position y to 20

You can add a "barrier" actor and use the Collision behavior to bounce the player actor away or you can do something like constrain self.Position.Y to max(0+self.Size.Height/2,self.P

If by don't have "do not move" ticked you mean do have "movable" ticked then that won't effect anything as Constrain behaviours are outside of the physics engine, s

button... when press is released...add a change attribute and set game.bestscore to tablecell value of table-x row 1 col 1,....then say post score (bestscore) to leaderboard... then -> show le

Are you moving the non-moveable actor with an Interpolate Behavior? If so, that is the problem. When an actor is being interpolated collisions don't register.

the actor on the first scene that sets the attributes (which obviously makes more seance) and this is where my translation problem comes in, in windows i don't seem to have a way to get to the game c

In the gamesalad file you sent, you're using the constrain attribute behavior on the instance of actor B, not on prototypes.

(Quote)

(Quote)