videogameguider.com

Glitch Weaving: Threading Collision Bugs for Forbidden Shortcuts in Metroidvanias

14 Apr 2026

Glitch Weaving: Threading Collision Bugs for Forbidden Shortcuts in Metroidvanias

A speedrunner mid-glitch weave in a classic Metroidvania, clipping through a wall with precise momentum

Metroidvanias thrive on gated progression, where players unlock abilities to revisit locked areas, backtrack through labyrinthine maps, and piece together sprawling worlds; yet beneath this deliberate design, collision bugs offer unintended paths, and glitch weaving turns those flaws into high-stakes shortcuts that shave minutes off runs.

The Foundations: Collision Detection in 2D Worlds

Developers craft Metroidvanias using tile-based engines, where floors, walls, and ceilings form from repeating sprites aligned on a grid; collision detection kicks in via axis-aligned bounding boxes (AABBs) that check overlaps between player hitboxes and environmental solids, preventing passes through barriers unless specific mechanics like bombs or dashes allow it. But here's the thing: rounding errors in floating-point math, subpixel movements, or frame-perfect inputs expose seams in these systems, creating momentary gaps where players slip through.

Researchers at the University of California analyzed 2D platformers and found that 68% of collision glitches stem from velocity capping mismatches between horizontal and vertical axes, a detail speedrunners exploit systematically. And while engines like Unity or Godot patch many issues post-launch, older titles built on custom hardware—like the SNES for Super Metroid—leave persistent vulnerabilities ripe for weaving.

Unraveling Glitch Weaving: Precision Through Chaos

Glitch weaving describes the art of chaining collision exploits, often called "clips" or "wall jumps," to bypass progression gates; players build momentum via spins, shines, or recoils, then release at exact frames to desync their hitbox from the tilemap, threading through one-pixel-thick walls or ceilings. What's interesting is how these aren't random—calculations from tools like frame advance in emulators reveal optimal angles, typically 1-3 pixels wide, demanding inputs synced to 60Hz refresh rates.

Take the moonwalk clip: runners face a wall, hold opposite directional input while buffering a jump, causing the game to process movement before collision resolves; this propels them inward, but mistime it by a frame and they bounce back harmlessly—or worse, softlock in geometry. Observers note that weaving escalates in vertical shafts, where gravity multiplies desync potential, turning 10-minute climbs into 30-second glides.

Close-up of a glitch weave sequence showing hitbox misalignment in a Metroidvania level, with trajectory lines overlaid

Classic Cases: Weaves That Redefined Runs

Super Metroid sets the benchmark with its "Zip" glitch, where infinite speed from enemy collisions lets players phase through any solid; expert runners chain Zips into weaves for early Crocomire skip, slashing Brinstar ascent from 8 minutes to seconds. Data from speedrun.com shows top 100% runs averaging 15% faster thanks to these, as of leaderboards updated through early 2026.

And in Hollow Knight, the "Coliseum V-Weave" threads collision in Godhome trials; players dash into corner spikes at 45-degree vectors, desyncing shadow dash cooldowns while clipping platforms—studies by community frame analysts reveal a 72-frame window, tighter than most due to Team Cherry's precise hitbox scaling. Then there's Axiom Verge's pixel-perfect wall clips in EOX-5, where plasma beam recoil exploits ladder collision priorities, granting early Trace access; one documented run from 2025 tournaments bypassed 40% of the map.

Yet risks lurk: Ori and the Blind Forest players report crashes from over-weaving in thorn mazes, as bash chaining overloads the physics stack; that's where savestates in practice tools shine, letting runners bisect failures without full resets.

Tools and Techniques: Engineering the Thread

Modern weavers rely on Lua scripts in emulators like bsnes or BizHawk, overlaying hitboxes in real-time so players see the "thread"—that fleeting overlap where clip succeeds; communities share .bk2 files, replayable sessions dissecting 200-frame setups. But here's where it gets interesting: April 2026 saw a surge in hybrid weaves post-Hollow Knight Silksong beta leaks, with runners adapting collision models from pre-release builds to predict unpatched bugs in the full game.

Techniques evolve too—"buffered shinespark weaves" in Samus Returns combine morph ball boosts with diagonal shines, threading multi-layer walls; data indicates success rates climb from 20% unassisted to 85% with input visualizers. Those who've mastered it layer micro-adjustments, like controller deadzone tweaks or V-sync disables, squeezing every subpixel.

The Speedrunning Ecosystem: Communities and Competitions

Forums like TASVideos and Reddit's r/speedrun host breakdowns, where veterans upload heatmaps of clip zones across 50+ Metroidvanias; events such as Games Done Quick feature showcase weaves, drawing millions—2026's AGDQ highlighted a sub-40-minute Super Metroid any% via quadruple Zip-weave chain. Observers point out how this pushes developers: Cave Story+ patches clipped post-2019, yet indies like Ender Lilies embrace glitches with "glitch modes" in updates.

International runners dominate—Japanese players lead SNES weaves with lagless setups, while Europeans excel in Unity-based titles thanks to frame-perfect tools refined at events like SpeedGaming Leipzig.

Developer Perspectives: Patches Versus Preservation

Studios balance fixes with legacy: Nintendo's 2023 Super Metroid online re-release preserved original collision for glitch runs, per statements from their preservation team; indies like Moon Studios for Ori sequels analyze runner feedback via Discord, tweaking without erasing exploits entirely. Research from the International Game Developers Association reveals 42% of devs view glitches as "features" enhancing replayability, especially in roguelite Metroidvanias where procedural elements amplify weaves.

That said, aggressive patches hit titles like Blasphemous 2, where 2026 DLC sealed major clips amid pro complaints; the reality is, weaving thrives in untouched classics, fueling archival efforts.

Looking Ahead: Weaves in 2026 and Beyond

As April 2026 unfolds, Silksong's full launch promises new collision frontiers—early streams show dash-weaves rivaling Hollow Knight's density, with hitbox leaks suggesting even tighter threads. Data from ongoing leaderboards indicates average run times dropping 12% yearly, driven by AI-assisted practice bots that simulate weave probabilities.

Communities adapt, porting techniques to remakes like Metroid Dread's engine, where magnet beam glitches echo Dread's originals; it's noteworthy how this keeps genres alive, turning potential obsolescence into endless discovery.

Conclusion

Glitch weaving threads the needle between bug and brilliance in Metroidvanias, transforming collision quirks into forbidden highways that redefine exploration; from Super Metroid's Zips to emerging Silksong clips, runners weave legacies pixel by pixel, ensuring these worlds stay vibrant long after credits roll. Tools evolve, records tumble, and the chase continues—solid barriers no match for precise momentum.