Making video games is a dream come true for most developers, but as we’ve seen, it can
also be a daunting journey filled with new challenges and surprises.
Not everyone makes it to the finish line - and some don’t even make it to the starting
line!
In this video we are going to look at reasons why people quit (or not even start) their
game development projects.
We are Ask Gamedev and these are the Top 10 WORST Reasons to Your Quit Gamedev Dreams
Welcome back!
If you’re new to Ask Gamedev, we make videos to help you learn about the gaming industry
so that you can elevate your games and inspire others.
If you’re on a gamedev journey yourself, consider subscribing.
We’d love to help you along the way!
And if you’d like to continue the conversation, join our Discord server.
Check out the description for an invite link.
Number 10.
“I don't have the money for it”.
Being a game developer is too expensive!
Why is this a bad reason?
Nowadays because of so many open source projects, it’s arguably never been more affordable
in the history of game development, to be a game developer.
There are a number of free game engines out there like Corona and Cocos2DX.
Unity has a personal license that’s free for any dev with revenues under $100k.
And for an open-source 2D and 3D engine try, a community favourite, Godot!
For art, you’re spoiled with options.
There’s GIMP - the free photoshop alternative, Krita - an open source painting tool
Inkscape - a free vector graphics editor And of course Blender - the beloved 3D suite.
Number 9.
“I don't have anyone to work with”.
We understand this.
It’s sometimes hard to keep motivated on a project while working alone.
So, why is this a bad reason?
The answer is because you don’t have to stay alone!
Just remember, the game development community is huge, and there will always be people just
like you, looking for a group to work with.
Here are just a few places to meet fellow game devs looking to partner up:
Crowdforge.
Crowdforge has a section on their site dedicated to game jams . On each jam’s page you’ll
be able to see each team’s discipline composition, and find out what roles they still need to
fill.
Either create and recruit your own team, or join one that’s looking for your skill.
r/gamedevclassifieds.
Reddit’s Gamedev Classifieds is still a very active subreddit, with over 40 thousand
members.
And finally, the many gamedev Discord servers out there that provide a platform for people
to form gamedev teams (like Ask Gamedev’s Discord Server)!
All of that said, if you really are a lone wolf, there are plenty of solo devs that have
seen success taking the road less travelled.
Check out this playlist of the some of the best solo dev success stories.
Number 8: “I'm too young”
We see this one a lot, and every now and then get someone asking “Am I too young to make
games?”.
Why is this a bad reason?
Well first, let’s clear this one up right now: You’re never too young to start your
gamedev journey!
If you’re old enough to be interested in game development, then you’re old enough
to make your first game.
If you’re interested in coding, there are a number of accessible coding courses designed
for people of all ages.
Code.org is a nonprofit dedicated to expanding access to computer science in schools.
They also have online courses designed for grades K-5, 6-12, and beyond!
If you’d like to try your hand at design, there’s BAFTA’s Young Game Designers initiative.
It’s a yearly competition where young designers create ,develop, and present their new game
ideas to the world.
Aspiring game designers aged 10 to 18, can compete to win the “YGD Came Concept Award”,
or the “YGD Game Making Award”.
For more info, check out BAFTA’s website.
Number 7.
“I don't know what engine to use”.
This one can cause people to stumble right out of the gate.
You might even find yourself going through analysis paralysis making sure that you’ve
chosen the right one.
Why is this a bad reason?
Well just because there are a wealth of engines to choose from, doesn’t mean you should
get stuck right at the start.
To simplify things, here are some questions to ask yourself when choosing an engine:
Is this engine suitable for the type of game that I’d like to make?
Are there any comparisons?
Do I have the knowledge to use this engine?
If not, can I learn from the documentation, or books?
Are there enough tutorials for this engine that feature the type of game I want to make?
Do I have the hardware to support this engine?
Does this engine support the platform that I want to release on?
Am I ok with this engine’s license and/or fees?
For more on game engines, and the types of games you can make on each, check out this
playlist of game engine showcases.
Number 6.
“I didn't go to a game design school.”
Some people think that you need to attend a game school before you can start making
games - and that’s a misconception.
Why is this a bad reason?
First we should say that going to school is never a bad idea.
We do not want to dissuade you from going to a game design school.
At the same time, not going to one should definitely NOT stop you from trying to make
games.
In regards to game schools though, here’s what one of our favourite indie game developers,
Derek Yu (of Spelunky, UFO50, and Spelunky 2), has to say “The most important thing
to know about video game development and schooling is that no one, whether it’s an indie studio
or big company, cares about degrees.
How could it, when some of its most prominent members are drop-outs or never-beens?
John Carmack, Cliff Bleszinski, Jonathan Blow, and Team Meat are all prominent members of
this club.”
You can read more of his tips on GamaSutra.
We’ll leave a link to the blog post in the description.
If you’d like to learn about game design on your own, here are some books that we recommend
on design: The Laws of Simplicity by John Maeda
Level Up!
The Guide to Great Video Game Design by Scott Rogers
The Art of Game Design: A Book of Lenses by Jesse Schell
A Theory of Fun for Game Design by Raph Koster
Number 5.
“I can't make art”.
Drawing is tough, and some of the best, highest-selling indie games out there have amazing art [Cuphead],
so we can really sympathize with this one.
So why is this a bad reason?
Well if you really can’t make art there are at least 3 things you can do:
Learn.
There are so many great artists out there sharing their techniques.
Our video on “The Best YouTube Channels to Learn about Game Art” was just the tip
of the iceberg.
Use simple shapes.
Not all games need super complex art.
We’ve seen games that take the minimalist approach become critically and commercially
successful Source your art.
If art is a roadblock for you, try buying an asset pack, or even commissioning your
artwork.
For more on this topic, check out our video on how to source art for your games
Number 4.
“My game idea won't make any money”.
Some people think their idea is too niche to garner any sort of attention or success.
Why is this a bad reason?
Well we’d caution setting high financial expectations.
In most cases, trying to make a lot of money, especially with your first game, is not a
realistic or probable goal.
As we’ve seen, making an indie game does not guarantee you any money at all.
In fact, many developers have lost a substantial amount of money.
With your first game, your goal should likely be to ship and to better yourself for your
next effort.
If you can ship a game, and learn from it, that’s already a huge accomplishment.
Number 3.
“I don't know where to learn about gamedev”.
Why is this a bad reason?
This is a bad reason because we live in the age of learning.
You can learn coding for free on sites like Khan Academy, or Codecademy.
You can also find full gamedev courses for various engines on sites like Udemy.
And lastly, you can learn a lot of what you need to know, for free, on YouTube.
Some channels we’d recommend learning gamedev from are Brackeys and Blackthorneprod.
For our full list of recommendations, check out our video on the best gamedev youtube
channels.
Number 2.
“I don't have any time”.
Well this one isn’t specific to gamedev as this could impact any hobby.
Why is this a bad reason?
Well what we can say here is that game development is flexible.
You can find pockets of time and work in small bits, or learn in small chunks.
Matt Rix (of the award winning game Trainyard), created game ideas and prototyped them on
his netbook all during his commutes to and from work.
It’s also common for indie developers to work on their titles part time on evenings
and weekends before ramping up and releasing their title.
We saw that in last week’s Community Member Game of the Week, Must Dash Amigos.
Also, Daniel Mullins, creator of Pony Island and The Hex, had a full-time job for most
of Pony Island’s development
And finally, the number 1 worst reason to give up on your game development dreams: Number
1, “I can't code.”
Some people think that if they can’t code, then they have no place in game development.
Why is this a bad reason?
Well for starters, just because you can’t code doesn’t mean there’s no spot for
you on a game dev team.
As we’ve seen in previous videos, all great game development teams are comprised of people
across a variety of disciplines including art, design, marketing, project management,
and more.
And second, you don’t necessarily have to write a single line of code to make a hit
game.
We’ve seen amazing titles come from no-code game engines.
And finally, if you can’t code now, there’s no reason you can’t start learning!
If there’s one thing that we want people to take away from our channel it’s that,
if you have a passion for game dev, you can learn anything that you put the time and effort
into, at any stage in your life.
For more Ask Gamedev on how to plan a development project, check out this recent video.
Or alternatively watch this video on the most sought after gamedev roles.