• Advertisement

100 tiny games, ideas needed

Recommended Posts

I'm planning to build 100 tiny games, (the specific number is not so important).  

The general idea is to improve my skills, by pushing my comfort zones in game development.

I'm looking for a breakdown list of 100 tiny game concepts.  

These are genre's, but then also pushing different concepts, like AI, physics, graphics, animation, etc...


Any thoughts on this.  Or if there is another post or article you can point me to. 


 - Thanks!

Share this post

Link to post
Share on other sites

Its hard to take you seriously, when you say 100 games (or even 50 games, given your implied flexibility), as you're more likely to be repeating the same code over and over instead of actually learning anything through fleshing out a bigger project (and by bigger, I mean "still fairly small" since you want to "scope small", as they say). Keep in mind that, unless you have a sizable team to work with, even your smaller games are going to require months of work if you want to build anything that is worth playing. Even simple mobile apps for iPhone take 18 weeks on average, according to google. And that probably assumes some team-based effort.

Also, let's be realistic. What would even be the purpose of making that many games? You would see greatly diminished returns on your learning long before you're done with even your 10th game. Focus on 1 game at a time, and visit the various concepts you want to learn through each subsequent projects. (Good) games are extremely iterative in their design, which means that you don't need to know a lot of the stuff on day 1. Things will come to you in due time and as you're gradually becoming better and coupling your development with constant study and learning.

Just start making your first game, and iterate on it. And what do you even mean by 100 game concepts/genres? Just play a lot of games and you'll learn which genres and concepts exists. Always start with some core game functionality that is going to be the meat of the experience, then expand upon that relative to the size that you're aiming for. Then make your next game when you're ready. Iteration is the key, not planning 25-50 years worth of gaming.

I've played well over 700 games in my life (which are necessarily across most, if not all, genres and conventional settings). There's really not that many of them. Successful games tend to converge on a small subset of genres compared to the total number of genres that could potentially (an unsuccessfully) exist.

Edited by Madolite

Share this post

Link to post
Share on other sites

@Madolite, Thanks for your feed back, but I have a lot of what I believe are good reasons.  First off, I have developed a lot of game concepts, especially large scale games that never saw the light of day.  My professional title is VR Solutions Architect, and I'm a Microsoft MVP for my work in 3D.  (mostly business focused and educational)  I bring this up to emphasize that my issue is not ability to code, or work with the technologies.  

The specific issue I'm trying to get through is faster completion of PoC's, and to have experience in a larger variety of game mechanics.  Not just theoretically, but functionally.  I'm trying to expand my abilities to be comfortable in game jams.  Also, much of my professional work requires pulling together a game concept for business purposes very quickly.  


Also, I want to be able to get through Game Jams easier, and have trouble minimizing my goals into more manageable tasks.  I want a lot of different code bases, So I don't get stuck in just a couple that keep growing, but instead focus only on the absolute minimum to get a concept or mechanic done.  

You are absolutely correct that I will end up having a lot of pieces repeated.  But hopefully in different ways and approaches.  Things I can try to shorten down a lot.  May also make good blog posts.

Share this post

Link to post
Share on other sites

You might consider looking at very old consoles, like say the Atari 2600, and look at the games that were most popular on it.  I bet you can come up with a good list of at least 10 or 20 simple game ideas to implement that way.

Share this post

Link to post
Share on other sites

I rather liked the Experimental Gameplay Project site. I imagine the explanation on the about page is something like what you're figuring, " The project started in Spring 2005 with the goal of discovering and rapidly prototyping as many new forms of gameplay as possible."



Also, if you're looking to get more comfortable with game jams why not take a stab at past jam themes that were originally intended for fast turn around time?


I would expect that there's random theme generators out there as well, although personally I would rather have other projects to do self comparison with.

