I'm trying to create an enemy behavior where the enemy will freeze momentarily if they are hit by one of the player's bullets.

Though setting the enemy's "timescale" to 0 works to some degree, I have run into a major unforseen issue due to how my enemy is set up. The enemy's behavior involves waiting for a couple of seconds, firing a bullet, then firing a second bullet, and then restarting the process. Simple enough. To accomplish this, I'm using the System command "wait" to determine the amount of time between enemy actions. (seen below)

<img src="http://i1306.photobucket.com/albums/s571/Matt_Dabrowski/enemy_zpsfe1d9b64.png" border="0" />

The problem is this: Setting the enemy's timescale to 0 does not pause these specific System Waits. So if there is a wait of 2 seconds and I shoot the enemy at 0.5 seconds, this Wait will continue to count even though the enemy is supposed to be frozen. So once the enemy is unfrozen, their next action will occur immediately instead of 1.5 seconds later.

I'm going to attempt my own solutions and I'll post here if I come up with something that works really well. It may just involve completely changing the way I write enemy behaviors (maybe it's not a good idea to be using Waits for this sort of thing). But I'm curious as to how other people have dealt with these sorts of timing issues.

Nevermind. The solution is actually in this post, I just didn't read hard enough :P

scirra.com/forum/ctrl-w-and-other-browser-shortcuts_topic48047.html

While working on my game today, I ran across an issue while testing. It seems that keyboard shortcuts for the browser that I'm using (such as ctrl+x or ctrl+s) still get called while running a Construct application. This occurred for me in Chrome, Firefox and IE. So for example, pressing ctrl+s will attempt to save the web page instead of just performing an in-game action.

I found a couple of postings in the manual and on these forums indicating to me that these shortcuts are supposed to be intercepted:

scirra.com/forum/ctrl-w-and-other-browser-shortcuts_topic48047.html

scirra.com/manual/113/keyboard

Maybe this is better off in the Bugs forum, or is there some sort of known workaround?

Wait, nevermind. It was just an error on my part.. I had something setting the gravity to 3500 on every tic. Nothing to see here :)

Hey all. I'm a bit stumped over something that I'd imagine is a fairly simple fix. I'm attempting to create a "float" move where the player is able to fall at a slower rate while holding the "down" key. The problem is, the following code doesn't appear to be affecting the gravity on the object at all. Normal gravity is 3500, and I'm attempting to set it to 1500. Is there something I'm missing regarding how the gravity property functions?

<img src="http://s7.postimage.org/6en9v2dbv/gravity.png" border="0" />