In before this somehow becomes my fault and someone wants to have a go at me for not reading. #rooThink

Every time that the discussion comes up someone brings a non-issue to the table to try to justify its exclusion.

If one can find a better (or rather more consistent) way of achieving runs without glitches and then defining the rules-set for guaranteeing glitchless runs, I'm sure people would be more receptive to the category. ...define glitches clearly and reasonably and bring up a defined set of rules that allows for fair comparisons between runs...

Clearly someone didn't read and just wants to pick an argument ¯_(ツ)_/¯

Hi, don't mind me, Computer Game Development student coming in.

What is a glitch? Well, it's defined as an error made by the programmer/developer that is not as catastrophic as a full bug (these tend to soft- and hard-lock the PC/console!), but it is passed by Quality Assurance to allow the game to make it to Format (i.e. getting the game published). They are generally non-critical (they won't blow up the game or fry your hardware) and so they are never normally fixed.

Why is this definition important? Well, it's because Bethesda. Doom is not a stable game by any stretch of the imagination. I have been able to perform railboosts (by accident) at <60 FPS. Granted, the main speedrun category ramps the framerate up to make the glitch easier to perform, but the mechanics of the game allow it at the normal FPS as well. This is an issue with no quick and easy fix, and pretty much invalidates any attempt at a Glitchless category without some hefty arbitrary constraints. Playing the intended route without performing exploits (e.g. clipping out of bounds) is doable, but that does not get rid of the fundamental glitches. (Difference between a glitch and an exploit - a glitch is something unintended by the developer, an exploit is normal intended behaviour manipulated into doing something unintentional.)

Is it possible to run without encountering any glitches? Possibly, but in order to do so you'd probably have to make some very detailed rules about how to do the run. I believe this is the main issue with the Glitchless category - if the rules, aren't well defined, the runs themselves lose credibility. If one can find a better (or rather more consistent) way of achieving runs without glitches and then defining the rules-set for guaranteeing glitchless runs, I'm sure people would be more receptive to the category. As I understand it, the general complaint was that certain runs included glitches and then dared to call the run glitchless anyway, which is a nonsense.

In short - glitches bad, Doom has glitches, glitches != exploits, get way of glitchless to be good, HungryTag, better defined rules, everyone happy, we all get back to speedrunning and stop writing long forum posts like this one. mic drop

Best forum this year, 5/7 perfect.

Is this thread a snuff film now? cirThink

We have an auto-splitter tool that pauses during load screens that is used to help process the times for in-game time. You can post either time, but generally it's the in-game time that determines the run's speed.

Time is on the start of the Spider Mastermind GK.

Good example of Animation Cancel is when you first gain control of DoomGuy - in Any% runners fire the pistol to stop a slow animation from triggering whilst activating a panel by the door; in Glitchless, you would not be allowed to stop that animation.