Skip to main content

On Sale: GamesAssetsToolsTabletopComics
Indie game storeFree gamesFun gamesHorror games
Game developmentAssetsComics
SalesBundles
Jobs
TagsGame Engines

If you're looking at 3D, have you considered playing around with the tutorials on Unity learn? You make small prototypes during the courses which gives you insight into the software and gaming fundamentals.

It does sound like you're aiming to make a time management game. They are particularly complex in terms of how many things must work together and work separately at the same time.  It's a difficult game for a starter game.  Games like point and click adventure games - where people simply walk around and click things - or games with simple game play like Sokoban / space invaders are easier to make the first time round. 

 There's nothing wrong with making a complex game first, but you need a lot of motivation to keep going because as you say, it will take months before you can play it - and with starter games - there's normally many bugs which specifically are things that you did not foresee happening, and therefore did not provide code to cope with it due to a lack of experience. 

When I started I set myself a goal of creating 10 small games - at least 30 minutes each, each one had different game play and graphics features,  before attempting a full length game to gain the knowledge on coding and game play.  That way I was creating a playable game much faster which kept me motivated. It also meant that I had  own examples of most features that I was going to put into a larger game.

Tip: Play a lot of games in the genre you're writing. That is the best way to know if what you're doing is fun or tedious.  Avoid the aspects of those other games that you find annoying, and keep the aspects that you find fun.

(1 edit)

Thank you, these tips help a lot. I think my biggest takeaway was to play games in the genre I want to make games. Honestly, I'm not sure what you would call the genre of games that I have in my head, but I would like to figure out how to make adventure games, so maybe I will start there.

You mentioned that you made 10 small playable games. I would also love to do that, but what do you consider "small" and "playable?"
Also when you say that these games were 30 minutes each I imagine your referring to playtime and that is something I have been puzzled about recently. Because unless it's a story game I don't know how to judge how long the game would be played for. Perhaps not knowing my genre contributes to that confusion but if your games are not solely story games then, how do you determine the length of their playtime?

For me it was about making a game from start to finish, and adding in a new feature every time. So it would have a start screen, basic menu,  a final level, a win screen and a way to restart. The first few games I wrote did not have a save, but they were short enough that someone could play it through in a single session. They had at least 10 levels, and it takes about 2-3 minutes to complete a level and two to three difficulty settings so that there was replay ability.  Every game was a little longer, had more options etc.   

With an adventure game - work on how many scenes, or how many interactions, so consider each scene a level, and how long the player is going to walk around for i.e. how big the scene is and how much dialogue there is.  It's also something you learn with experience - you need to first create a playable scene and then time yourself - if it's taking you 10 seconds or 10 minutes, there's a problem.  (the first is too short - put more obstacles in the way, the latter is too long - players will get bored, have more scene changes.)  

My criteria for free games is that it should not take someone longer to find, download and install the game than to play it. And it should be a game they can replay to make it worth their while i.e. it will be different next time because of random elements. (That's a little harder to do in adventure games.)

My personal criteria for the the paid games I develop is that it should be at least 5 hours of game play (which includes reading the stories - those that have them in) - to justify the price. (That's more or less the benchmark for casual games - I read a lot of forums / reviews to get a feel for what people liked / disliked - and below that benchmark people often ask for their money back - longer than that adds more value, you can charge more or they feel that they are getting good value for money - this is at the $2.99 - $6.99 price point.) 

You can find good quality adventure games here (free) that will give you an idea. 

Thank you, I appreciate those kinds of guidelines to work within. I feel that keeping in mind the time frame of longer than 10 seconds and shorter than 10 minutes will definitely help when trying to figure out which game idea will be ideal for me to put my time into. And thank you for the link as well. Something else I am gleaning from these discussions is that it may be beneficial for me to spend more time in the forums. I generally watch a lot of YouTube videos, Unity documentation, and other articles but I imagine the forums are where I will learn about the "real world" challenges and lessons that people are learning.