its at the end of this video, is this glitch documented at all? never seen it before
The reason for it not being documented is it's extreme unlikelyness of happening. I think.
I've seen a lot of portal glitches but never this one. Maybe ask the subreddit and Discord?
@REDACTED_O5_13 that is a portal boost, some people in the discord can give you a better explaination but all you really need to know is that it sometimes just happens and is basically random.
its also allowed in glitchless as long as its accidental and you dont save time from it, but if you wonna be safe just reload a save
yeah that sometimes just happens, it's pretty fucked and run killing
THIS GUY DID A GLITCH IN A GLITCHLESS RUN BAN HIM NOW
"run killing" mfw i can make a quicksave:
if this could be replicated consistently, would save ~5 seconds on oob and like ~30 secs on inbounds runs
it would most certainly not save anywhere near that time, it would literally lose time, have you seen top level oob and inbounds for 11/12?
@italvera yeah nice idea but in the oob route i literally cannot remember any place in the run that would save time at all and certainly it would not save 30 seconds in inbounds, look at a run and try to find places where consistent portal boosts would save time (there is actually a setup used in nosla and inbounds for a portal boost in 01 but thats already used)
Can confirm, it just happens sometimes. It can be devastating when it happens in the middle of a perfect run.
Starting now and currently being grandfathered, all console runs will be manually retimed with load times removed. This process will be redone by the verification team anyway, so don't worry about doing it yourself when submitting. Massive shoutouts to Tactix1 for doing this basically single handedl