Super Mario All-Stars Random Debug Mode

We are told by The Cutting Room Floor this interesting fact. Super Mario Bros. 3 has a debug mode that activates when a specific memory location contains 80 hex, that allows the user to grant Mario any powerup. In normal play this never activates because the cartridge initializes all of RAM to 0 as part of initialization. But the version of the game included in SNES Super Mario All-Stars, while it closely follows the original’s logic in many ways including including debug mode and its criteria for activation, doesn’t initialize memory when starting up. When the console boots up, its RAM contains random voltages that can be interpreted as nearly any value, and there’s a chance that there’ll be 80 hex in memory location 7E0160, and enable the debug mode for Super Mario Bros. 3.

While ordinarily this would be a 1-in-256 chance, some consoles are prone to favoring specific values, so some units will turn on debug mode more often. As a result a legend developed that certain Super Mario All-Star cartridges are special debug versions that accidentally got put into retail boxes and sold.

Supper Mario Broth made a short video (about 1 1/2 minutes) explaining how it works in crudely animated form:

As it turns out, Mario All-Stars has its own debug modes for each game in the compilation, but the one for Mario 3 is different, and buggier. Meanwhile the original debug mode for Mario 3 remains, intact, buried in the code, waiting for the value 80 hex to appear in its magic location to unveil itself.

Why Is NES Strider So Janky?

There are a number of NES games that feel like they’re held together with paperclips and chewing gum. Some of them are almost endearing for their glitchiness. When it comes to janky NES games, a few that I tend to think of are those made by Micronics (who implemented Ghosts N’ Goblins, which has an awful frame rate) and Athena (where one boss has a death animation that causes it to flip through many of the sprites in the game).

A company that usually did a lot better with their internally-developed games was Capcom, makers of Mega Man, 1943, Bionic Commando, and all the Disney Afternoon games from the time, all of which have slick 60 fps update rates and smooth animation. One game they made of which that is definitely not true, however, is NES Strider.

If you’re only familiar with Strider from the beautiful arcade version, you might wonder what even NES Strider has to do with it. It’s not proper to say Famicom Strider, because Capcom never released it in their home territory, perhaps because they were too embarrassed to.

Other than the first stage being set in generally the same fictional location in Russia (even if it doesn’t look at all the same), its story has absolutely nothing to do with it. Jeremy Parish looked at it (and remarked on its glitchiness) in an episode of Metroidvania Works from a couple of weeks ago. Some people, like Kid Fenris of the self-titled blog, actually likes it, although acknowledges its many issues.

Behind the Code, one of the best game internals series on Youtube, had a look at the implementation of NES Strider. It’s an interesting 15 minutes to my taste, but if you want a tl;dr, NES Strider often doesn’t make its framerate target, and instead of slowing the game down as most games do, it plows ahead forward into the next frame, leaving the incomplete data in its update buffer to be copied into the PPU. This causes the individual hardware sprites that compose enemy characters to sometimes have only one of their coordinates updated, or even causing data remaining from previous frames to be copied over.

Why does it does this instead of just slowing the game down? Possibly the coding was so crappy that it would have caused excessive slowdown; the scene chosen as an example in the video has the problem occur when there’s only two basic enemies on the screen in the game’s first area! Not the best engine on the system there Capcom.

The Garbage Sprites in Strider (NES) (Behind the Code on Youtube, 15 minutes)

David Wonn’s Game Glitches

We’ve been feeling a yen for the Old Web here lately, where someone with a particular area of interest and the time and effort to tell the world about it could create a site that could attract hundreds of readers, and become the hub of discussion around that topic.

The internet seems to have largely left the era of the personal obsessive website behind, in favor of videos and social media. I find this a huge tragedy, as the flat HTML page is still a very useful method of communication. Straight static HTML doesn’t rely on backing scripts or content management engines so there’s a lot less to break, and there’s a much smaller attack service for nefarious entities. (If one wanted to make a site like that there are even tools to help you out, like the Python package Jekyll.)

David Wonn’s glitch site is legendary in speedrunning circles, having been mentioned in various Youtube videos as the source of some prominent tricks. (One of them is this video on Mario Kart 64 tracks that have not yet been broken.)

The last update mentions having trouble with Yahoo’s hosting. The site has several dead links to Geocities sites, and I believe it was one of the sites lost in the Geocities Shutdown, part of Yahoo’s long, slow deterioration. The current version is a mirror hosted by kontek.net, which also maintains several other vintage gaming sites. Thank frog for them!

