Bacon and Games

Tag: nes

Name That Scrambled NES Game

I’ve always been a fan of the little corners of the internet or App Store that put my nostalgia to the test, so this is my contribution to that part of the web. I’ve taken 100 well-known Nintendo game screenshots and scrambled them up. Can you name them all?

Play Name That Scrambled NES Game here.

NOTE: This was just a quick project so it probably doesn’t work in all browsers (maybe not at all on mobile). If you run into issues, please leave a note in the comments or just play it in Chrome :)

Free Sound Effects Generator for Games

Some time ago, the Super Flash Bros. ported a sound effects generator called sfxr to Actionscript 3.0. The original was written by Tomas Pettersson and can be found on a few different platforms. AS3sfxr, as they call their port, gives you the ability to create old school sound effects right in your browser. The sfx can be exported as .wav files at 8 or 16 bit and 22 or 44 HZ. And if you find your mind so blown that you have to take a break mid-creation, you can save your work and reload it later to pick up where you left off.

The beauty of this sfx generator is that if you’re not sure what you’re looking for, it can randomly generate sfx for you. If you have a general sense but don’t know where to start, it can randomly generate sounds from a few preset ranges; pickup/coin, laser shoot, explosion, powerup, hit/hurt, jump and blip/select. I usually find that if I’m looking for a particular sound I can click one of these to find something close and then play with any of the 22 sliders to create exactly what I’m looking for. Perhaps the most unique and helpful feature is that the app keeps a history of the sfx you’ve created, much like a browser tracking the pages you’ve been through. You can create a whole bunch of sounds and then walk back and forward through your work to select the most fitting sound.

This isn’t a scoop by any stretch of the means, admittedly I’ve been using as3sfxr consistently for almost 9 months now. However, my suspicion is that many game developers don’t know about this gem. It’s free, there’s no royalty issues, it’s always at your fingertips and perhaps its most endearing quality, it can with little effort give your game a custom-tailored voice of its own.

If you’re looking to make a game with that classic NES sound, look no farther than as3sfxr.

The Difference Between Tetris and “tetris”

TetrisIt’s been over 25 years since Alexey Pazhitnov unleashed Tetris on the world. In that time, several million new games have been thrown into the mix. So why am I still playing Tetris? The obvious explanation: Tetris is a fantastic game. Well duh, but why? If you answered: ”the concept for Tetris is damn good” again I say duh, except that you’re only partially right. It takes a lot more than a good idea to make a great game.

To Illustrate this point I want you to think about all the Tetris clones you’ve ever played and how few of them, if any, are as much fun as the original. I think it’s safe to say that most of them don’t even come close and almost all of them feel at least a little bit off, even if it’s not obvious what’s missing or different. The rules of Tetris are simple, well known and it’s not terribly hard to get your hands on a copy. Over 30 million copies of Tetris were sold for the original Gameboy alone, which is to say nothing of the NES versions and arcade cabinets still in use today. So how can it be that a game so ubiquitous, so simple, so well known and already proven to be such a phenomenal hit be so difficult to copy? Simple. It takes a lot more than just a good idea to make a great game.

If you were asked to list the rules that govern the way Tetris behaves, you might come up with something like this:

  • There are 7 different blocks that fall randomly from the top of the screen into the play area, one at a time. You would of course have to somehow detail each of the 7 shapes and describe the play area.
  • The player tries to arrange these blocks into contiguous lines stretching the width of the play area. Upon doing so, this line is removed and the blocks above shift downward.
  • The user may rotate and move the blocks left or right as the block descends in order to position it as desired.
  • As the game progresses, blocks spawn and descend more quickly. As blocks drop, they drop in increments equal to the size of the squares that make up each block. i.e. the blocks are confined to a grid.
  • When the blocks pile up such that they extend above the play area the game is over. The goal is to last as long as possible.

