Reacties
Antarcticabringupyourpost2 hours ago

ok that is a solution

Also @Sir_Farcelot it would be good to know what browser you are playing and what OS you are using.

JS is somewhat depedent on Browser. But the replay code is completely dependent on JS math and string handling. The differences between JS in browser are stuff like what the react command does and whether consts are valid. These won't affect the replay code system. Scratch-Vm, the turbowarp-compiler, the scratch-renderer are also OS independent so it cannot be a probably with them. The only thing that isn't is HTML. But the replay code is stored in a div tag. But Div tags are not OS or browser dependent.

Sources: I will add the rest of these later, I have to go to class now. https://developer.mozilla.org/en-US/docs/Web/HTML/Element/div#browser_compatibility

Sure, Appel may be different across platforms but that isn't really a defense. Turbowarp's compiler is not different based on OS. In the case of Michael that was a graphical error which could probably be chalked up to HTML differences cross browser and platform.

The fact that he is able to do inputs past the lel ending is enough proof

speeeedy vinden dit leuk
Antarcticabringupyourpost15 days ago

i mean many times you jump on a goomba to get more height. like you jump let go because you don't want a full height jump and then land on a goomba and then press the jump key again

Antarcticabringupyourpost15 days ago

this jumps 14 times

Antarcticabringupyourpost18 days ago

I will include hundreths from this point forwards

Antarcticabringupyourpost1 month ago

The timer in game is fully accurate. But you are just running appel slightly faster.

Antarcticabringupyourpost1 month ago

Does that make sense?

Antarcticabringupyourpost1 month ago

@Sir_Farcelot, I have discoverd a discrepancy in the way you did your calculation. See the display in appel only updates every 3 frames which means that if I get 18.9 that could be 18.90, 18.93, or 18.96. If DapperScratcher got say 16.0 on one level and Michael get 16.1 on the same level that doesn't mean the difference is .1 because if DapperScratcher got 16.06 and Michael got 16.10 then the difference is 0.06. We can't fully account for this in the calculation but if we assume that Michael got the lowest possible time for each time he gets (e.g. 16.0 we assume 16.00) and Dapper gets the highest (e.g. 16.0 we assume 16.6) then that would turn the scales in Michael's advantage and he would have the better total time. So it isn't impossible for Michael to have a better run. But this doesn't mean Michael did get a better run.

LionCoder10 vinden dit leuk
Antarcticabringupyourpost1 month ago

well my wr was short

Over bringupyourpost
bringupyourpost for my evil plan
Lid geworden
5 months ago
Online
today
Runs
13
Gespeelde spellen
Appel Category Extensions
Appel Category Extensions
Laatste run 18 days ago
9
Runs
Appel (Scratch)
Appel (Scratch)
Laatste run 1 day ago
4
Runs
Gevolgde spellen
Appel (Scratch)
Appel (Scratch)
Laatste bezoek today
63
bezoeken