[Major vs Minor lag]

Lag can be used to,

1- Pass through game triggers without activating them
2- Buffer HS
3- Perform cube fly

Both of the currently relevant methods of lag, F11 and Alt+Enter, can be used for any of these purposes. Let's define these methods as sources of "Major lag", since they lag the game for a significant number of frames. In lengthier categories, namely 120 signs, the time loss associated with using a Major lag method is negligible. However, for the time critical categories like Any%, seconds (and even milliseconds, especially in the case of the Warp subcategory) are vital. The current WR for Any% Warpless uses a previously undocumented source of Minor Lag, F9, to buffer hub storage, as it is a more time sensitive method for lag than any of the Major lag methods.

[F9 - source of Minor Lag]

By default, F9 is bound to "shot". This is a default bind in UDK (https://docs.unrealengine.com/udk/Three/TakingScreenshots.html) used to take and save screenshots. After pressing F9, a very small amount of lag is created (a very substantial amount of lag may be experienced on the first press of F9 each time the game is started).

F9 works on both Linux and Windows (untested in OSX). There is enough lag to buffer HS. This method of buffering HS is more difficult than using any of the Major lag methods. The current WR for Any% Warpless uses this method (0:46)

There is enough lag to pass certain triggers without detection, but not all. For example, beams that activate/deactivate doors can be skipped without detection. However, there have been no successful attempts to bring cubes through the particle field leading to The Chase using this method.

Notes:

-The game's screenshot directory will fill with actual screenshots, one per press of F9 or use of the "shot" command. However, if playing the game in Linux, there are no files output. -F9 has not been tested with Cube Fly.