EsperantoYoutube embeds are weird like that but that doesnt realy seem to be happening for me .. Sometimes itll do a thing where it's ridiculously low quality for the first few seconds and then it goes to 1080p tho
Yeah that'd be fine! Things like wallhop macros definitely wouldn't be allowed but a keyboard having support for alignment key wallhopping is pretty standard so that'd be fine
No worries about the time stuff. To be honest I dont realy understand how its set up either. Ive been meaning to clear it up and make it make more sense for a while
I guess I'd have to see a run that demonstrates this to have proper context but rn I don't see any problem with that
wtf was i even doing having those runs in glitchless anyway
@BlastingDuck So like hears my thought process regarding this .
On this leaderboard there are a lot of things considered glitchless that are functionally the same thing as what we consider glitches. Take, for example, any ladder flick, but especially ones like what happens around 3:55 into this run. This is, down to the motion and timing of the jump, the exact same thing as a wallhop, but since there's a stud of air between the two parts, it's interpreted as a ladder flick and so it is placed in the Glitchless category. I bring this up because this "contradiction" in the rules is completely intentional; it encourages better competition and higher quality speedrunning than if ladder flicks weren't allowed in the category.
With that in mind, what benefit is there to separating runs based on one stud of one highjump? What unfair advantage could a runner possibly gain from this, especially when wallhopping the end by accident is quite literally slower anyway? It could be argued that the advantage is in the fact that it's slightly easier to do the highjump this way, but I really just don't see that as enough to warrant separating it from other Glitchless runs. That seems no more valid to me than if runs were separated based on whether or not you climbed the ledge at the end of a 12 stud jump. It could be argued that the advantage is in the time the runner hypothetically saves based on the assumption that they would not have landed it had the stud at the top not been there, but that also isn't very convincing to me because like . It is there tho. If the wall was designed any other way then it would be different. But it's not. Idk I see it as my responsibility to encourage fun and fair competition on this leaderboard and separating runs this way only really stands to do the exact opposite of that
Would additionally like to clarify that this only applies to walls up to 12 studs tall. If it can't be highjumped normally than wallhopping it would in fact be considered Glitches
Well idk if any one could find a way to cut out 3 seconds from this run it would be you
solw month hadnt even arrived yet ... what did he know
an emulator's just like . an application that lets a device run games designed for another type of device . It comes up alot more with console games in speedrunning I think but it's completely irrelevant to roblox. Speedrun.com just displays that when you go to submit a run no matter what
LOL i was womdering about that . I thought maybe it was lilke a stylistic choice or something
Yea it's not normally this bad, it's because someone submitted 300 runs the week before among other things . I should have your run verified by the end of today
