Canada@Vwasprobablytaken I confirm, no weightless mod in sight :P
You're playing a tad too conservative lol, you can go quite a bit faster than this :3
Update: I just sent this to BlastMagic
Oh wait, I think we both hadn't realized there's a distinction between bellket and broomket Mak does bellket (so do I these days) and the strat you showcased is broomket Both are valid yet different Admittedly, only slightly different, but at least as different as leftket and shalket Really feels like that deserves inclusion.
Also the difference there is even more slight but pogo bellket (mak strat) vs pull bellket (my strat) ''pogo off the bell tends to be weak and slow'' (from what I recall) (your words) Very true, that's the advantage of pull bellket, but on the other hand, it's riskier because if you miss the bell it's practically guaranteed to immediately end the run.
Here is the bucket guide: https://scratch.mit.edu/projects/875520598 Pretty much everything meaningful is mentioned in the desc. Whatever isn't specified, if anything, is indeed just preference :) Personally when I was at my prime I was using right bucket when grinding for PBs and bonket when more casually, or needing more consistency. These days I'm more into bellket but I may switch back sometime, who knows lol. The best is to be able to efficiently choose between different strats, depending on how your boot jump went.
Good amounts of snake are subjective anyways. Nothing is better or worse than anything else, except having too many or too few categories
?? I'm pretty convinced it was 51.700 when I verified it lmao
It's heavily recommended that you put the code in a scratch project yourself, share it and use the link of that project as video proof. So that only one person has to do it instead of all viewers xD
No worries :P Nice run btw! And good luck
In the replay too you have to set Backwards to yes (mod menu page 2). Also, you'll see the timer is stuck at 0.03 - not sure what happened. I looked at the Player Y in the replay code it doesn't start high enough (like 3 pixels too low). My guess is that the code order is wrong but that's surprising lol. Anyways, starting with a savestate higher (to make sure there is at least one full frame before you trigger the time) should fix everything for next time :P
