Have any classic NES games been open-sourced? [closed]

Closed. This question is off-topic. It is not currently accepting answers.

---

Want to improve this question? Update the question so it's on-topic for Stack Overflow.

Closed 10 years ago.

Improve this question

I just played a game of RBI Base开发者_运维知识库ball in a browser window.

That in and of itself strikes me as simply amazing. When I was young, the NES was a magical box, capable of providing hours of enjoyment to young kids throughout the world.

Now, decades later, I'm a programmer. And I can appreciate the programming that went into games that were developed with more primitive hardware just a couple of decades ago. In fact someday, I fully expect that code from some of these games will be enshrined in the Smithsonian.

My Programming Question:

Have any classic NES games (like RBI Baseball) been open-sourced, and if so, where can I find code to study?

Failing that, are there any NES games for which source code is available to study?

I think it would be worthwhile to learn from their example.

For instance:

• Did they use object-oriented programming?
• Did they use design-patterns to keep the code maintainable?

---

No. At least none that I know of (and I've been searching).

NES appeared right after the 1983 video-game crash, the main reason why the market crashed was the flood of bad games, triggering the customers to not buy a single game, because there was no way to know what game was good.

So Nintendo when introducing NES (and all other consoles from the time, like Master System from SEGA), decided that only approved games would ever get released, AND making anything open source ever being a breach of contract with heavy fines, the reason for that is that by not releasing a public API, it would make "homebrews" harder to flood the market.

Today Nintendo is much more easy on the part of allowing the games, see the flood of crappy games on the Wii, but still no console allow you to use their "true" API, to avoid the flooding, there are even a issue when someone used a GPL engine (ScummVM) on Wii, causing trouble, because releasing the source of a game for a Nintendo system is a breach of contract, and GPL demands the source to be released, in that particular case the games were pulled of the shelves.

And no, XNA and PS3 Linux are not really console APIs, both impose severe limitations on what you can do with the console.

Maybe you can find homebrew, or reverse engineered games. But I guess that this is not what you asked.

Also the source of remakes and ports sometimes can be found, but these don't use the console API.

---

Maybe you have since found this, but Metroid (the original, for NES/Famicom) has been disassembled and the code (in beautiful ASM) posted on Romhacking.net.

Direct link.

---

If you're interested in NES programming you should check out Episode 91 - Tengen Reunion Roundtable of Retronauts. (Note this is episode 91 of the original run of the podcast, newer episodes can be found @ http://www.retronauts.com/)

It's basically a bunch of former NES programmers reminiscing about game development on the system (and other retro systems). They occasionally dip into the technical stuff, which is all really fascinating.

---

I've never worked in the videogames industry, but I've read quite a bit about it and I talk from time to time with friends that do, so I'll try to explain a more or less what's the difference between a game and other application, regarding programming methodologies.

The first thing to understand is that a game is a one-off product. It's not like a spreadsheet or a word processor, where you can release new versions improving and extending the previous codebase.

The second thing, is that you need to release the game as soon as possible. Usually, the more time you spend in a game, the worse will it be in comparison with the other games of the time. This is mostly true for PC games, where hardware evolves much faster than in the console world, but still applies to a large extent (games continue to get better even with the same hardware as better tools and algorithms are developed).

The third thing is that usually games need to push the hardware to the limit. So screw all the elegant patterns that would make your code more beautiful and maintainable if they make it to run slower.

So what I would expect after dissecting an old NES game source code is just spaghetti code, most of it written in assembly with plenty of low level hacks tightly tied to the architecture of the machine.

I hope my answer is useful for you.

---

I would recommend looking at nesdev.com if you are interested in NES game development. They have detailed documentation.

---

You won't likely find source for the original games, but there is plenty of homebrew out there and a relatively mature toolchain. As is the favorite answer, google is your friend. But to get you started, here is relatively decent tutorial:

http://www.bestdamnpodcastever.com/millerblog/?p=72 via "The Wayback Machine"

---

NES Games were developed only (as far as I know) in assembler, and I guess the source code is long lost, after those many years.
Anyway, having assembler source code is not so far from machine code, so it may not be too much revealing as it would C or Java code.
About object orientation and desgin patterns, again, it was assembler and the 80's, don't expect any of that.