HexxWizard wrote:

I know I'm being a weirdo, and I've been on Scratch for about 5 years now, but do you know how to create a new post/question through forums?

dem_bot wrote:

A part of the problem probably is that it doesn't take in account that the level moves after or before the collision checks, so changing scroll x and y only has an effect on the script the next frame.

EAE_animator wrote:

dem_bot wrote:

A part of the problem probably is that it doesn't take in account that the level moves after or before the collision checks, so changing scroll x and y only has an effect on the script the next frame.

So… is there a specific order that'd work?

define Try Move (X) (Y)
change x by (X)
if <touching [wall v] ?> then
change x by ((0) - (X))
end
change y by (Y)
if <touching [wall v] ?> then
change y by ((0) - (Y))
end

change x by (() - (speed_x))

dem_bot wrote:

EAE_animator wrote:

dem_bot wrote:

A part of the problem probably is that it doesn't take in account that the level moves after or before the collision checks, so changing scroll x and y only has an effect on the script the next frame.

So… is there a specific order that'd work?

The best option is to use maths for collisions such as in my 2D map engine. This allows you to also have some visual effects such as making the camera smooth instead of the player locked in one place, is very reliable and often less laggy.
An easier, but often buggier option is for the player to not do the movement, but the level instead. As FLAMINFOX711 described.
A third option is to have the player sprite move during the frame (so when you change scroll x also change x) and move back after calculating the collisions, but that is prone to float roundoff error and requires some handling for when the player starts the frame in the ground.