In a nutshell, that’s the overarching concept behind Tetris. They are the rules that explain the way the game behaves, what the player does, what the goal is and how a game comes to an end. They are the rules we all know off the top of our head and could probably articulate if asked to. What makes the original stand out from its clones are the touches Pazhitnov applied to the game as he designed it. These are the things that you might have sensed were missing or different in the clones but just couldn’t put your finger on.

Here are some of the rules that fall just outside the general concept of the game. How many of these can you answer without going back to play the game?

  • Can a block be rotated when it’s up against the wall of the play area?
  • When a part of a block is removed and the remaining square is above a gap, does it fall until it hits another block? Does it fall by only the number of rows that were removed? Does it fall at all?
  • Does the block rotate when you pressed the button or when you released it?
  • After a row is removed, is there a pause before the blocks above drop into place? How long? Do the blocks above drop all the way down or do they drop one row at a time until they’ve moved as many rows as were removed?
  • Around what square of each block does the block rotate?
  • Does the music speed up as the game gets faster? Does the music change when the game ends? Are there sound effects when a block is rotated, dropped or spawned? Is the Tetris theme music playing in your head yet ;)
  • How many more points is a Tetris worth (clearing 4 rows at a time) compared to clearing 1 or 2 or 3? Is the difference linear or exponential?

It’s likely someone cloning Tetris would miss these points, because they’re not part of the core rules of the game. They’re the supporting cast yet they can make all the difference in the world. Regardless, if a programmer cloning Tetris did think to ask these questions, he or she could play the game and get a concrete answer to each. However, some of the most important details can’t be extracted just by playing the original:

  • How long after a block has touched down can it still be rotated or moved?
  • At what speed can you no longer slide a block horizontally into an opening?
  • By how much does the speed increase each level?
  • Are the blocks generated completely at random or are they chosen based on previous blocks chosen, a weighting system or even what the player might be waiting for? (how many times have you been dying for a straight piece and never gotten it?)

These lists are incomplete, but they ought to be enough to illustrate my point, which is not to say that Tetris cannot be copied. Of course it can, any game can if you’re willing to spend enough time testing and tuning. I’m also not interested in the reasons behind why so many Tetris clone programmers couldn’t make the grade; lazy, rushed, low budget, first time programmer, bad eye for detail, whatever…the reasons are of no consequence. What’s important to note is that Tetris is an extremely well known game with a simple set of rules that isn’t much of a technical challenge to program, yet so many of its clones just don’t cut it. Why do you think this is so?

The answer is simple. It takes a lot more than just a good idea to make a great game. Is it sinking in yet? When it comes to game design, the final product is very much the sum of its parts, which include but are not limited to concept AND art, sound design, interface, difficulty, originality, learning curve, proper tuning and those extra touches. Without getting too analogous, a game, like a house needs a solid foundation. But in order to be a great house it will also need sturdy walls, furniture, nice carpeting, hopefully a tv the size of a small country, maybe a snappy doorbell ring and with any luck a sexy wife with a penchant for cleaning in the nude…but I digress. The point is, even with a solid concept every game walks a fine line between flop and phenomenon. Most of the Tetris clones out there follow all of the concept’s rules but miss just enough from the other lists that they feel dull. You don’t have to stray very far from Tetris before it becomes “tetris”.

But it’s easy to compare a classic to its clones and see where one succeeded and the other failed. How do you identify these key elements before you send your game out into the world? Are there blanket rules that can be applied to all games in order to make them better? What kinds of questions can I ask about my games in order to identify the important details that will transform my good concept into a great game? How do I know when my concept is good or my game is great? Which of our contemporary games have gotten it right and why? These questions are just a very small sliver of the things I’d like to tackle here at Bacon and Games. Thank you for taking the time to read this.

I play games. I make games. I love games. And I really love bacon.

– Sean

P.S. Yes I know that versions of Tetris existed before Nintendo came along, but let’s not kid ourselves about who put the game on the map. For the purpose of this discussion it makes the most sense to treat the version the vast majority of the world is familiar with as the original.

Copyright © 2017 Bacon and Games

Theme by Anders NorenUp ↑