Doom Eternal Developers React to 27 Minute Speedrun

Storyline (as referenced in the video)

• The subtitles don’t go into full plot details, but the discussion focuses on Doom Eternal’s campaign progression across multiple levels.
• It culminates in major encounters, including Marauders, and ends around the Crucible/final moments—particularly the sequence being shown and/or criticized for presentation.

Gameplay highlights & what the speedrun shows

The featured run is described as a 27-minute “current world record” style speedrun. It’s claimed to be “no exploits” by the runner, though the developers identify multiple glitches/exploits.

Key moments discussed

• Extremely fast navigation / skip behavior

  • The runner appears to bypass intended interactions or triggers—described as “shortcut” style behavior.

• Combat execution

  • Developers praise how the runner “murder[s] everything” and stays effective even while routing around areas in non-standard ways.

• Super-jump / momentum-glitch style movement

  • Uses rapid jump inputs combined with movement on slopes/ledges to leverage jump-extension-like behavior.
  • Builds velocity and then launches off geometry.

• Weapon-wheel / mouse-wheel “fast jump” setup

  • The explanation claims that using the weapon wheel can alter game time / allow more jump inputs within a short window.
  • This effect is described as especially exploitable at very high frame rates.

• Checkpoint / trigger manipulation

  • Developers describe instances where the runner “activates triggers” and/or relies on checkpoint behavior to reload or reshape world state, enabling shortcuts or unintended access.

• Weapon module merging / cheat-modified behavior

  • A more technical segment describes a scenario where:
    • a cheat enables/unlocks or forces weapon module behavior,
    • the runner switches weapons/levels,
    • switching back causes weapon modules to merge.
  • Result: one weapon can fire with another weapon module’s speed characteristics (described as Precision Bolt becoming Micro-missile speed).

• Environmental and world-interaction glitches

  • Repeated mentions include:
    • clipping through geometry,
    • using skyboxes/multiple skybox loads,
    • and frame-rate-dependent physics.

• Ballista-related movement/combat

  • Developers highlight Ballista jumping, compared to older rocket jumping / Quake3 bunny hopping.
  • They praise its mobility as “cool.”

• Cutscene/sequence skipping talk

  • Notes include skipping a cabin/cinematic, and handling cases where content is presented as unskippable or awkward to watch—implying speedruns try to minimize non-interactive beats.

Strategies / key tips mentioned (developer explanations)

The developers (and the explainer in the video) focus more on how glitches are achieved than on conventional route strategy.

Glitch-focused “how-to” points

• Super jump glitch (described as repeatable)

  • Stand on a slope or fall off a ledge
  • Spam jump input within a short time window
  • Rely on a system that allows jump while not fully touching the ground near ledges (framed as “mechanical jump extension”)

• Weapon wheel used to manage time / input density

  • Use the weapon wheel to slow in-game time
  • This creates space for more jump inputs in a short interval
  • At high FPS, it’s easier to exploit for momentum building

• Momentum building then release

  • Wait for velocity buildup, then let go/release into the intended trajectory off ledges/platforms

• Trigger/checkpoint exploitation

  • Some skips rely on teleporter/activation triggers and checkpoint state changes so the game loads sections/areas in ways not intended for normal play

• Weapon module merge scenario (cheat/code described)

  • Enable a cheat/activation that changes weapon module availability
  • Switch conditions/levels with the cheat toggled
  • Switch back to cause module merging, producing mismatched firing behavior (Precision-like firing at Micro-missile speeds)

Developer discussion: balancing speedrun fairness vs. bugs

The developers joke about “not stopping speedruns,” but they discuss whether:

• records should be invalidated after a bug fix,
• the community expects a consistent “level playing field,”
• an “old vs new” challenge mode (a toggle idea) could allow both bug-tech and intended play to coexist fairly.

Gamers / sources featured (mentioned at the end)

• Sam ID (the speedrunner; described as performing the world-record run)
• IGN (mentioned with a thanks at the end)

People credited/mentioned in the video

• Marty Stratton
• Hugo Martin
• Jerry Qian
• Evan (Eubanks)
• Evan with Jerry (collaborative mention)
• Peter (appears as “Sam and Peter” for the glitch explanation segment)
• Tony
• Brandon
• Danny O’Dwyer (suggested source/person to follow for process documentation)