nesdev.com

DRW, you seem to be willing to discount the fact that it is easier to write and develop modern C++ than old C (which is the type of C you necessarily have to write using cc65). IDE support is way better. You get true namespaces, you get templating (which can make for writing more readable code). If ...

Using all the advantages of C++ that can't be easily recreated in C (object orientation, inheritance, templates, comfortable data types in the standard library like dynamic arrays) cannot be used in NES games anyway since it costs too much ROM space and CPU time. What about metaprogramming and temp...

If you're looking to start making an AI, one approach used in (relatively) modern games is creating state machines. I imagine this would work on the NES, but I haven't seen any concrete examples. For example, you can have an "Idle" state that transitions into a "High Attack" state when the opponent ...

Personally, I've written my dev tools in ruby (I am mostly looking at GB right now, though, if that makes a difference). I use Ruby at my job, so the biggest reason I've selected it is familiarity. In the past, I've used Python extensively for this sort of pipelining, because I find it to be quick t...

You may want to consider making a simple state machine, instead. Especially if you're going to have multiple screens (inventory, main menu, etc.), a state machine seems like it would make things simpler. Consider a case where you have multiple pause screens (a la later zelda games, one screen for st...

One thing that I like to do with version control is set up the ability to recreate any ROM on a fresh box (habits from work die hard). I'm not sure how much art you are generating, but if you're using version control for a single project, I am pretty sure that GitHub will not complain no matter how ...

It really depends on what you mean by "winning" and "losing" For example, games that require you to do things in a time limit may be considered "unwinnable" and "unlosable" Like Fruit Ninja where you have to slice fruit, but if you choose not to, it isn't really a problem. You could argue, though, t...

Espozo wrote:

NYMike wrote:Game Stop sells SB Melee for 54.99, Ebay is around 55ish as well.

Blame competitive melee making a resurgence the past few years. Popularity of the game has almost never been higher, despite it being out for 15 years.

I saw this - it looks really interesting.

Also interesting is the fact that most of the game was written in C. I was under the impression that anything of this relative complexity would've required more hand-tuned assembly.
I'm eager to look through the source, though.

So wait, in a nutshell calling an enemy is like this: enemy *e = enemies[i]; //this declares the pointer (*e).function(e); //this calls the function That is one way to do things. Personally, I prefer to do something like this: enemy_update(enemy *e) { switch (e->type) { case ZOMBIE: zombie_update(e...

This looks really neat! Any chance we will see a ROM to play it?