Diablo hackers uncovered a speedrun scandal
A long-standing Diablo speedrun record has been exposed as a spliced, tool‑aided fake, prompting renewed interest in how speedrunning communities define fair play and verify legitimacy. Commenters dig into the technical forensics used to debunk the run, the role of RNG seeds and segmented runs, and how categories (glitchless, TAS, any%) are used to keep comparisons “apples to apples.” More broadly, they contrast speedrunning’s “anything goes if you’re honest and follow the category rules” norm with traditional sports and question the value and rigor of external arbiters like Guinness World Records in gaming achievements.
Nature of speedrunning “ethics” and norms
- Many comments say the core norm is simple: “don’t lie.” Any exploit is fine if it’s fully disclosed and the run is correctly categorized.
- Debate centers on whether this is a unique “ethics” or just standard competitive honesty shared with most sports and society.
- Some distinguish between ethics (cheating vs honesty) and norms/rules (what categories exist, what tricks are allowed where).
Categories, glitches, and TAS vs real‑time runs
- Games usually have multiple categories: any%, 100%, glitchless, “no major glitches,” etc., each with detailed rules.
- Communities draw lines between “major” and “minor” glitches based on fairness, difficulty, and watchability (e.g., Super Metroid, Ocarina of Time).
- Tool-Assisted Speedruns (TAS) are separate: they use emulators, savestates, and scripts to push theoretical limits, serve as proofs of concept, and often inspire later human routes.
- TAS itself has rules (input files must beat an unmodified game; no hacked ROMs or spliced videos). Hardware TAS devices are used to show runs on real consoles.
Verification and cheating detection
- Serious communities require video, seeds/saves where applicable, and frame-by-frame scrutiny.
- RNG-based games often require posting the seed; fixed-seed or “fastest known seed” categories can emerge.
- Cheaters frequently rely on splicing, external tools, or impossible RNG; detection often mixes tooling, reverse engineering, and statistical analysis.
The Diablo scandal and rule ambiguity
- The Diablo run mixed segments from different seeds/versions, used impossible item drops and boss damage, and likely edited game state (e.g., fireball damage).
- It was submitted as a segmented run, which was allowed; the controversy is how segmentation was used.
- Older Speed Demos Archive rules banned hardware cheats and mid-run media tricks but were vague about offline save editing and continuity between segments; later rules explicitly ban file edits and require continuity.
- Some argue the run clearly violated the spirit of the rules even then; others note the written rules were looser at that time.
Spectatorship, fun, and community dynamics
- Categories are also shaped by what’s fun and humane: e.g., banning tedious RNG abuse or ultra-fragile tricks, allowing turbo to avoid RSI, or preferring glitchless for watchability.
- Many see speedrunning as “community vs game” as much as runner vs runner, with researchers and TAS authors valued alongside top competitors.
- Some dislike glitch-heavy runs and watch only glitchless; others enjoy game-breaking TAS and arbitrary code execution.
Guinness and meta‑commentary
- Guinness’ involvement in gaming records is widely criticized as low-quality and pay-to-play.
- Several people treat speedrun cheating exposés and verification deep dives as a kind of technical drama: a “soap opera” mixing human psychology, statistics, and reverse engineering.