Mario’s 2D games have naturally evolved over the course of 40 years, introducing new power-ups, enemies, and worlds that have captivated generations of players. Yet beneath all the innovation, there are fundamental mechanics that have remained constant since the Italian plumber first appeared on screen. He has always been able to jump with precision, consume mushrooms to grow larger, and grab fire flowers to gain the ability to throw fireballs at enemies. These core abilities have become so ingrained in gaming culture that it’s difficult to imagine Mario without them. However, one essential mechanic that players have relied upon since the very first Super Mario Bros. game actually started its life as an unintended bug in the original code.
The mechanic in question is Mario’s ability to dash or run across small single-tile gaps without falling through them. This feature, which allows players to maintain momentum and cross tiny openings in platforms, was never intentionally programmed into the original 1985 Super Mario Bros. game. Instead, it emerged as a happy accident during development. The game’s physics engine, designed within the severe memory constraints of the Nintendo Entertainment System, calculated Mario’s position in a way that occasionally allowed him to briefly hover over small gaps when moving at full speed. Rather than fixing this quirk, Nintendo’s developers recognized its potential and decided to keep it in the final release.
The Birth of a Beloved Feature
Nintendo’s legendary game designer Shigeru Miyamoto and programmer Takashi Tezuka were known for their pragmatic approach to game development during the 8-bit era. Working within the NES’s limited 2KB of RAM and 40KB cartridge space, every byte of code had to serve a purpose. When bugs emerged during testing, the team would evaluate whether fixing them was worth the precious memory required. In the case of the gap-crossing mechanic, the bug actually improved gameplay by making the experience feel more fluid and forgiving. Players could maintain their running momentum without being punished by pixel-perfect precision requirements on every small gap they encountered.
This approach to game development—embracing beneficial bugs rather than eliminating them—became something of a tradition at Nintendo and throughout the gaming industry. Similar stories exist for other iconic game features, such as the combo system in Street Fighter II, which also began as an unintended programming quirk that players discovered and developers later refined. The gap-crossing ability in Mario games has since been deliberately included and refined in every subsequent 2D Mario title, from Super Mario Bros. 3 to the modern New Super Mario Bros. series and Super Mario Bros. Wonder.
Legacy and Impact on Game Design
The decision to preserve this bug has had lasting implications for platform game design. It established an important principle that would guide Nintendo’s approach to difficulty: games should be challenging but fair, and mechanics should support player momentum rather than constantly interrupting it. This philosophy is evident in how modern Mario games handle player movement, with generous coyote time (the brief window where players can still jump after walking off a ledge) and other subtle assists that make gameplay feel responsive without being punishing.
Game historians and developers often point to the original Super Mario Bros. as a masterclass in intuitive design, and the gap-crossing mechanic exemplifies why. By allowing players to dash over small openings, the game encouraged speed and risk-taking rather than cautious, slow-paced platforming. This created a sense of flow that made Mario games instantly addictive and infinitely replayable. Today, speedrunners and casual players alike benefit from this four-decade-old bug, often without ever realizing that it wasn’t supposed to exist in the first place.
Expert Opinion: This revelation underscores a fascinating truth about game development: some of the most beloved features in gaming history were never intentionally designed. As game preservation efforts continue and developers share more behind-the-scenes stories, we’re likely to discover that many mechanics we consider essential were originally accidents that simply felt right. This serves as a valuable lesson for modern developers—sometimes the best design decisions involve recognizing when a mistake actually improves the player experience.