Why did it stop updating? Well it had a good run; it lasted eight years, and anyone’s allowed to move on from their old interests. I’ve said before of other sites and it applies to this one as well, it’s a miracle that it persists, and I hope that it lasts a thousand years.

David Wonn’s Unique Video Game Glitches

In NHL 2022, Secret Base makes the most violent NHL team of all time

EA Sports says you must accept this. EA Sports says this is your god. Your malformed football god.

Jon Bois has been an internet favorite ever since Breaking Madden, his series where he strained mightily to upturn all of the assumptions that the Madden football games make to present reasonable game experiences, and in so doing revealed those games are made out of cardboard and paste.

Modern EA has long been on the outs with me, but discovering that this company that has locked up the exclusive rights to make official games for multiple sports, for decades now, makes terribly buggy, broken product, has caused me to see them as a force for evil in the world. If you want to play with NFL teams, it’s either the Football Fetus (see above), or nothing. I know, capitalism sucks, but this is a particularly egregious example. But that’s beside the point.

(The only reason I’m not linking to an explanation for what the above thing is, is I’m saving it to post later. Keeping up a daily gaming blog is a marathon, not a sprint, and there is no reason to wind myself.)

Jon Bois and sitemate Kofie Yeboah now hold their game breaking adventures over at Youtube channel Secret Base, which also has a homepage. They mostly work in the medium of video now, which I can kind of understand? Youtube ads probably pay more than web page banners. I still miss their text output though. But that’s also beside the point.

What is the point? They have a new video where they tried to adjust the stats on an AI team in NHL 2022 with the sole purpose to get them to the end-game shootout, which apparently happens in the NHL in the primary season if overtime ends with a tie score, as often as possible. In the process they incidentally cause and win an epic number of fights and eventually take the Stanley Cup. And in the process, in typical EA Sports fashion, game bugs cause players to slowly skate with the full speed animation and sometimes put a spurious extra player on the ice in overtime for no discernible reason. Here it is:

Watching these videos and reading their old articles almost make me want to forget about my long-standing disdain for both EA Sports and pro sports games in general and get one just run crazy experiments like this. But only almost.

Video: GoldenTorizoCode

This is a channel on YouTube of various Super Metroid glitches and weirdness. A lot of it is pretty deep magic, and they tend to throw around evocative terms like Murder Beam, Chainsaw Beam, and even Spacetime Beam. Those links are useful in understanding what in the burning acidic heck the narrator is talking about. Knowing and caring about the gameplay of Super Metroid is, of course, required for comprehension.

But if you do know about Super Metroid, and you do care about learning about some of the more ridiculous glitches in videogamedom, then you’re in for something that is a reasonable approximation of entertainment.

The name of the channel refers to a debug feature left in Super Metroid’s code, that can be pulled off without hyper-obscure tech, although in the process it’s likely to crash your game. When you enter into the room of the of the bosses, the Golden Torizo, if all of the face buttons are held down during the transition, your equipment will be overwritten by a number of items. The code gives you all of the beam weapons in the game, which is good, but also turns them all on at once, producing the afore-mentioned Murder Beam, which will likely crash the game, not good. The opposite of good.

Here’s links to a few of these videos: an unused enemy called a Bang, activating “God Mode,” and how to obtain and use the end-game weapon Hyper Beam against bosses. It is some pretty intense geekery, but that’s sometimes what flows out of the faucets around here.

Video: The History of the A-Button Challenge

It’s now been some years since pannenkoek2012’s “A-button challenge” videos hit the scene, introducing the internet to hyper-obscure Super Mario 64 glitch concepts like the HOLP and Parallel Universes. For the record, those videos can be seen here and here, and if you haven’t seen them before, you are in for a ride. Videos like the Walls, Floors, and Ceilings series (37 minutes, 32 minutes and 37 minutes) are not only interesting in their own right (to people of a certain mindset) but are a good introduction to concepts for writing your own 3D platforming engine.

These videos are all ultimately in service to the A Button Challenge, a long-running quest to try to complete Super Mario 64 with a few presses of the A button as possible. What may seem like a completely spurious pastime, it turns out, has been an obsession with some players since not long after the game first came out!

The origins and history of the A Button Challenge are explained by a surprisingly long and deep series by YouTube user Bismuth, totaling over four hours of video and, as I write this, isn’t even complete. I’m not sure how many people would be interested in watching so much on such a niche endeavor, but pannenkoek’s videos have been popular enough that I figure they must be out there, and some of them may even read this blog, so here goes!