Generally the difference between softlock and cutscene is minimal, because cutscene is kinda like "glitchless", however, there's only one glitch that differs the two being the softlock glitch at the end of the game, since we don't consider out of bounds a "glitch" but merely a lack of collision in areas where there's supposed to be.
So my proposition, is if we can find an actual glitch in the game, like an item duping glitch, as an example, then we could easily rename cutscene to "glitchless" and softlock into "glitches allowed" (or... something of that nature.)
What about we simplify things and do a "Any%" and "Any% Glitchless" where Any% would be the current Softlock any% and Glitchless would be a mix of the current "in-bounds" + "cutscene" sub-cats without any of the exploits (quick load, out of bounds, dialogue skips). . so basically:
- any% : anything goes, everything is allowed including the softlock at the end
- any% "glitchless": no exploits, no out of bounds, no dialogue skip, no quick load tricking, no softlock . I know "glitchless" is not the proper term regarding the actual nature of glitches, BUT, people usually use that term quite loosely so it would make sense to call it "glitchless" especially if any% has the softlock glitch and the glitchless any% doesn't.
That way you'd have only 3 Any% sub-cats including EOR. I think that's a pretty reasonable suggestion that would satisfy every one and also make the leaderboards clearer and more intuitive.
If we do that then we go back to the conversation of "should we allow the timer to end at a softlock?" and idk about you, but I'm not down for that argument again as we collide so much regarding that issue. Besides, there's only the two of us atm, it'll be fine keeping the 4 categories.
That said though, after our previous discussion regarding whether or not out of bounds was a glitch or not, you had claimed that it was just collision not being coded where it was supposed to be, and that we can't really consider the out of bounds tricks as "glitches", same goes for the quick load, which is... beyond a shadow of a doubt not a glitch.
Furthermore, Your version of glitchless takes out EVERY speedrun trick that we have, which we don't even do for the current method of In-Bounds.
