Have you tried using arrays for this? You could always define the positions in a 2d array, then you could always have the sprites set to whatever position was stored in the array, that way whenever the array changes, so does the characters position: https://www.scirra.com/manual/108/array

Funny thing is, I'm not aware that using the jump-through at an angle in the way I have in this example is causing any glitches, I just literally want to be able to force the "fall through jump-through" faster than the platform engine can try and put the character on the jump-through.

Really amazing engine, love the way it's a nice behaviour, tight and tidy. This could potentially take over the crown of Sonic Worlds in the indie sonic dev community.

I never understood why they got rid of this, why couldn't it just have sat there, collecting dust, being useful to whoever needed it?

But I'm still trying to figure out why they dropped java like a hot potato without even a fallback plan.

I've updated the title in an attempt to make it easier to understand my issue.

Started a new topic as I'm working on a new method that would harness the power of the Jump-Through for stairs without having to enable it or disable the jump-through behavior, which is a benefit to multiple platform movement-based characters based layouts. Here's what I have so far: https://www.dropbox.com/s/5ja6iexdx8i1y ... .capx?dl=0

It *works* if you very carefully walk slowly by nudging the player over the staircase, somehow this misses the tick that calculates the jump-through and allows the character to walk past the stairs. If I could get that condition to always work faster than the jump-through, therefore being able to have the jump-through behavior enabled if the character falls onto the stairs/walks from a platform onto the stairs OR has the up-arrow pressed, it would replace the method of enabling and disabling the solid behavior (of which you can see has been disabled in the events, which is the old way of doing it)

So what I'm asking is, how can I get the check that enables falling-through the jump-thru to work faster than the jump-through behavior is?

Here's an incredibly rough clone of what I'm using, the duplicate events are there for customizing if you want different lags on jumps and falls independently, at the moment all direction changes are the same, and you can change the "0.3 seconds" to adjust how much lag (faster reflexes) is there before the "camera operator" catches up with you. It basically adds a more human feel to the camera, since a real operator wouldn't know when you would change direction, but would be able to track you if you continued at a steady pace: https://www.dropbox.com/s/4f825i1vxzwcs ... .capx?dl=0

Okay, I think the problem is addressed here: new-feature-request-solid-ignore-select-solid_t79689

and: selective-certain-solids-in-platform-behavior_t148723

Which leaves me trying to create a new stairs function using jump-throughs. Here's an idea I had which, in theory could work if I could "fall through" to loop faster than the platform engine registers: https://www.dropbox.com/s/qtgg5itcficxi ... .capx?dl=0

Setting "fall through" for the player on every tick isn't good enough though, I need something that is faster than the platform engine can register the jump-through platform. If you walk slowly through the stairs, you can see the player just slightly goes up then keeps walking, if you run at full speed, the player skips over the "fall through" action. Is there a way this technique could be harnessed to create proper a staircase?

Sorry, this is the correct example, this has a random picker for the enemy to go upstairs on it's own random choosing and I corrected the keyboard condition, but you'll still notice the enemies stair function is screwing up the players: https://www.dropbox.com/s/1uwivi2bj1wgm ... .capx?dl=0

Or should I say, how do I enable and disable collisions for platform-movement based sprites, I'm using enable/disable solids on the staircase so it acts like a jump-through platform, but I want the enemies with platform functions to have their own enable/disable solid switches. Here's my example: https://www.dropbox.com/s/1uwivi2bj1wgm ... .capx?dl=0

You see how the enemies own solid disable/enable triggers are screwing up the players behaviors? Is there a way to have the interaction with the staircase have it's own individual settings per character/enemy?

Is it the same in desktop Chrome? Both are based on v47 now.

Are you sure you haven't disabled vsync in nVidia control panel/Catalyst control center/any other graphics settings? Changing settings there has been known to cause problems in the past. By default Chrome should have pretty good v-sync by now.

Yes, it looks the same in Chrome. Here's my settings from my nvidia panel (it does the same when set to integrated):

I have no idea why it's calling it russian roulette!

I'd list all weapons in an array (weaponList), together with their current power (I'm guessing 1-3 is the power for each weapon, right?) so I could add as many weapons as I needed later. Also, I'd use a variable (selectedWeapon) to store which weapon is currently selected.

So I could use the following code to switch:

On <key> pressed >> Set selectedWeapon to (selectedWeapon + 1) % weaponList.Width

When shooting, I'd just check selectedWeapon and the power of that weapon in weaponsList, and create the blasts accordingly.

Do you have an example of this kind of idea that I could compare my own to? I've never used arrays and I think mine looks okay but I'm having a bit of trouble keeping my head together with it