Transcripts
1. Introduction: Let me know if this
sounds familiar. You've been wanting to make
games for a long time. Maybe even your whole life. Maybe you've made a few or
had a few false starts. But something always
seems to get in your way. You've been toiling away on
the same idea for years. You can't find the
time to devote to it. Or you tried to teach yourself
a skill and got frustrated. Or maybe you got halfway through your project and then
you've got bored. Well, guess what? You're not alone. I've talked to so
many people that have these kinds of issues. And that's why I wanted
to make this course. My name is Miko Charbonneau I have a PhD in computer science
studying dance games. I'm currently running
the indie studio, prettysmart games, and I've worked in the
game industry over eight years as a game designer. I've self-published
over 30 games and apps. And I want to help you make your games because
I think games are amazing and more people
should be making them. games or magical. They can make you laugh, they can make you cry. They help us bond
with our friends and they ease our loneliness. They can even teach us about
the world that we live in. But making games is
really hard because it's a creative challenge in so many different skill sets
that you have to learn. So don't feel bad if
you've struggled, because making games is also
a lot like playing them, you need a strategy
guide to help you overcome the challenges that
you face along the way. And that's what this course is. Every video is going to tackle a different
area where you could potentially get stuck as you make your way through
the game def process. You can watch them all
in order where you can jump right to the one that
you need the most right now. So let's do it. Let's finish your indie game.
2. Your Goals: Before we get too far, we
have to talk about goals. You wouldn't start
a race without knowing where the
finish line is, right? And yet when it comes
to creative goals, we put a lot of pressure on ourselves and develop a lot of anxiety because we don't exactly know what we're
trying to reach for. Setting goals is more about the journey than it is
about reaching them. It's something that encourages
you to work a little bit harder on a Friday night or to set a deadline for yourself so you can encourage yourself
to get something done. That's actually what our
first indie game was. We were going to game developer
conference and we didn't want to tell people that we were aspiring game developers. So we worked for
two months to make a little puzzle game that
we shipped on Android. You should set a goal that's
in your power and one that aligns with the
reason you want it to make games in
the first place. If you're wanting to learn a fun skill or get a job
in the game industry, think about what kind
of indie game would best show off those skills. If you want to
make something fun for a friend or family member, that's great because you already know your
target audience. Or maybe you have
an idea that you just really want to exist. Which is amazing. I personally think the
more different types of people out there
making games, the better we're all going
to be because there'll be so much more diversity and the types of games
that we're playing. But I also want you to not make these your short-term goal, profitable game
and popular game. They're not in your
control, right? Not entirely. So it can be really frustrating
if you set yourself a goal like I'm gonna make thousands of dollars
on this game. And you haven't been able to set up the infrastructure
to do that, especially if it's one
of your first games, light in your burden. Let's focus on one thing at
a time and just make a game. Okay, here's your homework. We're going to do one
of my favorite goal imagining exercises. This may mean you'll
be touching on subjects other than
game development, or that you'll be considering life beyond finishing a game. Close your eyes and imagine
yourself ten years from now. Ask yourself what a typical
day in your life is like. Where do you live? Who are
the people that surround you? And what skills do you
have for yourself from any real life worry and focus on what would
make you so happy. You're practically tearing
up, thinking about it. Open your eyes and
write it all down. Now, try again. Imagine where you have to be five years from now to be
on the path to that future. Right, all of this
down to finally, close your eyes and imagine
yourself a year from now. What do you have to
do a year from now to get to that five-year plan. That list is the
goal for this year. Look at what's important to you. Is it your health,
your skill level, your finances, your
creative expression? Use that to remind yourself that success isn't doing
everything at once. It's making progress to
what matters most to you.
3. Phases of the Game Dev Process: Now we're gonna do
a quick overview of the game dev process. This is essentially a list of phases that every game goes
through as it's being made. Different studios and courses will teach you different
versions of it. I'll teach you the one
that I like the best, but it's okay if you decide you want to shake it
up a little bit. I'm going to use the
game dev process as our structure for describing the places where you're
going to get stuck along the way because it's
kinda like a big funnel. Everybody starts
at the beginning. Then you kinda get weeded out along the way as you try
to finish your game. You can refer to
your project files for a copy of this flowchart. So let's go through what
each of these means. Concept is where
you have the idea. You brainstorm features. You're talking
about mood boards. You're gathering art
and audio samples. It's restart to flesh out what you want the
whole game to be. Prototyping isn't
always a phase, but I like it because
it's fun and it lets you quickly challenge or
more unique ideas. It's where you take anything
that's still a question and experiment to
answer those questions. This could be anything from how does the magic
system work to how will we represent water
and our island game? Pre-production is all about
answering the question. Do we know everything we need
to know to make this game? It's normal for more iteration to happen after this phase. But to the best of your ability, you should use this time to decide how many art
assets you need, how many levels, how
many gameplay features? Answer all the questions. You have, the whole plan
of how much it will take, time and effort and
maybe budget as well. To finish this,
production is where you execute your plan with the
knowledge you have now, make deadlines and finish your work bit by bit
until it is done. You can go back a few phases. If you have to rethink a feature or come up with a new one. But generally you're
trying to avoid this and you're focusing on just getting everything built. Polish is where
you fix the bugs. You make the game sound
good and look pretty. This is the constant
cycle of iterating, playtesting and making cuts
and difficult decisions. Release is where everything
is prepared for launch. If you haven't done
any marketing yet, you're doing it now. You're making the final build, the store assets and
whatever else you need to push the button
and get your game in the hands of players. Finally, maintain
is the long thread. After a game is out. You listen to the reviews
and the community. He fixed bugs or make updates that you pushed off for lunch. If it's a smaller project like a game jam or an experiment, you may not have to do much. If it's a project
you want to continue developing for a long time, you can move into
a service model with regularly planned updates. The rest of the videos in this course are
going to walk down the lifecycle and point out areas where you're most
likely to get stuck. So we can address those
problems along the way. You can keep this
chart handy so you can refer to it and know where you are at in your
game development as you go. Homework, print out a copy of the game dev process worksheet. For any previous game
projects you've made, write down their names under
the phase where they ended up pat yourself on the back for any of
that made it to launch. Think about why your project
stopped in different phases. Think about which phases where
your favorites to work in. Fill in this section below with how you feel about each phase, which ones you love doing, and which ones are
harder for you. This is going to
help you realize the places where you're
most likely going to want to avoid work or you're going to have the
most trouble moving on.
4. Concept: The Right Idea: We've talked about goals, we've talked about
the game dev process. It's time to choose a project. And a project starts
with an idea. But you may not have
any ideas at all, or you might have too many. In this video, we're going to
talk about how to organize your ideas and also how to
choose the right one for you. First of all, ideas need a home. They need a little paradise to live in where you can throw them all in there and know that you haven't
forgotten any of them. You may be one of those
people that says, I don't need to
write down my ideas. I keep them all up here. And that's amazing for you. I'm not going to argue with
you that you can do that. But I would want you
to consider that if you took those ideas
out and wrote them down, it's like an extra external hard drive space for your brain. You can have even more
ideas going on in here. And for most of us, we learned our best ideas
kinda slip away because we don't even realize that they're going somewhere, right? It happens invisibly. So I recommend that you do
make yourself an idea home. This can be a physical notebook. It can be an app that you like. I personally like
to use Notion or one node or Google Keep
anything like that. Something with cloud
storage is usually a good idea because
it'll sync between devices and you might have an
idea while you're watching a TV show on the couch and you just grab your phone
and write it down. Or you might have an
idea while you're getting ready for bed
or your computer. The point is to have a place. Every time that you
have a cool idea, get in the habit of writing
it down in your idea home. You don't have to think about
yet if it's a good idea, just write down everything because you never know
when things are going to maybe float backup or a different take on
something you were before. We'll suddenly inspire you. I like to think of ideas is starting from one of two places. It's either going to start from the gameplay or the theme. Your game will have both, even if it leans heavily in
one of the two directions. It gameplay idea
is a game genre, which in the game industry tends to mean the
gameplay features, the mechanics, the systems. We don't really
use genre to mean. Like thriller or fantasy. Usually mean things like tactical RPG or first-person shooter
or action platformer. So one way to know what's
the genre of the idea that you want is to look at a game that has
the same features, are the same interactions
as you want and see what they refer to
as their gameplay genre. A theme idea is something that starts with the characters, the world, the story, the way that you want
your players to feel. It can be kinda
autobiographical or it could be about a certain culture
that you are part of. A, can be just a story that
means something to you that you think would be interesting to play
interactively. And theme and story ideas. Start with that narrative and
then you pick the gameplay, genre and mechanics based
on what's going to get across the feeling that you most want to make your players
feel while they play. Neither is better
than the other, but it's good to know
what your tendencies are. Now let's go through some of the common hurdles that people have. So problem number one is, I have no ideas. You may be a person
that gets really excited about building things, but you're not too
concerned with making a game that's never
existed before. And that's okay. So let me teach you
two quick strategies for how to generate ideas. The first strategy we're
going to call what-if. This is kinda going back
to like when you were a kid or if you've
been around kids, you know how they're
always asking questions. Why is it like this? Why are you doing that? How does this work? What if this happened? Kids have great ideas
because they're exploring so much
in their heads. And as we get older, we lose that because we start to fill our heads with information and
then we think we're right, so we don't really ask
questions as much. We just say This is what I believe and that's
what must be true. So getting in the
habit of asking what if an outlandish
situations or just making everyday
situations seem more abstract or out there is a really good habit for
coming up with new ideas. Maybe on your daily commute, you're asking yourself, well, what if the road was blocked
and it was because there was a dinosaur walking across it or there was a military parade, why would that happen? What would I do if that
happened or what if I saw someone sneaking to an alley and they were like glowing gold like what
would that even mean? Like anything
that's like kind of random event and
just start to think, well, what if this happened? You can even do it when
you watch a movie, or when you read a book, or you're playing a
game, you can say, well what if they had
done this instead, or what if my character
could do this? What if they had taken the
plot in this direction? Maybe I like to write
a game about that. And that's a good way
to generate new ideas. The other technique you
can use is the mashup. We previously talked about, bucketing your ideas and to
gameplay genres and themes. And what you can do is
essentially randomize this, pick one from each category
and combine it and see, do you want to make a game about Guitar playing,
unicorns or something. You can even choose to
do things like mashup to gameplay genres or two
themes and see what happens. So playing with mashing up
things like that can be a way to generate an idea that will really resonate with you, okay, so the next problem
you might be having is that you have too
many game ideas. And if this is you, then you and I have
something in common. I always have too many
ideas and then I worry, how will I have enough time in my life to finish
all of these things? So the way that you get
past this is just picking the right idea for right
now and prioritizing them. When we get to the homework
at the end of this video, I'll show you a prioritization technique that will help you. But in general, you want to pick the one that's the
easiest for you to accomplish right now and will also help you towards making
one of your other ideas, or maybe multiple of
your other ideas. So it's less about saying, oh, this idea is more
important than another. It's about putting them in an
order that lets you get the most done in the
fastest way possible. Another problem that
you may have is feeling like your
idea is in good. Now it's important
to know why you don't think your idea is good. Because sometimes you
just need perspective. Sometimes you feel this way
because you're doubting your own ability to
make your idea happen. And it's important to know
that if it's something like, I don't want to make
this idea because it's been done so many times before. It's really about the execution. So you don't need
to feel bad if it's already been done or if there's a lot of
games in that genre, you should think about what's the unique perspective
I'm going to put on it? What's going to make me
excited to play this? If there's a lot of other
games in that genre, how would I stand out? What would make me
pick up this game instead of or in
addition to others? Don't forget that
people play games a lot faster than we make them. So you may be thinking, Oh, there's already like
five great games that are similar to this. But if you're a person
that's played all of them, you may be looking
for your sixth game, so don't discount it based on
something like that alone. The other reason why
an idea is maybe a good one for you is if you're just not
that interested in it, you might think that sounds cool or you might be like, yeah, like this game is the type of game that
lots of people like, but maybe you don't
like it that much. And if so, it's
gonna be really hard for you to finish
that game because we're talking about hundreds or even thousands of
hours you're going to put into not only
making the game, but playing the game and telling other people
about the game. The more passion you
have for an idea, the more successful it will be. It's really important to
pick ideas that you're gonna be so excited about that
during those rough patches, you'll be able to overcome them. It's time for your homework. Create a place for your ideas
to live your idea home. This could be a whiteboard, a text document, a
notebook, or a mindmap. Make it someplace
that you'll be able to access easily even when you first wake up or
it's after a drive or a walk, give yourself a block of time to write down all your
current ideas, gather them all into
your idea place, sorts your ideas by your goals. You can tag them and label them, move them around, or make a
fresh page for this exercise. For example, if your goal is based on learning a
new skill bucket, your ideas based on which ideas will show
off those skills best. Now focus on the ideas that
most line up with your goals. Prioritize these ideas based on your current abilities
and resources. Projects that would take you less time should
be near the top. Projects are more complicated
and require more people, skills, or money should
be near the bottom. Now you have a list of projects
that you want to make in the order that is most
likely to help you succeed. Finally, if you
haven't already picked the idea that
you're going to use for the rest of this course.
5. Prototype: Game Engine and Tools: Okay, so we have an idea, we know we're doing,
we just gotta get started building
stuff, right? We could do that. But we probably need
some help along the way. And that help will come
in the form of tools. In this lesson, we're going
to talk about your main tool, your game engine, and some other software that will definitely help you
make your game. What is the game engine? It's essentially just a piece
of software with a bunch of features that are useful
in making a game. If you don't use a game engine, you'll have to write all
of the code and all of the features that may be something that you
really enjoy doing. It may be part of your goal. That's fine. If that's true, I
would recommend for most people that
you do not write your own game engine if
your goal is to finish your indie game in the shortest
amount of time possible, because you're going
to save a lot of time by taking advantage of what other people
have already made. Basically don't reinvent
the wheel if you don't have to buy using the right game
engine for your needs, you can focus on what makes
your game really unique and fun instead of getting hung up in all of the little details. So how do we pick the
right game engine? Well, I'm glad you asked. We're going to talk about
all these questions that you should answer. And if you don't totally know the answers yet, That's alright. The next couple of videos we're gonna be talking about breaking your idea down into more
features and tasks. And that may help you ultimately decide on
the right game engine. How big is your team? If you need to pass
files back and forth, you'll need some sort of
source control that's smart enough to lock files and deal
with merges and conflicts. Even if you're
working on your own, you'll want some kind of backup so you don't
lose your work. But the more people
that are in the engine, the more support you need for an only keeping track of changes and not
losing that work, but commenting and making
notes for one another. What's your technical
experience? You love to code or are you
doing it because you need to. What languages do
you like working in? Some engines are much more
coating heavy than others. I do believe you can make a game with limited coding experience, but you will probably
want to pick an engine with all
the features you want already built or provided
as add-on assets. Because your games
single-player or multiplayer, some game engines won't have support for multiplayer and some will consider if you're going to need servers are lobbies, multiple controllers,
text and video chat. My recommendation for this
course is that you pick a single-player game because it's simpler and you're
more likely to finish. But I get it. If you're passionate about
multiplayer games, then no, you're adding on a bit more
work to not only build them, but playtest them and fix the bugs that are
unique to them. Do you plan on
selling your work? I know that I said we
weren't going to focus on it that much in this course, but we do have to
bring it up because some engines or a onetime fee, some are free with no
royalties expected, and some do expect
that you pay them a royalty if you make over
a certain amount of money. Now the good news is for your first indie game or one
of your early indie games, It's highly unlikely that you will get over that
threshold if you do, I'm very excited for you, but you should know that
you would be expected to pay royalties if you use
some of these game engines. And then what
features do you have? We're going to dive
into that more deeply in the next video. But some of the game engines
out there are specifically made for certain types
of gameplay genres. Finally, what platform
do you want to support? This is also a question
about interaction model. If you're releasing a game for mobile than you're
gonna be doing touch. If you're releasing for PC, you're probably doing
keyboard and mouse, maybe controller as well. And then there's other
platforms like VR. There's all these different
interaction models. And you should know
which ones you're planning to support
from the beginning, because you'll definitely
want to make sure the game engine can
support them to. So as for my recommended
game engines, I have too many of them. So I ended up just making you a project file that lists all of my favorites and has
some information in there about what makes them
distinct from each other. And you can look at what you've answered in this checklist and cross-reference with
those game engines and see which one is a good fit. Let's talk about
some other tools. I'm not really talking
about hardware, although depending on
your interaction model, you'll want to have the
controller that you plan to use or VR headset or whatever it is that you need
for your type of game. And you're going to need
some kind of computer, usually that will help you do all your coding
and everything. Let's talk more about the
software side though. You'll want a word
processor of some kind, a note-taking software for your game design
documents and planning. In most cases, you
can use the same one that you're using
for your idea home. I recommend notion or OneNote. I know other people
like Evernote, or they like different apps that they have on their phone. That's totally fine too. You'll probably need a code
editor that makes coding easier with features like autocomplete
color-coding and search. Notepad Plus Plus
is a great choice. I also like Visual Studio. Having an image editor is really important
because it will let you capture your design
sketches and later on make or modify
your 2D assets. I mostly use Photoshop
for my assets. My paint on NADH can be used as a free alternative as
simple audio editor is also great to have. You may want to record
dev voice-over for a social media post or edit
music and sound effects. I use Audition or Audacity
for my editing needs. You can also record
directly into the program. I'm personally not experienced
in music creation, but I asked a couple of
my composer friends. They said that
GarageBand for Mac, cake walk by bandy
lab or Reaper are all good options for people that
are making their own music. If you're making a 3D game, you'll want software
that can make 3D models, textures, and materials, and help you rig and animate
your characters. I personally recommend blender. It's free and powerful. There are so many
tutorials out there that can help you get
ramped up quickly. Blender also works
really well with the top 3D engines,
Unity and Unreal. You'll be making UX of some
kind while making your game. And you can totally
get away with doing paper sketches and using
your image editing software. But if you're more
experienced in graphic design or
you want to level up your UX experience skills and have a more refined
touch to those screens. I recommend a UX Design app. I like to use Figma, but I've also enjoyed
using Adobe XD and Azure. You're going to want a
way to track your tasks. Many Game Studios use heavy-duty planning
software like Jira. But if you're just
starting out with a small team or by yourself, you can use any task
tracking app that lets you set deadlines and
has checkboxes. I like using Notion, but you can also use
Miro or a whiteboard. The last tool I'm going to
mention is screened to give. This is a free tool that lets
you easily capture areas of your screen and as you might guess and make
them into gifts, you can resize crop, add watermarks, remove frames, and change the timing. Making gifts of your games
as you're building them is a really cool way
to look back on the progress that
you've already made. Having a tool like
screen to give makes it super
easy to just grabs a little fun animation
or something that you're working on without having to put too much thought into it. Alright, we got to
the end of the list. I know that was a
lot of information, but you're going to feel so good having all these tools setup, and knowing that you
have exactly what you need when then moment arises. So let's talk about
your homework. Go through the game
engine checklist and narrow down the options
for this game project. Download one or two engines
that suits your interests. Do a simple tutorial in each engine that
you're considering. Something like drawing a square
with a words HelloWorld, compare how each game
engine made you feel. Choose the game engine you'll
commit to for this game, search online for tutorials and videos series using that engine. So you can quickly
update your skills, install other software
tools that you'll need as necessary for your project and play with all
your new software. Don't get intimidated
if you open something and you get
stuck or overwhelmed, you can learn about them later, but at least know how to open them and see what
they're all about.
6. Prototype: Idea to Features: Okay, so you have your idea, you have your setup
with all your tools, you're ready to get started. But maybe you're
sitting there thinking, now what I don't
know what to do. I know I have an idea, but like what's the first
thing you start with? So if this is happening to you, you may be having
trouble breaking your idea down to features. And that's what this
video is about. Let's talk about some of the
ways that you can do this. Features are essentially
just parts of your game. When you buy a game, you're
probably only looking at the top features
list the things that are most important to make you want to buy
that game and play it. But as the person
making the game, you actually need to consider every little thing that is needed in order for
it to be a full game. My number one tool for
breaking down an idea into features is the
game design document. The act of writing a game
design document, or GTD, helps you break down all the little pieces and understand how this
game really works. The GTD is a document
that describes your game is for you and whoever
else is working on this. And I do think you
should make it even if you're the only one. Because back to the
whole idea of thing. We may think we're keeping
everything up in our head, but by writing it down
in articulating it, it takes that space
in your brain. We're keeping how
this game works, puts it in another place where
it's easier to parse later and can be easy to
review in the future. And this is especially good when you're doing indie
projects because you may be stealing time
like once a week or five-minutes in the
morning and it's in-between a lot of other
stuff going on in your life. So having it all
written out somewhere, how does this game work? What was the last feature
I was working on? Having that all written
somewhere as a huge help. Here's how you do it. In the project file. I put a starter
table of contents for your GTD so
you can copy that wherever you're
planning to write your GTD and make
modifications as you need to. You can cut some
sections if they don't make sense
for your project, where you can add some that
you specifically need. I specifically didn't add
too many details about the different systems because I don't know what kind
of game you're making. But if you know your
gameplay genre, then you'll know what those features are
and you can add them. I also added a GTD
feature template for each of the topics in
the table of contents. You can make a sub page
or add a page below. Then it's just a
matter of filling it out and making it
makes sense to you. It may seem like it's
a ton of writing, but don't get overwhelmed. You can use diagrams
and tables, flowcharts, images and sketches, anything that's
going to help you figure out what this is. The ultimate goal of the GTD is that it's
something that people on the team look at and everybody understands how the game
is supposed to work. Or another way to think
about it is this is the design and whoever's
doing the implementation, whether it's you or
someone else on the team, should be able to
look at the design and know how to build it. There's a lot more to
be said about how game design documents work
and how you write them. We can't focus on
it in this course. So to help you with
game design in general, I also included a list of books that I recommend
on game design. Remember, the point of this is that it
works for your team. So if some part of my town's
lid doesn't work for you, people on the team
don't like it or they want it split
out a different way. That's okay. Being flexible is one of the most important things about
making a game design doc. From the game design doc, we now have a feature list. The feature list
is that table of contents plus whatever
changes you've made to it as you build out your
GTD from the feature list, we can now prioritize
our features. So I want you to copy
the features that you have come up with
into another document. And we're going to sort
and prioritize them. The way that you're
going to sort your features is first
by prerequisites. If a feature requires another feature before
you can get started, then you need to put that
feature higher up in the list. For example, maybe you
want to build a shop. You want your players
to be able to spend money and buy items. In order to do that, you need to have money as
a concept in the game, a wallet where you can save the money that you
have and you need to have an inventory
of some kind that the player carries around
what items they have. You can put both of those above the shop interface and
your priority list. The next thing you're
gonna wanna do is label each feature with
a priority number. And you don't have
to use numbers, but it's pretty
common to do that. So p zeros are
features that you just literally cannot ship this game without because they
won't function. So if you have a platformer, you would probably say P 0 is the player can control the
character and move it around. A P1 is something that if you
didn't have it in the game, your players would notice
and it would hurt to not do. Technically, you could
ship the game without it, but you really don't want to because it adds so much value. A p2, it's a nice to have you really wanted it's going to make
your game standout, but you have to admit that
you could technically ship without it and
added at a later time. Then P3s and P4's not the most important
things in the world. But sometimes you just want to label all the cool
ideas you have, even if you don't think
you'll get to them for awhile or you may
never add them. So resort or your feature list. And this is going to
help you choose what features you're going to
work on and in what order. Now it's homework time in order to hone your
game design skills. Here's an exercise
I'd like you to try. Pick a game that you love, and now pick one specific
feature from the game. Go ahead and play that game and really explore that feature. You might want to
pick a small one like a single menu screen or a character or attack a collectible item
or a player action. Use the GTD template to write a game design document
around that feature. Essentially you're going
to reverse engineer how it works and
describe it in words. Your goal is to make the
page complete enough. Someone else could implement it. Don't forget to make note
of any sounds or images, animations, or other
assets that are used to make this
feature happen. You can use this
exercise to practice several more times across
other games that you love. And when you're
more comfortable, you can return to filling out your game design document and see if it's a
little bit easier to describe the features that you want to
make now that you've seen how to break them down from other games are
already published.
7. Pre-Production: Task Tracking: What's the most important skill that you can have
as the game dev? It's not your coding prowess, it's not your artistic talent. It's your ability to
manage your own time. So let's talk about
task management, which is essentially taking the features that you've
already discovered and breaking them down even
smaller into things you can add to a task
list and start doing. When we talked about tools, we talked about having
a task tracking app. And even from the beginning, you're going to want to start
throwing things in there. I keep mentioning using these
tools as extra brain space. And I really believe that
often when I just have an idea or I realize we
have to fix that bug, or we have to make sure that we don't forget
to do this later. I'll just throw it at the
back of the task list. So starting this task list
early is a good idea. Now, my task lists are in Notion and I labeled
them with lots of different properties I have
who's assigned to do the work and estimate what milestone is supposed to be for
the type of work, what deadline, and
often what feature, or even some attachments. If that's something
important to the task, then I can filter them and
notion by whatever I need to, I can view them in
different ways. This is pretty advanced, but it's worth thinking
about things in terms of databases because it will make things easier for
you as you go along. You're going to go down
your feature list. And for each feature, just start making whatever to-dos you think there
are to make that feature. So if I add a feature like add a health pickup in the game, I might say art asset
for health pickup is a task and sound effect for
when I collect it is a task. And player can pick up objects and an action will
occur as another task. And healing is another task. I just started listing all
these things and by having labeled them all involved
with the health pickup, it really helps me. So this is just
your initial list. You're going to come
up with new things and you're also going
to come up with some of your tasks
just being too large and they need to
be broken down further, but don't get too overwhelmed. And then we can move on
into estimating time. It's really hard to
estimate creative tasks. We're not really good at it because even if you've
done it before, there are so many
variables as to like how this one will
take more time, or you might be fixing
a bug and there's no way to really know
how long it will take. It might be an hour long task or a three-day task depending
on the complexity of it all. But it's still good to try to estimate your tasks
because that's what ultimately gives us a rough idea of how long it will take
us to finish our game. So you may have
seen people talking about estimating tasks and time, like how many hours or days
it takes to finish something. Or you may have also heard of something called Story Points, which is part of
this agile system of task tracking and doing
sprints and getting work done. If you already know how
to do those and you prefer that, that's fine. But I think this one's a
little bit easier to handle. And this is called
T-shirt sizing. You're going to sign
all your tasks. A t-shirt size. From extra small, small, medium, large, and extra large. And extra small is
usually a task that in your mind you're thinking nothing that's
like half an hour, that's like a few minutes, but you still want to
give it an estimate. So you know that you're thinking it won't be
much time at all. And an extra large task is
probably something that needs to be broken down
into smaller tasks. So you're almost saying, I don't even know how
much time that is. Let's just bucket it over there and then worry
about it later. Now you can look at maybe
some tasks you've done before and started thinking about what would you call them? What is your example that helps you of what a small task is, a medium and a large. And it doesn't really matter if my version of a small Is a day, yours is four hours and
someone else's is one week. What matters is that you
understand what that means for yourself and that you understand that the comparison between different tasks makes sense that a medium
task is always gonna be more for you
than a small task. You can also make
a little rubric or cheat sheet that has
for each t-shirt size. Here's an example task. So I might make this with
tasks I've already done. And then when I'm looking
at task and I'm like, I don't know if this is
a medium or a large. I can look at my
rubric and say, OK, I said that this
was a medium and this new task is
more work than that. So I'm going to
say it's a large. Now, just like we did
with the features, we're going to prioritize
our tasks too. And even if a feature has to
happen before another one, like we said, the tasks can get a little
bit more split out. So typically anything that's like a little bit more policy like choosing the
final sound effect or the final animation. If you come a lot
later than something that's like just
make sure it works that you can have money in your inventory and then
we can build a shot. At this point, you probably have a really long task list, okay? And that's very
overwhelming to look at. You're going to want
to split them up into milestones or sprints. Now for me personally, if I'm working on
another studio, we usually do sprints. One, 23 weeks with indie work. I don't really like to do
weekly sprints because I'm working with different
people and they're all on different schedules. So I like to do
milestones instead. I'll roughly say like, you know, our milestone is by the end of this month to
get this feature done. And I only want to look at
the tasks have to do with this feature Olin like
five things from the top. When you finish those five, you can pull in another five. So that's one way that
you can slowly go through your Indy work without being overwhelmed thinking
of task boards, a kanban board is
essentially a group of columns and you get to visually move something
across the columns. It's useful for
things outside of tech and game industry as well. I like to have a ready column. These are tasks that are
ready for somebody to start making a not started, which is basically the person who's assigned to it
as pulled it from the ready column to let everyone know who they
are planning to do it. An in-progress, which means
they are currently working on it and a completed
which means it's done. And if you're working
with other people, I'd also like to have a blocked column and
a review column. The blocked column
is if you need something from somebody and they're not done
with their work, unless your producer or
your lead now that there's a problem and they need to come talk to you and see
how can they help you. And the review column
as if a task isn't technically done until
somebody has reviewed it, you can put your work in
there and then whoever's responsible for
reviewing it will then have to go through
your task board, give you the thumbs up, and then move it
on to complete it. Now, when is a task finished? It's really important
with game design and game development to do things
in an iterative process. And that can be really hard because wouldn't
it be great if we could just design the
perfect game, build it. And it was just done with no need to update it
or tweak it at all. Most commonly though, as
people play your game, you're going to
learn things about what your audience wants. You're going to see things
that you want to change. And for all these
reasons, it may feel like a task is never quite done. So I recommend that the
first time you do a feature, you call it something
like first-pass, initial drafts,
something like that. And that lets you
finish that task, even if you're looking at the first version
and you're thinking, well, there's a lot more
we have to do here. So as long as you have
something in your backlog that acknowledges the fact
that there's more work to do. You're okay to finish the task and feel accomplished
that you've got it done. So here's your homework. First, you're going to set up a task tracking software
like Miro or Notion, or you can use a whiteboard, especially if you're just
working by yourself. Take one of the
feature pages that you made in the last video. Make a list of all the tasks you know of right
now that you need to finish that feature and place them on your
task tracking board. Repeat this process whenever you finish your
work on a feature, if you're having a
good time with it, you can also do it all at once and prioritize
the whole game. But be careful not to let
yourself get too overwhelmed. And remember, every
time you come up with something else you need
to do to finish the game, make a task for it
and your backlog.
8. Pre-Production: Building Your Skills: At this point, we're
now building the game. We're going through our tasks
and we're finishing them, and we're making progress. And it's really common
for us to get stuck here because we feel like we don't have the skills to continue. We're having trouble
learning something. We're just not up to par
with what we wanna do. In this video, we're
going to tackle what does it mean to
build your skills? How do you get the skill set you need to
accomplish your game. One of the best
things about making games is how
multi-disciplinary it is. But it's also one of
the hardest things about making games because you have to be good at so many different things
in order to make them? Or do you, you actually
have three choices for every type of task
when making a game. So repeat after me, do it yourself or
pay someone else, find it free and legally and technically
there's a fourth option, which is to omit it completely. But if you're doing that, you
should have a reason why. Maybe you're making
an audio-only game because you want it to be really accessible to people who are
vision impaired. That's an awesome goal. It doesn't have to be
something specific like that. It just has to be
something that makes sense for the narrative
or the gameplay. So it's not that common to
omit something entirely, but you can do it in general. Let's focus on these
other three categories. Doing it yourself. Who doesn't love the story
of the solo indie dev. But there's not that many
people out there that are actually equally adept
and all of those things. And in fact, all those people who are doing it all themselves left to learn all
those disciplines and work really hard
to be good at them. So don't be too
hard on yourself if you don't want to do
everything yourself. Most of us specialize
in only a few areas, and that's where we
want to spend our time. So lean into that, figure out what are the areas of game dev that you
actually really enjoyed doing and consider
a specializing in that, because the other aspect
of trying to do all of it yourself is it's just
going to take longer. There's no way around it. So if you're trying to
finish a game faster, you should only do a few
areas yourself entirely and lean on those other options for things that you
don't like doing. Not as skilled at, if you're certain that
you do want to do every aspect herself though, make sure you've picked a really small game to start with. Scope it down. Because then you're
gonna get done faster for those areas that you have decided to invest in and that you will
be doing yourself. You should set aside time to
learn and grow your skills. And this isn't just
true for game dev, this is true for
life in general. For example, if I decide today that I wanted to
own a pet snake, I personally would not just go to a store and buy a snake. I would start watching videos. I'd call up friends
that own snakes. I would read articles online. I would talk to somebody
at the pet store. There's a lot of different
ways to do research and prepare yourself for
something before you do it. Whether it's fixing up
something in your house, learning to make a
meal or making a game. So think about what you do and other aspects
of your life when you want to learn
something and apply any techniques that work for
you there to your game dev, learning a new skill
as a combination of research, observation
and practice. So make sure you're doing a
little bit of all of that. And of course you're
always iterating. So if you don't like
your first version of something you
put in your game, you can update that
later when you have a little bit more
skill and don't feel bad about taking
notes along the way. I often take notes
when I take courses online for different types
of tools such as blender, because I'm really bad at remembering keyboard shortcuts
and they change a lot. So then I can go
back to my notes the next time I returned
to that kind of task. So paying somebody else, there's basically two
ways to go about this. If you want to buy
something that's some ways already made in an asset store. That's a really
straightforward way to do it. You know how much it costs. It's probably already
been vetted by the store or by other people
who have purchased it. So you know what you're getting
and it'll work for you. And there are plugins and assets in many stores that are
divided by game engine. Even if you're using a game
engine like Unity or Unreal, there's already a lot of
people out there making contents specifically
for those engines. Firing a coating plugin is
a great way to save time because you don't have to
make that feature yourself. And nobody is really going to notice that you bought
it unless they're looking at your credits or they're already a
game dev themselves. But if you're buying art
assets or music assets, you do run the risk that there
was another game out there already using them
because they're being offered for sale for
many people to use. So you may lose a little
bit of originality there. And if you're fine with that, because this is more of a
portfolio piece, that's fine. But you could also
edit them so they fit into the style that's
unique for your game. Now if you're working
on a creative team with somebody else that's
more challenging. You have to treat every creative collaboration
like it's a marriage. And that means that
you need a prenup and you need to know what
happens if you divorce. So it needs to be
clear up front. You equally own this game. Are you giving away royalties? Are you just paying them
for freelance work? And everybody knows you own the game and they are
getting credit for the game. All those details
have to be figured out even if it's a
friend of yours. In fact, I think it's more important if it's
a friend of yours because it's so easy for something like this to
harm your friendship. So thinking about and talking about before you even
get into it, hey, what happens if I no longer
want to work on the game, or I lose interests, or I'm too slow, what do you want to do about it? That's a really important
thing to talk about. Two, also, I know
many of us have limited funds and you
may be thinking you can't afford to have
somebody else work on your game and pay them
for their efforts. But if you're not paying or offering
something of value to someone than they have no
reason to meet your deadlines. It's really awkward to tell somebody to work
harder if they're not getting anything that's helpful to them in their life. Sometimes people that are starting out or just really
want to work with you will be willing to work for a lower rate because they loved the project
or they love you. I think the most
important thing is to talk to people and say, Hey, I'm doing this thing. I'd love to do it with you. I can offer you
credit in this game. How much would you
charge for this? And then if it's above
what you can pay, you can honestly say, I'm sorry, I just
don't have that money. And maybe you can work out some kind of deal in the middle, like but you could
sell stickers of the character or you could get royalty when
the game comes out. Royalties are hard
because you don't know if the game is
going to sell or not. But if you're really
good front of somebody and you're willing to
do that work with them. It can be something
that you offer. So just listen to
other people and be respectful and honest and find a deal that
works for everybody. Don't forget to give credit to people when you
use their assets, whether he bought
them in a store, or whether you worked with them collaboratively
to make this game. I just don't personally
see the reason not to give credit to people that helped
you and worked on the game. It's up to you how
you want to divide that up in the game itself, but it doesn't cost
you anything and it shows that you respect the
people that you worked with. Finally, there's find it free and legal with the
emphasis on legal, there's actually plenty of public domain things out
there for you to use. And maybe you want to be
really creative and find some older painting style
to use in your game or some recordings of music
that are public domain. Just make sure that
you have the license, you know what's expected
for you to use it. And then you give the
proper credit, attribution, whatever is required of you
when you do ship your game, your homework, go through the project files and find
the task type sorting board. Rank each one based on
your skill level and interests and choose which
categories you will invest in. For each row, make a list of things you plan to
buy or find online, read the licenses
of any asset you plan to use that's
not made by you. Block out time each
week that you will devote to increasing the
skills you want to master.
9. Production: Is it Worth it?: It's time to face the
inevitable existential crisis. Even working on your
project for awhile. And you're asking yourself, why am I even doing this? Why did I start this
in the first place? Is it worth it to continue? This is the first of
several videos where we're going to talk about some of the mental blocks they
are going to have. Being creative is hard and there's a lot of
pressure being put on you, and you have to be
very self-motivated. So you may find yourself
procrastinating. Now, procrastinating happens
because we are creatures that seek to avoid the
path of the most pain. And so if there's
something that we perceive to be painful
for some reason, we will avoid doing it by doing something else
or nothing at all. And the first thing you
wanna do is ask yourself, why are you procrastinating? Sometimes I find that if I
just say the reason out loud, it helps me come up with
a way to get around it. So for example,
maybe there's a type of icon I need to
make in the game. And I realize I'm procrastinating because
I don't like though art that I make when I attempt icons and I'm already
anticipating, I'm not going to like the
result of this and I'll feel like I wasted my time
if I say that out loud. Now I'm starting
to think of ways that I could get around that. I could choose to take a video course that'll
help me make icons better. Or I might decide that
I'm going to look for somebody who's
already made an icon set, like the one I want to make, or somebody that will
make custom icons for me. Another anti procrastination
tactic that I've used, this is going to
sound really weird, but it works is to pit two tasks against each other
that you don't want to do. I've found that I
will start doing basically anything
I can possibly think of if I have
to do tax work because that's the
thing that I hate doing the most personally. Now let's also talk about
the new shiny idea. This is a huge reason why
we stop what we're doing. We go all the way back to the concept phase and we started getting you have to
put it away for now. Okay. Put it in your idea home, put at the top of your list. I'll even allow you to have a cheat day just for one night. I'm allowed to work
on the cool new idea and I'll do a bunch of
design work for it. And that's usually enough to get it out of my
system and I can return to the game I'm currently
in the middle of making. But do your best to get more focused on what you're
doing right now. Every game goes through this
middle building process. Don't want to just
keep rewinding and going back to the beginning. If you're looking for
more help on how do you get past those tedious moments. Let's talk a little bit
about being discouraged. So there's many
reasons why you may be feeling less confident now
than you were when you began, when you first start
out and you're building your concept phase mood boards and you're planning your ideas. It's only the limit
of your imagination, how great your game
is going to be. But now that you're actually
seeing it come together, it's normal to be a
little disappointed because you're seeing
some doors close. You're seeing how some
things are not going to match the target that maybe
you wanted them to be. Or it may even be
that somebody says something hurtful
or mean to you. They may not have even meant it. When we were making
mobile games, are families only had an idea of the games that they like
to play on their phones. So they would give
a lot of advice that wasn't necessarily helpful. Like, is your game
hooked into Facebook yet or even the, Haven't, you made millions of
dollars yet because I'm playing this game that has
made millions of dollars. And it can be kind
of embarrassing to tell people like, no, it's not really what I'm
doing or it's not that easy because they're not living that life the
way that you are. The truth is it's
just much easier to tear someone down than
it is to lift them up. And people that don't
make things may not understand your goals are
why you want to do it. In general, you just
have to remember what's the reason why you want to
do this in the first place? And try to focus on that. You're the person who
gets to ultimately decide how you live your life. If you're feeling
particularly unmotivated, it's time to refill your creative well and you
do that by taking a break. Sometimes that really is
the best way to do it. Go for a hike, go for a day trip
somewhere with your pets, and maybe just
walk in the woods. See your family, read
a new book series, whatever it takes to get
yourself inspired again. And you'll see that
sometimes taking time away will make you rethink something that you
thought was boring. We sit back down
to your project. You're going to have a
whole new mindset about it. And finally, there are times when you really
should give up. It could be that the
game that you want to make isn't something you're
super interested in. You might actually feel
like you don't have the motivation to
finish this idea where life gets in the way
you're going through a wedding or someone in
the family has an illness, you have your own
health problems. You're graduating
college, whatever it is, you have to make time for
things that happened in life and happen around you
to the people you love. So don't feel bad
if you're taking a pause for something that's happening in the real-world outside of your
game development. That's okay because you can
always come back to it later. Just make sure that this isn't a recurring theme with you. Don't quit because you're
bored, because you're scared. Don't quit because somebody told you it's not
worth it to do it. Quit for your own reasons if you feel they're
strong enough, okay? So your homework, take some time away from
your project to rest. Go on a day trip, watch
movies and read books. If you find yourself
procrastinating on a task, write down y, and then see if there's
some way to alleviate that issue by looking
at it a different way and make a plan to reward
yourself for doing the not fun parts of a game or accomplishing
a huge milestone.
10. Production: Finding the Time: It doesn't matter how big
or small your project is, you are going to have
issues finding the time. There's only so many
hours in the day and everybody's fighting for a
slice of your attention. So let's talk about how do we find the time for indie project. So time is what we make of it. It's a precious resource. You're constantly going
to be making trade-offs. You can't just work, work, work whether you have a day
job outside of making games, or whether this is your
main source of income. So make sure that you're
making time for your health, for your basic needs, for the people that
matter to you, for things outside
of making games, because that'll actually help inspire you to
make better games. Not to mention some of us have other circumstances
like health conditions, financial restraints,
things that will get in the way and
take away or hours, be kind to yourself, okay? Don't hold yourself
up to others. Don't say, hey, this
person I know made a game in a weekend or they
made a game and six months. Everybody is on a
different timeline. Everybody has different things that are important to them. Only compare yourself
to yourself. You know, that's, that's
what's really important. And don't feel bad. The important thing is
that you're making space, you're carving it out to get
things done at your pace. Okay, so how do we do that? I like to call this time blocks. No matter if you have a day job or you're working
full-time for yourself, you're probably familiar with having some kind of calendar blocking out time on it for meetings and other
things like that. Dedicated time
blocks can be about a certain skill or just about
your project in general, I also think it's helpful to do time blocks that require
the same mental space. Because that gets
you in that mindset. If you're doing
things that are very similar to each other, then you're probably going
to make more progress. So if you like to do music
tasks for your game, maybe do a day that's
like music day. And the whole day
you're just focusing on audio and it doesn't
have to only be productive to I have
a time block in my weekly schedule where I look at things
from my own health, like if I need to make
a doctor's appointment, you could have a space
that's like family time. We have a space in
the mornings for when we take the dog out in the morning and spend
time playing with her, those are important in too. If you didn't do your time
block and you feel stumped, you've got creator's block. That's okay too. Just the fact that you're
sitting there looking at document and getting in that
mind space once a week, it's going to help you
make more progress. So don't get frustrated if some weeks are
slower than others, it's still important
that you made that time and you let yourself have that space where you're specifically working
on your game. Now if you are having
a creative block, I recommend a
technique where I make a different music playlist for different types of tasks or different characters
are stories. And I listened to it
during my time block. And I get used to the fact
that this hour long block of songs will always play when I'm thinking about this
character in this game. Over time, I've noticed that when I hear that
first song start, I'm already getting
into the mode to work on that game and
work on that character. So it's really helped
me get focused and be in the zone faster
during my time blocks. There's also software
out there that can help you with your
task tracking. I like to use something
called toggled track. I think I've also used
rescue time before. These are software
that can even look at what apps you're using
on your desktop and give you a little report to say
how long have you spent maybe scrolling
through social media, browsing when you
should have been doing work or how
many hours did you really spend in Photoshop or in your game
engine this week? You can even label
these to save this as productive time and this
is not productive time. You can also go a
step further and use blockers that blocks or
insights for a time period. So you can't get distracted by social media or other things
that you'd like to look at. You're supposed
to be doing work. So your homework, create
one or more time blocks and your weekly schedule
where you're going to spend time on your
indie game project, install a task
tracking software, and consider installing
a social media blocker. Create a music playlist
for your project. Listen to it while you work.
11. Polish: Fighting Perfection: No matter how hard we work, we are rarely 100% satisfied
with the end result. And it's really important
that in game dev, we don't get too stuck on
making things perfect. You might end up with one
incredibly detailed 3D chair and missing half of
your game features. So let's talk about how
we fight perfection, how we become okay with the level that we're
able to create, and how we get things done. First of all, remember
that you are indeed, you may be looking at AAA
games for inspiration, but those games are being
made by hundreds of people that have been
working for many years, sometimes a decade or
more on this project. And nobody is holding
you to that standard. You may be trying to hold
yourself to that standard, but consider the fact
that the expectation of your player will change the
more polished or game looks. And when people know
that you're Indie, they love and respect you for what you're able to do
on a smaller scale. Bigger is not always better. So don't think that
you have to make the most hyper-realistic
everything in order to have a great game. We made that priority list
of features for a reason. I know that it's
important to you that everything looks really great, but we want to focus on
what's at the top of their priority list
because that's what people really care about. If there's a singing
mechanic and your game, because it's a game
about karaoke, you're going to want to focus on that and nobody's
going to notice the coffee mug that's on the table in the back
of the karaoke bar. That's something that
you can simplify or make much lower resolution
than things that are up and center
in your art style. So really think about that priority list
and be strong and steadfast that not everything has to be super highly polished. What has to be
highly polished is the things that are high
priority to finish your game. We talked a little bit
about tastes level before. As you continue to
grow your skills, tastes level is going to grow to and you're not gonna be
able to always meet it. Don't be surprised
if you're like, wow, I just painted the most
amazing background. And then a couple of months
later you look and you say, Oh my gosh, I had some
weight flaws in it. That's normal. That's because you are
growing as a creator, whether this is in
terms of coding or art or music or design, whatever discipline it is, this project and future
projects will be better. You also may have heard the term perfect is the enemy of done. And it's easy to
say that and not live by those words,
but it's true. We're trying to get
something done. And you may be thinking, I can't possibly leave
that bug in there. I can't possibly leave this weird-looking
art acid in there. I want you to think about other games that
you've enjoyed though. Have you ever played a
game where there was a silly bug and you had
a lot of fun with it. Or where there was
like a weird line of dialogue or a funny animation. Players, they may
complain about bugs. And it's usually because of bugs that make it impossible
to play the game. You have to prioritize
fixing things like losing your save file or things that
make it impossible to win. Those are the bugs that
people want fixed, but things that are just silly. It's okay if you leave
them in the game. It could actually give your
game a lot of personality. It could give people playing
your game a sense of community that
they really enjoy. So try to look on the
funnier side of things too. Sometimes the best thing
that we need during the polish phase is perspective. So if you haven't already, you should consider
doing some play testing. I will choose a few
different types of people to test your game. Ideally, they're all people who have your best
interests in mind. They may be rooting
for you to be successful and your
creative work. They may be people that
also love making games. Somebody who's not
going to just rip it apart for no reason, but somebody who genuinely
wants to have fun, wants to see you succeed. And of those people, it helps to have those that
have never played this game before and those that are really familiar with
this gameplay genre, because you're gonna
get different types of feedback from both. You should know how much
of the game you're gonna show before the
game-play session. Plan a 15-minute section of it. If you don't have a
tutorial in your game yet, because they're printing
out a cheat sheet with the buttons on it or some info about the game that people
won't get from your demo. And there's a few
things to remember while you're watching
the play tester. They are aware that
you're watching them. They're going to try
to do their best. They might be embarrassed
if they struggle. So you need to make them
feel very comfortable. If somebody is embarrassed
or saying, Oh, I'm failing a lot, continue to reiterate to them
that they're not failing. You're learning
from them playing. You're learning a new way to
see how your game is played. So make sure they know
that they're super valuable and that you really are happy that you are seeing a different type of
person play your game. Also, if people
have feedback about something that's not
working very commonly, they know there's a problem, but they don't know
the right solution. So make sure you're focusing
on someone's saying, I don't know how to get to the
next area more than their, their idea they might
throw out like maybe you could put a bridge
here or something. That's interesting too. But you know the details of
your game more than they do. So make sure you're
focusing on the problems. And as hard as it is, try not to talk back
to your play testers. Try not to explain. Oh, well, we had to do it
because of this or well, you'll find out later
why that happens. In general, you
just want to say, can you clarify or oh, that's good feedback and that'll keep the
conversation going. And it's unfortunately our
tendency as the creators to want to tell them everything you know about the game as
they're playing it. Also people are
telling you things even though they're
not saying everything. So pay attention to
their expressions. When there were their eyes light up. What are the parts are? They seem to be more confused. What are the areas that they
tend to gravitate to and the level and take lots
and lots of notes. And finally, your game will
never be for everybody. Okay, that's fine. So you may get some
people playing and you might be embarrassed thinking, I don't know if they
had a good time. They seem to really
struggle with it. Some of those doubts
might start to come back. Your game is for somebody. First of all, it's for you. You made this game
because you wanted it to exist and you wanted to play it. And there'll be more people
like you that want this game. So don't worry so much if you do run into
somebody who's just like, Yeah, this isn't my thing.
Here's your homework. Show your game to someone
who hasn't seen it before and is rooting
for you to succeed. Look at your prioritized
feature list or you polishing the most important
elements of your game. Are there parts of your
game that you can spend less time on without
losing too much value. Bring your game to
a game dev event or an online social chat for game devs make new connections and see
what others are doing. Then show them what
you're working on. Post something publicly
that is a work in progress. And don't worry too
much about the fact that it's not done
and not perfect. Make a list of post-launch task that you'd like to
return to later. Contemplate the fact that you
may never do those tasks. And that's okay.
12. Release: Meeting Deadlines: Some point you do have to stop working and
it can be really hard to figure out when is it
actually going to be done. So let's talk about
what to do when you're nearing the end
of your game process. And you're trying to figure
out when are you going to release and what goes
into releasing or game. Releasing your
game is made up of a technical side of community
side and a marketing side. And we're gonna be focusing
mostly on the technical side, though we'll touch those
other two in the next video. A release simply means that your game is available
for other people to play. They may be getting it for
free or through a store, but there's some way
for them to get it on their devices in order
for them to play it. Well, you can make your
game available yourself by hosting it on your website or
giving it away at an event. In most cases,
you're going to be offering it through
someone else's platform. And when you offer it as
someone else's platform, there are rules that you have to follow in order to
get a released. If it's for a mobile platform, there's going to be an app store if you're offering
it for desktop, most people buy
games through steam, but there's also a
CIO and Windows. I would recommend
if you're doing a desktop game that
you start with initio, It's a quirky game site for indie games as a
really great community and it's really easy
to get started. The back end of how you publish your game
is super-simple. Plus people and NGO or used to things that
are prototypes, artistic experiments
are works in progress, whichever store that you choose, you're going to see that
there's a lot of requirements. There'll be some visual assets that you need a very
specific sizes. There'll be some texts
they expect you to write. You may also need to improve your build through the platform, make sure that you have
planned it out and that you've made time to make
all these assets, because it may seem easy, but it's actually a little
tricky to figure out. Now how do you set a release
date and a perfect world? You haven't done this yet. And you can look at
the remaining tasks, look at their estimates, figure out about how many hours a week that you're working. Buffer it out. If I have some small, medium and large tasks left. And I know a small
roughly takes me a day, a medium takes me
three or four days, and a large takes me a week. I can say, okay, this is how many weeks
that I have left by just doing some addition
and multiplication. I'd also want to add
some extra time on that, because once I finish
all my features, I want to just
have the luxury of playing through and
fixing some bugs, showing it to people,
making sure there's nothing there that
would cause a concern. So with that in mind, I would probably use that method and set a
release date once I'm pretty close to
finishing and I'm really confident that I'm going
to finish by that time. However, you may have
already set a release date, and if you've done that, you are left with a few options. So let's talk about
what those options are. The first option is
the worst option, and that is crunch and burnout. This is the option where you don't quite have enough time, so you just work
harder and longer. And you can start to recognize when this is
happening to you because you'll start to feel
these physical symptoms like racing heart. You get up too early, you have trouble going to sleep, you dried, getting
to your computer. You're really tired
because you're putting in too much extra effort. You're starting to get a
brain fog because you're not doing much else
other than then working. This isn't good for your game
and it's not good for you. It does happen. It happens in the game
studios that you may work at. And it happens when
you work for yourself because no one cares about
your game more than you. And it may seem
like you're doing something really great because you're having a
lot of fun and you really want this
game to be perfect, but you're harming
yourself in the long run. So remember that making games is a journey and you're just on the first
leg of the journey. And if you don't take care of your body and take
care of your health, you're going to regret
it in the future because you won't get
to make as many things. I've definitely had
nights where I decided I was going to work all
night to finish up a thing. And in those cases, what I do is like mandatory
rest the next day. I'm not allowed anywhere
near the computer. So there's a cost for it. But it's really important
because your brain does get tired when you do this and you're not doing
your best work, the most obvious thing to
do is push out the date. And in most cases
you can do this. If you don't have a lot of
people expecting this game, you can do this pretty much
silently just change the date and maybe inform your discord or posted on your social media. If you want to explain
a little bit more, you could even do a video or a dev vlog and tell people why. And in most cases, people
will be understanding that the game will be better if it gets delayed a little bit. Just make sure that the new
date is far enough away that you will actually get
what you need out of this. You may even want to
give it something like next quarter and not tie
yourself to a specific date yet. And the third thing you
can do is cut features. I mean, it's lunch. Maybe you don't need
everything you think you need. You could always
do an update right after launch to
pick up that stuff. Be smart and strategic. Don't be afraid to cut
things and realize that your players probably won't miss anything that you leave out. If they do miss it, they'll let you know and you
can put in your next update. So here's your homework, research what's needed
to release a game on any stores you
plan to support. Find out if there's a cost, if there's approval
needed before uploading and what assets and
text you need to provide. Write down a burnout
prevention plan. How will you recognize
the science? What will you do to
rest your mind and body when burnout
begins to appear? Make a list of your currently
completed features. Make another one of all
your unfinished features. If you ship the game right now, would you be happy with it? What would your
player's miss the most? Try out different
combos of adding in the uncompleted features
and ask yourself, which combo gives the players
the most value at launch, which ones could I deliver
later and maybe even make that an exciting
update in the future?
13. Release: Fear of Judgment: Now when you release
your game right before, during, right after, you may be feeling a wave
of negative emotions. You may be feeling insecure,
disappointed, embarrassed. When you wanted to feel
positive emotions, you wanted to feel
excited and proud. Don't be surprised
if there's a bit of this wave of dread that
starts to come at you. Maybe you didn't get the
reaction that you hoped for. You got some negative
complaints or reviews or just crickets,
nothing at all. Well, if that happens, let's talk about how it may make you feel and what you can do to be more comfortable
with being judged. When you're releasing a
piece of entertainment, you're indirectly competing with anything else that
a player could do. From the entire
backlog of Netflix to every other game that's been released for the
devices that they have. So no matter how
good your game is, there are elements of luck,
timing, and momentum. There are completely
out of your control. There could be a political event that happens the week
of your release. There could be a totally
different game that comes out that's
similar in concept. You don't know. So the most important
thing to remember is that even with your best efforts
and your best intentions, you can't completely
control your game rallies. And some things may
happen that you hoped wouldn't happen or
that you didn't expect. And it's really about
how you adapt from that to get the
result that you want. Embrace the fact
that you need to be flexible and switch tactics. If something happens
that you didn't expect, if you didn't have
a large following already when you
launched your game, you shouldn't be too
worked up or sad if there wasn't a big
splash when it came out. That's expected. And that's why we
talked a lot about making your goals focused
on something else, like making a game about an
idea you think should exist, or building up a skill set that you really
wanted to learn. I know I just keep saying
this over and over, but it's really true. When you focus on as your goal is the most
important thing. And if it happens, have become popular
and a bunch of people download it because they watch
a YouTube video about it. That's great, but don't
feel bad if you had a small audience and you got a small response
that's to be expected. And it's all part
of your journey, no matter what else you plan to do with your game dev career, having a group of people
that care about you and care about your games
is only going to help. However you choose to
build a community is fine. You could be going
to local events. You could be starting
a YouTube series, social media and community and marketing
tactics are always evolving, but that's part of the overall
concept of being flexible. If you're excited about
this and interested in it, There's lots of places
where you can be learning about what's
new and upcoming. There's a website I really like called how to market a game.com, where they go through and break down people's steam pages. They share data
from other people and how many wishlist they're getting and tactics to make you stand out
and the Steam store. And most importantly, it's
about picking what you wanna do if you'd like certain types of social media
more than others, invest heavier on
those because you're having fun making
content for them. For me, I found that I really enjoyed Twitch streaming
and that that was a place where I could
hang out with people that liked what I was doing
and liked my content. And so that was a community
that really worked for me, but it may not work for you. They may be something
else entirely that you wanna do to build
your community. The important thing
is that there is a place somehow where people can get the latest news about what you're doing and
they can follow you. Now, let's talk about
having a tough skin. Because I feel like almost
every video I've watched about putting content out
there that you've created, said you need to
develop a tough skin. And personally, I'm
uncomfortable with that idea. Maybe I'm just uncomfortable with the way the world works, but I don't like the thought
that if you want to create, if you have a passion for making art and making creations, you suddenly have to be amazing at letting people
yell at you all the time. That just doesn't
make sense to me, especially because
people who are creative are usually really receptive to learning and are interested in
improving their skills. So they're more
likely to listen to negative feedback and
take it to heart. And if that negative feedback
comes from a dark place, if it's not constructive, then it's very uncomfortable. You may be stifling that little flame inside of you that wants to
do creative work. Because you can't
stop thinking about the hurtful words that
someone said to you. It's not really clear
to me when people say, develop a tough skin, what tactic you're supposed
to do to make that happen? I think what they
usually mean is, the more you do something, the more used to it you are. So from that point of view, let's say that the
more times that you make things and you hear
people say things to you, the less it's going to
have that personal staying and the more objective
you can be about it. But I also don't
want you to feel bad if you're not checking
every single day. We don't have to obsessively check our comments for things. If you really must do it, then check once a
week or once a month, you don't have to keep
going back every day and feeling bad because
there's no new comments. Like just check every
once in a while. I think this is really
important for me because I'm in a
different mindset. If I'm looking at content, getting feedback from it
than I am if I'm creating, I'm creating my next idea. I really can't be focusing on what people said
in the last idea. Were comments are useful
to me even if they're negative comments or if there's something that
I want to improve. So for example, we have a game series code romantic
that we're working on. The first scheme is out. And when I work on the
writing for the second game, I do like to see what was the feedback
from the first game. How could I make the
second game have better writing for some people? However, if you are
having trouble reading negative comments
and you find them stressful, it's totally normal. And there may be a couple of ways to change your
perspective about it. They'll make them
more palatable. The first is based on advice
that my mom used to give me. She would say, if somebody
insults you and it's true, Why are you mad? And something about that? I find really amusing. Yeah, I guess if it's true that the game was short
and someone says, Hey, I didn't like
that, it was short. Alright, that's what she made. If you had cheesy jokes because you like cheesy jokes
but somebody else doesn't. It's okay. It wasn't for them. So sometimes I think about that. I think if there's
a truthful part of the negative feedback, a, That's what they think. It's not wrong. It's fine, right? And sometimes negative
reviews are good because somebody else
may not buy your game and get mad that it
wasn't what they expected if they read the
negative review and they think, oh, I don't like cheesy jokes. They just won't buy your game. It's good to cater to the audience you're
trying to please, rather than trying to assume you're going to
please everybody. The second thing you could do, as frankly, just find
the humor in it. Sometimes when I read one-star reviews or to serve
views on something we made, it's not even really about us, it's about something
totally different. You can make it sort of like
a steaming maybe take one of your one-star reviews
and printed out and probably put on the wall
and find the fun in it. Find like yes, I am the
cheesy joke person. Yes, we are the
game that dared to have an octopus and
that's wearing a hat. I don't know what people are going to say about your game. But it could be something
that you take as a moment of pride and that could
be something that develops that
so-called tough skin. So to wrap up just
a couple of things. First is the meeting
of your expectations. Even if you've got
no negative reviews, even if people said they
really liked your game, you may still be feeling really bad because you didn't
have to cut some things. You didn't want to cut. At the beginning of the game, you thought it would be this
thing that would change the game industry and it
didn't turn out that way. So I just wanted to
let you know that actually it was great
that you tried that. Because if we don't
reach for those stars, if we don't try to be the best that we can be when
we're making a project, we definitely won't reach them. You have to know that in most cases you won't get the
best outcome that you want. And you have to try it anyway. So don't feel bad that you
didn't meet your expectations because it made your game better and it will make
your next game better. This is one of the
hardest things you have to prepare for
the worst outcome. But you also have to hope, because the hope is
what makes us work really hard to be the best
game creators we can be. And then finally, I want
to talk about courage. Finishing your game
was your goal and you will accomplish
that. That's huge. I don't know if this
is your first game or your fifth game or
your 50th game. But every time you finish it, you're going further
down the path of your own creative process. You're becoming a better creator and you need to celebrate that because that's what gives you the excitement encouraged
to your next project. So don't be afraid to
celebrate at this point, no matter what happened. Have a launch party. Even if the launch party is just like you and your family having a picnic with your dog or
something, I don't know. Get together or
like a video call with your friends or the people who made
the game with you, celebrate the fact
that you freakin made this game that
you wanted to make, you did hit, Okay. Don't let anyone
take that from you. You accomplish your goal and I'm so proud of you.
Here's your homework. Make a list of worst-case
scenarios for your launch, and what will you do if
those things happen? Read bad reviews of your
favorite game or movie, build up an
understanding that not everything has to
be for everyone. Print out words of encouragement on a note to keep on your desk. It could be an
inspirational quote or a positive comment from
one of your players.
14. Maintain: The Aftermath of Launch: What's left after
you made your game? Well, in some cases you're
going to want to maintain it. And that's what this
video is about. If it's a game jam, if it's just a one-off
idea or experiment, you don't have to maintain it, especially if you're making
more and more projects, that's way too much work. So you need to
prioritize which are time will be going forward. But if it is a game that has a player base or you
want to make updates, or maybe this is your dream game and you're
just going to keep making more and more content for it for as long as you can. You need to maintaining plan. If you decide to
update your game, you should figure out what
is the schedule of updating? Is it something where every few months you hope to release a new update and you'll
just keep going down your task list until it's empty, which it probably
will never fee. Or maybe you want to just plan something
like every year on the anniversary of launch are
gonna do something special. And just like you
did for launch, you'll want to
treat these updates as their own mini launches. It's also good for
pretty much any game that you make to expect
to do a little update right after launch
in case there's some really terrible bug that's making it hard for
people to play. It's also an act of good faith for people to know that you are listening and you do plan to do some work on
it in the future. So sometimes you
can take a few of those tasks that you
didn't quite get done for launch and make them
a little update and release them maybe in a couple
of weeks or in a month. Now one thing I found really challenging is the more
games we've released, the less time I had to
maintain any of them because I was always looking at the next game I was making. Usually give yourself a regular schedule where you're
balancing that, maintain work with
your other work. You can do this with
your time blocks like maybe a couple hours a week you spend maintaining your
other projects as needed. Or maybe every few months, you take one week and
you just really focus on updating one of
your games that has a lot of things he
wanted to improve. If you haven't already, you need a way for players
to contact you. Make sure that you have
an email address as easy to find for
support questions, have a discord or a Facebook
page or some kind of social media where
people can make topics and talk to you. Often in stores with reviews, you can also leave
comments and reviews. So you can let someone
know if you're planning to fix their issue. Least let them know
that they were heard. Now, as we've talked
about in the last video, you don't have to
check every day. But since you're coming
into this maintaining flow, this should be part of
your natural process when you're thinking
about updating the game. But if you are moving onto your next game project,
that's awesome. To take a mini break though, take some time away
from the computer. You know, all those
resting and relaxing things we talked about
like reading books, going out to a park, going on a mini vacation, and let yourself
get re-inspired. This is a great
opportunity for you to rejuvenate your
mind and body and be at the best
physical condition you can be at the start
your next project. You'll probably be really inspired and motivated
when you start, when you're ready,
returned to your idea home and pick the next idea
that you're going to do. You can start the
process all over again. You'll be a lot further because you've
learned new skills. You've tried some things that worked and some
things that didn't, and it's time to
continue your journey. Here's your homework. Make a community
engagement plan, set yourself a regular
reminder to check in on what people are
saying about your game. Set up a space for
people to contact you. This could be a discord, a Facebook page or another
social media account. Make a maintaining task list and a schedule for when
you'll update your game. Start to think about
your next project. Will it be a totally
different game or a game that builds upon the skills
you learned with this one. Or maybe it's an update
or a sequel to this game. Whatever you choose,
don't forget about your goals exercise. Make sure you're still working towards that bigger agenda.
15. Final Thoughts: This concludes the course on
finishing your indie game, no matter where you are
in your game dev journey. I hope this course has
helped you and I'm really excited to see
what you came up with. Making games is one of my favorite things
to do and it was so much fun talking about it with you for this whole course. I'd love to see what
you're working on. So don't be shy about posting your projects or any of
your homework assignments. I are so many more
things I'd like to teach you and helps me to know
what you want to hear most. Please write into discussions. Let me know what
you want to hear. If you want to keep
in touch with me, you can join my Discord or follow me on Twitch,
Twitter or Patria. Thanks so much for
taking this course. And I can't wait to see
you in the next one.