Identifying Luck in Mario Party 7

ZoomZike on Youtube has been working for years on a comprehensive series of videos going through all the Mario Party games, and breaking down what parts of each are a matter of luck, and how many are of skill. Along the way, they also serve as fine guides to winning at them, at least as far as you are able.

They’ve gone through the series, trending longer with each one, for each game from Mario Party 1 through 7 (with an April Fool’s stop over at Advance). Even the shortest is at least an hour, and the most recent one is over five hours. That might seem like a whole lot, but imagine how long it took to construct! These are really deep videos, often with odds figured out through exhaustive, and exhausting, trial and error.

Mario Party 7 is the last of the four Mario Party games that came out for the Gamecube, even beating out the N64 portion of the series by one game. The early MPs were notorious controller destroyers, often resulting in the dreaded white dust of death, a result of ground plastic, emerging from the controller after heavy play. The Gamecube had controllers that weren’t as susceptible to wearing out, and so were better suited for the demanding play that Mario Party provides.

Anyway, here is the video, all five hours and 25 minutes of it:

And, here is the direct link:

Identifying Luck in Mario Party 7 (Youtube, 5:15)

On the SuperGrafx

What is the SuperGrafx? Why don’t we remember it as well as its predecessor, the PC Engine/TurboGrafx 16, with which it was backwards compatible?

Sharopolis on Youtube digs into the system and its capabilities (17 minutes):

As you can tell by the video’s cover image: Amazing Power, No games. The SuperGrafx only had five games released for it throughout its lifetime, pretty harsh for a system that cost around $300 by today’s money. That cost, relative to that of the PC Engine CD, which was also expensive but could play CD games with vastly greater storage, was probably what doomed it. For those really seeking an arcade experience in Japan there was the Sharp x68000, famous at the time as the true enthusiast’s system with a good number of nearly exact arcade ports. It also cost around $6,000 in today’s money, and still $3,000 in then-money.

The system used the same chip as the PC Engine before it, a 6502 variant running at 7 mHz, meaning it was only a 8-bit system. But was that really so bad? The major 16-bit competition for it was the Motorola 68000, another venerable chip at the time that was used in the original Apple Mac, the Sega Mega Drive/Genesis, the Commodore Amiga and the Atari ST. Yet the 68000 also had some more overhead. Many instructions on the 6502 completed in from two to four cycles, whereas the minimum cycle count of a 68000 instruction was four, with some taking up to 20. This, of course, is offset by the 68000’s greater number of registers and ability to work with two bytes at once for many instructions.

Its graphics were essentially two of the PC Engine’s graphics chip, with some circuitry to interface their outputs together. This description brings uncomfortable reminders of people deriding the Wii’s graphics as “two Gamecubes taped together,” but it’s a much closer description of the SuperGrafx’s graphics. But in practice this meant twice the sprites, dual-plane backgrounds, and double the potential colors on-screen at once, while the MegaDrive/Genesis infamously was still stuck with 64.

The SuperGrafx’s failure in the market was one of those inflection points of the growth of video gaming. If it had succeeded then NEC might still be a player in gaming today, and maybe Hudson Soft would still be an independent entity, instead of just another property for Konami to mine for nostalgiabucks.

Lode Runner on the Web

Commodore 64 graphics set

This one is going back to my Metafilter posting history. In case you’re unfamiliar with Lode Runner, I really have to give a short history and primer.

Lode Runner was a game released in 1983 for the Apple II home computer, although ports for several other machines were soon developed and released. Created by the late Douglas E. Smith, it asked players to maneuver through 150 levels of caverns and structures, collecting all the gold (little boxes) on each level then ascending to the top of the screen.

Apple II graphics set

150 levels sounds like a lot, and it really was, but amazingly the game keeps finding new ways to surprise with its small number of level parts and their implications. When player were done with those (or even if they weren’t), Lode Runner included a level editor that player could use to make their own levels.

