I'm not very good yet but just got a run with it at 3:39! It looks like in between the right side of the hole and the little green sludge pool is the approximate location of the end goal.
So it happened so fast that I didn’t realize it was a glitch, which in hindsight sounds dumb lol. A new theory after testing: the final area is stored underneath that part of the level. At one point I was trying to replicate the glitch and it activated the last bug’s dialogue before warping me back to the checkpoint.
Bear with me here, as I only half understand how this glitch works.
In my first ever playthrough of the game, I accidentally did this glitch and got to the end early, not knowing until after I watched a speedrun of the game that it wasn't the real ending (though I had my suspicions, as it made no sense). It happens in the hole after the gas station that leads to the toxic-waste-looking area. If you slowly go down the right side, it won't enter you into the room as normal, and eventually you go through the wall and fall infinitely. This will sometimes just cause you to respawn after a bit, but a few times it has warped me to the credits. I think you have to be falling near the entrance of the bottom of the hole; maybe something to do with the game not knowing what entrance you've arrived at and thus defaulting to the credits, though I'm not much of a coder so that is just speculation. This saves a lot of time and I plan on using it in a run!
Admittedly maybe saying "subcategory" is more apt.
Long time lurker here. It's awesome to see a new glitch bring Any% to sub 2:00, but with that said it might be interesting to split the category in half based on whether or not OOB is used. I feel like a lot of people would be interested in watching/running Any% w/o OOB. I don't mean this to discredit the new runs though, they're rad! Just might be a good idea.
The problem is that certain levels start with different types of animations, whereas these animations are the same upon a restart. If you don't start with a restart, the mods have to make a judgement call as to where to start the timer as opposed to being given a consistent starting point.
Nah @Shadowbrine1 I did it on a separate account from the one I beat it on and it still worked.
Has it actually been rejected or just not accepted yet? Certain games take multiple weeks to verify, considering levels of activity for certain games and of course keeping in mind that all moderators are volunteers.
Rip, thankfully I was going to stick to All Wonder Seeds anyway; mine autoupdated and I forgot that was turned on.
Sounds like a fun one, and if not in main categories I think it would make a good category extension.
Once a moderator checks it, if it was wrong it would be rejected. Thankfully a lot of mods will also let you know why it was rejected if it is.
Depend on how long ago you submitted them. Keep in mind the mods are volunteers for a game that’s not as active as some. If you submitted runs less than two weeks ago or so, it wouldn’t be unusual for them not to be verified yet.
I feel like we could do this with IGT on an old save file, just one right after the other and add the IGT together. Same with KO arenas etc
That's probably already going to be a subcategory in the IL for it.
I know this is from forever ago, but would it be possible to make a new category for the new version? It definitely isn't feasible to get a good time in the main category if you're playing 1.0.1. Either that or if the exact time added on by the level intros is subtracted from new runs/added to old ones, but that's a much more time consuming process.
This isn't a major change, but is important for anyone running full world ILs in the future:
"Full game runs will use RTA, and IL runs will use IGT. ILs of entire world may use either; IGT will always be faster in those instances, but will also be more time consuming to time for players and moderators alike, so this distinction is purely for ease of submissions. If a run is submitted that's faster in RTA than the WR but slower in IGT, a retime in IGT may be used if applicable."
I literally only did this because a new WR was submitted with RTA and I really didn't want to put in the IGT lol.
In all seriousness, I think this will be good for accessibility to the category. Again, IGT can be implemented at any time, so I may even go back and retime any runs that use RTA. That said, if you want your run measured in IGT, I suggest doing so yourself and presenting your math to make submissions under IGT easier. This rule may change in the future if I can find an easy way to automate measurements of IGT, which would render the accessibility and IRL time issues moot.