Share this post

Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

  • Advertisement
  • Advertisement
  • Popular Tags

  • Advertisement
  • Popular Now

  • Similar Content

    • By khoa dong
      New simple concept, one touch game. Please try and give your feedback 
      Like it  : https://www.facebook.com/bitrolling/
      Contact : littlerabbitgames@gmail.com
    • By a2j2tiwari
      Hey guys, 

      How is everyone doing? I am new to this forum and I thought what better what to introduce than show off your work? 

      I am a Pixel Artist, Concept Artist and now delving into the world of painting. 

    • By Andre Zunino
      First, a bit of context. I'm having my first contact with the entity-component-system architectural pattern in the simple shoot'em up game I'm writing. I appreciate the flexibility and decoupling the pattern promotes. So far, I believe I have the basics down. I have already defined a handful of components and systems which operate based on them.
      I'm now looking to add a cannon to the player's spaceship. I defined a Cannon component and attached it to the player entity (IOW, I "tagged" the player entity as having that capability). That component has a single member which indicates the cannon's rate of fire. Then I defined a PlayerWeapon system that is responsible for actually firing. At the moment, all it's doing is write a message to the console. Because no actual rate control is implemented yet, each press of the assigned fire button causes multiple messages to be output in quick succession. I would like to implement a sort of debouncing mechanism to have the fire rate respect what the cannon component dictates, e.g. fire once every 500ms.
      Now for the actual question on ECS modeling. Suppose I'd use a simple elapsed time accumulator to decide when the next shot should be allowed to fire. Where would that information be stored? Should the system be responsible for managing that type of information? Or should systems be considered completely stateless? In that case, the accumulator would be stored in the cannon component, along with the existing fire rate. Would you kindly share some advice on how to handle a situation like the above? As stated, I'm new to ECS and would like to make sure I implement the concepts as properly as possible.
      Thank you.
    • By Luhan M.
      I tried to implement the command pattern explained in this book : http://gameprogrammingpatterns.com/command.html. I'm looking up for someone which could revise my code and see if I did implement it the right way, or even if I did deviate a lot from how it should be implemented.
      Here's the code : https://github.com/Luhanmacedo/Command-Pattern  
      I didn't understand if the base class (Command) could be modified to introduce methods as I did to facilitate implementation details in the derived classes. What would be a good way to map the buttons according to the configuration the player wants to use, such as X for Jump and Y to shoot.  
      P.S. :  If it's not possible to review the whole code, tips in some parts are welcome as well.
    • By Lumberjack RPG Development
      I'm very much a beginner when it comes to game development. I'm merely trying to come up with a concept at this point for a project later in life. I would like constructed input, opinions, and criticism that will help me fix things wrong with my concept in mind.
      I've loved story-driven games, and have always thought about making one. I'm not the most colourful crayon in the box, so I find it difficult to come up with appealing storylines that are well designed for a video game and not a written novel. I've came up with several story concepts that I feel may be suitable for games, but for this thread, I'll only explain 1. Please respond with things that I should add, remove, or fix.
      I want this to be a story-based game, obviously. I'm not sure if I want to create a game that looks like an old-school RPG game, a 2D sidescroller, a click-to-select, or any other media I happen to think of. I feel it wouldn't be good to make it a first-person perspective game, because that is usually used for gameplay purposes in survival games, shooters, and other games including first-person fighting, which,  being a story-driven game, this concept does not have.
      The protagonist is this kid that's around 20 years old that has seemingly dropped out of high school before the game's story takes place. Despite this, he's intelligent and classy, and is able to live comfortably in his own apartment; he even has his own job at a nearby bookstore, where he makes decent money. You figure this all out around the time you begin playing. After a while you notice that the protagonist is dealing with strong grief and sadness; could this be the reason he dropped out? But, what could it be?
      This idea begins to grow itself into the player, but, as the player continues playing normally- meeting some of the protagonist's old friends, learning more about them- they begin to forget about the protagonist's depressed state. This is then brought back after a while of exploring the town and coming back to your apartment to rest. After doing so, the player is dropped into this "dream" first appearing to be your normal residence, but slowly becomes distorted over a few minutes until you realize where you are. You can't seem to wake up. This can be done a few sections later when you receive a necklace given to you by a dubbed "imaginary friend" from your childhood that appears in the dream. You can use this to your advantage if you need something to complete an area that is in the real world, shop for new items, or complete a day of work at the bookshop in exchange for currency. Doing so can and will affect the way you perceive the dream world; dreams are never the exact same. Enemies can become more difficult, an area can become more distorted, dialogue may change, tiles may switch, and you may lose or receive items. The amount of times you transfer between realms will affect the outcome towards the end; not by a lot. Only things such as dialogue, characters, and the attitude that characters have toward you will change.
      The game will consist of a tutorial character that is seemingly a normal-looking person. Of course, since the world becomes more distorted throughout the dream, the leading characters/bosses will also become more and more bizarre and hostile-seeming throughout the areas leading up to the end of the game, where you discover the true background of the protagonist and the reality of the real world; the character was born with a mental illness that allows them to create a different 'world' to cope with trauma, and has morphed the real world into their own perception of a normal life, where they only have to deal with the grief hinted at towards the beginning of the game (the death of their mother). Though reality is actually very terrible; they realizes that the world is filled with horrible death, destruction, and peril that is not only being dealt with by them. This realization causes them to revert their perception or the real world back to this insane nuclear wasteland full of sorrow. They can't find any of their "friends" and can't go back to the dream world, because none of them were real; they were made up by them to cope with their mother's passing. The wasteland is also a perception by him, but it's much more realistic, figuratively speaking. The message from this is that no matter what your issue is, almost everyone else has, is, and will deal with the exact same thing that you are. There is so much bad in the world, so much death, and so many horrible things that you don't notice. So, you need to stop wallowing in self-pity and fix it yourself, because no one else is going to. They have their own problems to deal with.
      Please respond with constructive feedback and advice. Tell me what to add, take away or fix.

      Thank you for taking your time to read this.
  • Advertisement