I added this to a new thread of it's own since i believe it's abit more important than virtually anything i've discovered before other than the Brejik skip, i'll continue posting smaller finds on the ''Possibly new skip, quality of life stuff too!'' post as i think it's best not to flood the entire forum board with minor routing finds.(later edit, i have made up my mind on the matter, i'm against using the glitch in runs personally due to the glitch most likely being more effective on certain machines than others to a much higher degree than basic save teleports.)

While i'm still against using this in actual runs i have found out a few minor things about the glitch that i'll put up for documentations sake, it doesn't actually need save buffering of any kind and can be done straight up with regular movement as long as you right click the window bar, the distance is based off how how long the game has been ''paused'' with longer periods shooting you further into the distance than a short one, the actual area seems irrelevant in distance traveled, having tried in lower city apartments and the dune sea and the result is the same. Also it seems that enemies are not affected by the glitch causing them to stay where you initated the windowed teleport, still locked on to you they will start chasing you to the ends of the map if you untill you kill them.

I think I've seen something similar on other machines, namely laptops, using full screen mode. If the game is minimized during a save or while just running you can teleport long distances. Aleck47 either demonstrated this or just mentioned it during his RPG Limit Break run, and I've seen another example before too.

I don't really know how to handle it as far as timing or rules are concerned. As the timer is programmed now, minimizing the game will make the timer start back up because the game is no longer in focus. I don't remember how right clicking on the game's Title Bar affects the timer. I know I've accidentally right clicked it during runs since I use mouse movement a lot.

This is obviously banned in Glitchless, but I don't know about Any%. I don't think we need to require runners to play in fullscreen mode. The game comes with a config tool (swconfig.exe) in the install directory that was used by the original release to put it into windowed mode. The Steam release doesn't seem to honor all of that tool's options, so we have allowed runners to force windowed mode by editing their ini file.

We may need to reconsider this stance if it becomes a larger issue. I'd like to hear other runner's stance too, so feel free to state your opinion. Should this be banned in Any%? Should runners be forced to play in Fullscreen? Should alt-tabbing be allowed while your character is moving?

Well, i play the game in windowed, my main concern was with the ''not being able to do it off a regular install'' part(ie making messing around the ini file a straight up necessity, which i'm really not a fan of compared to how we just do it for comfort, which goes too close to modding the game for my taste.) but if it's possible to do in the physical release i don't really see any issue with it.(Later edit: Also it seems to be irellevant as to how much memory usage is being used after testing the glitch a bit more so my earlier arguement of it being better on some machines most likely isn't relevant.)