The Making of Super Mario Bros. 3

Via Press the Buttons, a Nintendo Power feature on Super Mario Bros. 3, and the making of the game. From the post: "It's an interesting little article that has largely been forgotten over the years, as I've never seen any of the little tidbits and factoids in the piece resurface in other places (such as the existence of a centaur power-up instead of the raccoon leaf)."

Comments

Mario as a centaur?

[game kid]

I couldn't imagine him galloping on Goombas either. I'd reject it too.

I speak for every Slashdotter when I say the Tanookie Suit kicks ass, and huge portions thereof.

Re:Mario as a centaur?

[IthnkImParanoid]

Don't forget THE SHOE. You will bow before the awesome power of THE SHOE. THE SHOE is unstoppable, THE SHOE is untoppable, THE SHOE makes you irresistible to FAT PEOPLE. Okay, okay, that last thing could certainly be better, but THE SHOE excels in all other areas.

Man, no government would overstep its bounds if we all had THE SHOE. We'd stomp em good.

impossible!

[MasterDirk]

Is it just me, or has the guy in the middle picture down on the third page got some impossibly long arms? Are Japanese programmers extremely well-armed?

Linkage:

http://nintendope.iodized.net/smb3/smb3article3.ph p

404

[cyberkreiger]

Their 404 page is more interesting. :)

Random Question for Game Designers

[Prien715]

So I'm a programmer on PC. As such, I don't like changing dozens of lines of code before testing.

So my here's my silly/ignorant question: how do traditional console programmers test/debug code? Did the SMB3 crew do it the same way it's done today, and if not, how did they do it differently?

I see lots of pens and paper and a couple computers in the photos and a bit about how the graphics are explained but a lot of "how it's done" isn't really explained.

Re:Random Question for Game Designers

[Anonymous Coward]

In general, console programming on all the cart machines was done on a workstation with custom software(I remember reading somewhere that Nintendo used Apple IIs into the early SNES era). They all used assembly, of course. The compiled program was then transferred by data link hardware into some form of memory identical to ROM for test purposes. Debug monitors were also put together by the more sophisticated outfits.

Part of the problem for homebrew developers is that nearly all of this stuff was proprietary, custom-built, and usually became lost to history as soon as the developer folded. None of the systems were particularly HARD to make this stuff for with the right electronics knowledge and some reference material, but there wasn't any getting around it either, which is why 80s game development has such a mystique to it. Nowadays everyone develops with "off-the-shelf" kits and software, so it's substantially less interesting.

Re:Random Question for Game Designers

[MyDixieWrecked]

Programming for the NES actually seems quite fun compared to traditional programming. I've been toying with the idea of actually sitting down and learning it.

I've got a pretty intricate knowledge of the NES cartridge format, since I wrote a tool (based on openly available information) for modifying the graphics. (http://nesromtool.sf.net/)

Also of interest is http://grandtheftendo.com/ since the guy wrote tons of custom software to program that and has some pretty interesting things to say.

Re:Best game ever

[snuf23]

All I can say is:

I love the power glove, it's so BAD.

Uh that and "He touched my breast!"

Amazing Staff

[TheoB]

From the Article: "The team that produced Super Mario 3 consisted of over TEN PEOPLE..." My God. I mean, can you imagine ordering take out for TEN PEOPLE? Must have been a management nightmare.

from the article

[Flunitrazepam]

"The team that produced Super Mario 3 consisted of over 10 people and they worked over a 2 year span".

Maybe if design teams these days consisted of "over 10 people", there would be better games!

New game in the works...

[rlbond86]

I'm still waiting for this "Super Mario Brothers 4" they talked about.