If You Can't Make Games After This Video, Give Up
Summary
TLDRThis video offers a candid guide to aspiring game developers, emphasizing the importance of letting go of initial ideas, understanding the necessity of programming, and planning before diving into game engines. It advises creating simple, diverse projects to learn the basics and warns against becoming dependent on tutorials. The speaker encourages exploring different engines to broaden skills and stresses the importance of focusing on the development process rather than immediate success, advocating for continuous learning and improvement.
Takeaways
- 🚫 Initial Game Ideas May Be Flawed: Let go of your first game idea quickly as it's likely not the best.
- 💻 Inevitability of Programming: Games are computer programs; understanding programming is crucial, even with visual tools.
- 📝 Plan Before Starting: Have a simple game idea in mind before opening a game engine to avoid feeling overwhelmed.
- 🎮 Start with Simple Projects: Create at least three simple, different games to learn the basics without aiming for perfection.
- 📚 Learn Through Difficulties: Embrace challenges and use tutorials for specific issues rather than relying on them entirely.
- 🔍 Avoid Tutorial Dependency: After initial learning, be cautious of tutorials that teach entire systems to prevent becoming overly dependent.
- 🛠️ Experiment with Different Engines: Learning multiple engines, like transitioning from Unity to Godot, broadens your skillset.
- 📚 Value Documentation: Understanding the concepts and history behind game development can significantly improve your skills.
- 🎯 Focus on the Process: Game development is a craft; focus on improving and learning rather than solely on the end product.
- 🚀 Embrace Failure: Accept that early games may not be financially successful but are valuable for learning and personal growth.
- 💡 Be a Fountain of Ideas: Continuously generate new game ideas and don't become too attached to a single concept.
Q & A
What is the first lesson the video suggests for aspiring game developers?
-The first lesson is to let go of your initial game idea quickly, as it likely isn't as good as you think it is, and to be open to learning and improving.
Why does the video emphasize that game development involves programming?
-The video emphasizes programming because games are computer programs, and understanding programming is essential to creating them, even if using visual programming languages.
What is the recommended approach when first opening a game engine according to the video?
-The recommended approach is to have a simple game idea in mind before opening a game engine, to avoid being overwhelmed by the options and information.
How many simple projects should beginners make to learn the basics of game development?
-Beginners should make at least three simple projects that are different from each other to learn the basics of game development.
What is the purpose of making the first three simple projects in game development?
-The purpose is to learn and understand the basics of game development without the pressure of releasing or showing the projects to others.
Why is it important for beginners to understand that their initial games will likely be bad?
-Understanding that initial games will be bad helps set realistic expectations, allowing developers to focus on learning from their mistakes and improving their skills.
What is 'tutorial hell' and how should beginners avoid it?
-'Tutorial hell' is becoming overly dependent on tutorials that teach entire game mechanics or types of games. Beginners should avoid it by watching specific tutorials that focus on particular components or nodes, not entire systems.
Why does the video suggest making a fourth game without relying on tutorials for the whole project?
-The fourth game is meant to be a more polished project that can be shown to others for feedback. It helps developers to apply their learning in a more independent way and to start creating their own systems.
What does the video suggest about learning different game engines like Unity and Godot?
-The video suggests that learning different game engines can help developers become more versatile and understand the overall concepts of game development better.
What is the importance of focusing on the process rather than the reward in game development?
-Focusing on the process helps developers to improve their craft, withstand failure, and eventually achieve success by making better games over time.
What advice does the video give about becoming attached to a single game idea?
-The video advises against becoming too attached to a single game idea, as it's important to be a 'fountain for good games' and to understand that failure is part of the learning process.
Outlines
🎮 Embracing Game Development Realities
The speaker candidly addresses the harsh truth that initial game ideas are often flawed and encourages letting go of grand visions to start learning. They emphasize the inevitability of programming in game development, suggesting that one should not shy away from it but embrace it as an integral part of the process. The first lesson is to have a simple game idea in mind before diving into a game engine to avoid feeling overwhelmed by the options and information.
Mindmap
Keywords
💡Game Development
💡Game Idea
💡Programming
💡Game Engine
💡Plan
💡Tutorial Hell
💡Feedback
💡Concepts
💡Craft
💡Dream Games
💡Overwhelm
Highlights
The importance of letting go of your initial game idea as it might not be as good as you think.
Games are computer programs, and understanding programming is essential for game development.
Embracing programming as a key part of game development rather than avoiding it.
Having a game plan before opening a game engine to avoid being overwhelmed.
Starting with simple game projects like a Mario or Pong clone to learn the basics.
The necessity of creating at least three different simple projects to gain experience.
Accepting that early games will likely be of poor quality and facing many difficulties.
Balancing self-learning with watching tutorials to avoid stress and learn effectively.
Avoiding 'tutorial hell' by not relying solely on comprehensive tutorials for entire game mechanics.
Recommendation to watch specific tutorials for understanding particular components or nodes.
Creating a fourth game to showcase and seek feedback without relying on full tutorials.
The value of learning multiple game engines to avoid dependency and enhance understanding.
The benefits of learning Godot after Unity to appreciate game development concepts more.
Focusing on the process of game development rather than the financial reward.
Understanding that the first game might not be a financial success but can be personally rewarding.
The importance of making good games consistently to be appreciated by others.
Encouragement to start making dream games despite the fear of failure.
Advice on not becoming too attached to a single game idea and being open to creating more.
The realization that you are ready to make your dream game, and the value of learning from failures.
Transcripts
I'm gonna teach you how to make your own
games after this video you will be a pro
the number one lesson is your game idea
probably sucks the faster you let go of
the GTA 6 in your mind the faster you
will learn this will probably sound
really harsh but no matter how good you
think your game idea is it's probably
bad and listen I'm not trashing on you
I'm just telling you how it is I'm not
gonna serve you lesson number
two is you cannot Escape programming
games are literally computer programs
you can use visual programming languages
but you cannot Escape programming itself
and for me programming is the best part
anyway so why would you run from it
lesson number three is always go in with
a plan never make the mistake of opening
a game engine and trying to learn it
without a goal you're just gonna be
overwhelmed by the amount of options and
information that you need to take in the
first time you open a game engine you
should already have a game idea in mind
something very simple like a Mario clone
or a pong clone before we move on to
lesson number four I want to give you a
few tips for your first games you need
to make at least three very simple
projects you're only supposed to learn
from them these are not things you're
going to release or show anybody just
learn they all have to be very different
from each other for example you can make
a pong clone and then a Super Mario
clone because they are really different
in gameplay terms as a third option you
could probably make a top-down shooter
or something you want to make here it's
important to understand that your games
are going to be really bad and that
you're gonna have a ton of difficulties
you can try to do things on your own but
if you feel too stressed watch tutorials
man don't let your Eagle control you
allow yourself to do hard things just
not in the hardest possible way you know
lesson number four avoid tutorial hell
please you shouldn't really worry about
this in the first three games that we
were talking about earlier because you
were just learning the very Basics but
after that it's time to be careful with
tutorials that teach you an entire thing
like an entire game type or an entire
game mechanic because you could become
dependent on those tutorials and never
really learn how to make your own
systems in your own types of games as I
said you don't have to do things in the
hardest possible way so I still
recommend you watch tutorials but very
specific tutorials like how a specific
component Works in unity or a node in
Godot this way you can still avoid the
stress of something that is Way Beyond
Your Capacity but still learn how to do
things your own way so to definitely
Escape tutorial hell I recommend you
make a fourth game this time you can
even show people and ask for feedback
but the most important thing is being
something new and that you don't watch
tutorials for the whole thing just for
specific things as I said lesson number
five is explore new territory always
when I was starting I spent months
learning unity and I would never try
anything else I was making progress but
I felt like I was too dependent on Unity
itself as a tool and so I decided to
learn in the dough it was very stressful
at first but once I understood the
engine and the differences between the
two I realized that I was way better
after this learning Godot made me value
more the overall concepts of game
development and programming Kudos
documentation even focuses a lot on the
history of game development and why
things are done and that helped me a ton
this experience made me a better game
developer all around lesson number six
is focus on the process I know this
sounds cliche but game development is a
craft and you have to focus on the craft
not on the reward for the craft I know
you want to do this for a living but
your first game is probably gonna flop
financially but it's not gonna flop in
your eyes if it's good and if you learn
something from it focusing on making
better games is the only way to
withstand failure and eventually achieve
success and I promise you if you make
good games they will be appreciated
after you follow all the steps in this
video you can probably start making your
dream games but don't allow yourself to
become too attached to a single game
idea remember you have to become a
fountain for good games only one is not
going to get you anywhere in the
beginning you're gonna feel like you are
not ready to make that one game that you
always wanted to make but you are it's
just that you don't want that game to
flop so that's why you'll never make it
if you flop with that one you can always
make a better one and then people will
appreciate your first one because of who
you are alright this is your journey go
ahead leave a like in this video if you
want more
Voir Plus de Vidéos Connexes
5.0 / 5 (0 votes)