Here is the current sound actor setup (minus my attempt at a magnitude attribute).

One problem is that game.Time is a reserved attribute name and that attribute counts up from zero. There is no way to change that value. It's only possible to reference it.

just off the top of my head, the logic i would try is having a global attribute/variable to activate the behaviour that is either an integer or boolean (eg. activateChase or something like that and se

I want a rule that makes it so that if my actor is idle for 10 seconds, an attribute triggers an enemy to pursue it. I have it setup so that it seems to work ok but I would rather have the logic place

trying to completely remove a value for an attribute, it is completely screwed up. If anyone can assist me, I tried emailing him to no avail.

Create an attribute. each time you enter a scene- change its value to 1,2,or 3 depending on the scene.

This is getting really disheartening.. so after piecing collisions into the scene section by section (since GS can't read a multi-sectional json collision file) I now find that my sprite pops through

(Quote)

this is the code for the collisions json. far as I can tell it looks correct but then again I am in over my head with this lol

However for it to be 100% correct you'd want to use this script but remove the last comma on the end block since no further collisions blocks occur. There is probably a better way to write this. Maybe

@sinbot Can you post the JSON code here? I remember the export script for exporting from PES by default does not handle multi-polygonal collisions correctly, but it can be modified to do so. Here is a

Create Game.Attribute called Pause (value = 0).

For now, this problem is solved using the visible attribute, even when opening a new screen, the loading scene is visible and then moves away automatically. Will show the video once done.

on your player, either add camera behaviour, or constrain the x any y of whatever actor you use with the camera to your player’s x and y. also bring the camera area right in to the middle of the scree

the logic is this, when it is jumping in air, make some attribute to be true. If it is true it will not collide with the platform, so it will cross the platform, but when you release the button and it

Constrain your players Y position to a game attribute.

* HTML5 engine parity (except for performance). i.e. fonts should render the same, collisions should work the same. Aside for some minor bugs, it should work the same as the native engine.

attribute- poorly designed, under game or actor tab, there is a search box, just right of it is the + sign.

oh never mind i figure out the attribute now. just need the platform

where is the book and the device setting and where can i declare my attribute or variable lol. just start playing