So, the question seems vague but I will elaborate.
I’m a software developer, but I don’t do games; yet I have an urge to try and make something.
It just seems so overwhelming, I know I want to make a game where the main character is a cat and you have to complete missions, but where do you even begin. Where does the art come from? How do you refine your idea, if all you know is you want a cat game? How do you choose an engine? Do you just start with the basics and get a cat walking around and see what comes next? If you can’t hash out the idea then so you have a right to even try and make a game? Is it best to follow tutorials to get used to making games? I feel the answer to that is no as before I become a software developer, tutorial hell was a thing and I realised I needed to make things for me to actually learn.
Sorry for all the questions, this was just a stream of thought.
If you can’t hash out the idea then so you have a right to even try and make a game?
This is the most important thing I see here, because the answer is always ‘yes’. Of course you have the right. Start where you’re at and figure out what you need as you go along. Your first attempt might not work, but what you learn from it will be invaluable.
As far as art goes, you can either find someone who is excited to work on it with you in their spare time (difficult to find), or pay an artist whose style you like to create art for you (possibly expensive). If you do the latter, it’s best to wait until you have a clear idea of what you’ll need so you don’t end up paying for assets you won’t use.
One thing you can do right now is create a design document. This is basically just a long, detailed description of what you would like your game to be: specific mechanics and systems you want to include, what the gameplay loop will be, the audiovisual style, everything. Include images mood-board style for your future artist(s). This document will give you an idea of the assets you’ll need, as well as what you’ll need to learn as far as coding. It doesn’t have to be followed to the letter, but it’s a good place to start.
Thanks.
This is very insightful and I hadn’t really considered a design document so I’ll look into the structure of those and hash out something.