The ostensible subject of this post is a web recreation of Lode Runner that includes hundreds of levels to play and learn and enjoy. But the site largely speaks for itself in that regard, I think, so here’s some musing on Lode Runner itself, and its history.

So, here is the link. If you’ve never played it before, it’s simple to get into, but very interesting to puzzle over. Every level can be completed, even if many of them seem like they can’t possibly be. Good luck!

Design

Each Lode Runner level is composed of only a small number of parts. There’s the player and the guards that pursue them, of course. There’s normal, “diggable” blocks, solid “undiggable” ground, ladders, overhead bars, trap doors that look like diggable blocks but cause the player to fall through them, gold boxes, and hidden ladders that only appear when the last gold box has been collected.

Diggable blocks, the ones that look like bricks, can be drilled into, leaving a hole, but only when standing next to them and they have nothing above them. That means absolutely nothing: a quirk of the game is that even a set of overhead bars or an invisible ladder in the space above a block will prevent it from being dug.

The obvious use for these holes is to trap guards. When one falls into a hole, it’s stuck for a few seconds until it can climb out. Holes close back up after a short while, and a guard in a hole when it closes up around it are killed, usually to respawn randomly near the top of the screen.

Digging layers down to reach buried gold

The inobvious use is to penetrate into the very walls of a level to collect gold that would otherwise be inaccessible. By digging out a whole layer of bricks, the player can jump into the excavated space and continue digging the next level down.

The other thing about Lode Runner is the AI of the guards. They’re run by a simple program, and are easy to manipulate, but they still have a way of keeping the player guessing when they function as obstacles. When used as tools though, learning how to manipulate them becomes essential. The player can stand on their heads, and because they fall faster than the guards, can even use them as momentary platforms during a fall, to quickly step to one side on the way down.

I don’t mean to dive too deeply into the pieces, their workings and their quirks. A lot of the fun of Lode Runner comes from discovering them for yourself, and being introduced, step by step through the game’s levels, to their implications.

Culture

Back in high school we had an Apple IIc in the back room that we could play with on breaks. I’m not sure what it was there for, I don’t think any educational software was ever run on it, but the copy of Lode Runner on it (already a few years old by that point) was put into heavy rotation, and students would bring their own disks to school to save levels on.

This is an aside, but it demands to be told: one such student saved a number of levels they had labored over to a disk and left it in the room one day. A friend of his, who had thought that student had erased his disk or saved over his own levels, physically cut their disk up with scissors and left it on their desk! It was all in error, but the two’s friendship was never the same after that. The moral: do not be quick to vengeance, theatricality gratifies only one’s self, and in any case, be sure of the facts first. More times in my life I’ve seen someone take drastic steps in error than in rightness. So, back to Lode Runner!

A number of classic Western computer games got a second life, sometimes one that far outstripped their beginnings, when they got ported to Japanese computers and game consoles. Lode Runner was first ported to an arcade cabinet by Irem, then converted to the Famicom by Hudson Soft, where as a prominent early title for that system it went on to sell over a million units, and became a part of Japanese popular culture. From there it reached a number of other systems, including a version for the PC Engine, called Battle Lode Runner, that much later would make it back to the US as an early Wii Virtual Console release. A few other game series that would become cultural fixtures in Japan, adding hundreds of thousands of sales beyond that of their U.S. editions, were Spelunker, Wizardry and Ultima.

Image from MyAnimeList, still kicking after 18 years

At the time Hudson Soft licensed an adaptation of their Adventure Island game, itself deserving of a long post, as an anime production, called Bug tte Honey, which I’m still not sure how to pronounce. It was a Captain N-style setting, where video game players were transported into the game world to have various adventures. It was used as a showcase for several Hudson properties, including Lode Runner.

Lode Runner is a timeless classic, something that we didn’t realize how good it was when we had it. I mean, we knew it was good, but we didn’t yet know how difficult it was to create something so elegant.

For a history of Lode Runner, publisher Tozai Games has a short retrospective and timeline that still survives on the web.

Lode Runner Total Recall