Surely this is a high priority bug!? "Collisions don't work the same on HTML5".

Also, as I brought up a year or so ago, collisions ("Overlap or Collide") do NOT work the same as on the other platforms, meaning my game doesn't work properly.

You're welcome! Just to explain a bit further, since I offered this as a private message, the problem was that your rules were evaluating the value of a keyboard input attribute right after the keybo

Basically I didn't make a waterproof logic for my answer attribute, which made the game keep running through the rules and thereby executing the wrong interpolate behaviour as well.

Constrain Linear Velocity X . . . to . . . 50*(Mouse X - Self.X )

I tried to set the attribute of an object where if the pieces on either side (horizontal) colors change to black (or white) if it is the opposite color it will then change to the same color as in reve

Make an integer attribute called game.myTimer. Then add these rules to your timer actor:

There is no way to automate boundaries or do per pixel collision. However you can use "custom collisions" and make your own pretty easily with a tool like Physics Editor or Physics B

When I try to interpolate an actor, or make it appear from alpha 0 to 1 through change attribute, it also affects another actor. Which it shouldn't since the ruleset at hand don't apply to the 2nd act

I don't see anything wrong with your logic but to be sure, you may want to post a screenshot. Beyond that, I would recommend turning off rules one by one (make a separate backup of the file before yo

will increase both the correct and wrong score attributes. However, if it is wrong it will only increase the wrong score. I have stared at this logic for awhile trying to figure out what is happening

You're right about the Reset Scene behavior not resetting game attribute values. Likewise, copying a table will reset the table cell values but won't do anything with game attributes such as game.sco

I created another table apart from my category tables, and attached the copy table behavior to the "category 1" button, but it still isn't restarting my table. I am not too sure if I

If you want to record what row the player was on. Have a different attribute for each category that stores the row number. And have a Main Attribute called Row_Count. (If you want to reset, you would

(Quote)

to correct or wrong scores, and changes the attribute to another random question (picture) within the table. I have a menu button on the page and when the user presses it, the scores will be returned

(Quote)

Stupid? No. Inefficient, Yes. Build a single scene instead and use actors that can be modified (typically through the use of actor "self" attributes or even game attributes). Wit

I'll quote GS here , these are all the updates they gave us so far in order.

Another option is to just check the position within the actor since you already have access to its self.Position.X (and Y) attributes: