Here, now I got our stage 1-2 here for you.
While browsing through our Discord, I realize I have one weakness I can't overcome on my own with my habits: Handling images.
Don't bother asking why, just I'm not sure how to go about dealing with them at all. Attempting to get me used to doing so will be met with stupid amounts of resistance from my own personality. Anywhere images are concerned (
like, oh... our maps with routes drawn on them),
they will be lost in my migration attempts to here. This is where help will be mandatory, and no amount of time on my own will fix that.
In the meantime, rediscovering some tricks reading over old things is fun.
What is
BackJump, anyway? It's a deceleration abuse involving tricking the game into thinking we're headed in one direction, thereby having us "decelerate" to a higher speed threshold during the landing animation. Understood none of that? Good, because I'm still picking apart some of the intricacies of our tricks.
At the least, I can go into details.
The player's direction is stored in 0A1E. If the player's D-pad is pressed in the same direction as the player's momentum, this is updated to match the direction you're headed. For some reason, Up+Left is the only exception to this rule, in which any direction of north, northwest, west, southwest, or south is updated to be northwest if you press Up+Left. If the D-pad is neutral, 0A1E is also updated to match your momentum.
When landing from a jump, the game decelerates Zeke/Julie based on 0A1E. The deceleration is not affected by speed caps, because it's supposed to decelerate you, not speed you up. From full speed south, we can set our direction to the northwest easily because of the weird exception. We can then hold Up+Right to start moving east without losing our northwest direction. With most of the momentum to the east, and a little south, you can alternate between Up+Right and Down+Left in order to trick the game into keeping your direction as northwest. Once we land from the jump, at close to our speed cap east, the landing will magically ratchet our speed up faster to the east.
I suppose I should also talk about the speed cap. The game has your speed and subspeed. When asking if you're going too fast, it first checks your subspeed before checking the integer speed. If your subspeed is below the subspeed cap of your current movement, the game shortcuts the check and says you're good. If your speed cap is 2.50 px/f, and you're traveling along at 3.23 px/f, it just looks at the .23 part and decides you're under the speed cap after noticing it's below the .50 part, despite the integer being well above where it should be. The BackJump is abusing the deceleration direction to push the fractional portion up enough to get us to reach the next integer, then our subspeed is well below the subspeed cap and the game says we're good.
At the start of 1-2, this is what we do to get our speed above 4 px/f. We choose this speed because the camera itself doesn't go faster than 4 pixels per frame anyway, and most of the things we want done are limited by the camera. From there, we can pay the 120 frames it takes to get into Sprint mode while outracing the camera. Then we jump as soon as Sprint is triggered, splash into some water, and trigger Perma-Sprint and dash around 1-2 at a crazy pace. Ah, I need to figure out the mechanics of Perma-Sprint now...
