1. No, your game idea does not suck. Whether something sucks or not is entirely subjective. It does not matter how other people think of the premise of your game. If you really like your game idea, make it anyways. I really dislike it when people actively create an environment where you feel like everything you do is wrong, as it causes people to become discouraged and then they leave. Create a positive environment, especially for beginners and add helpful tips as you go. Saying something like "This is nice, but it would be much better if you did this" is such a better motivator than "this is trash", and I'm tired of seeing so many people quit their passion as a whole because the world won't grow the hell up. 2. If you really hate programming, it's perfectly fine to skip it and use visual programming, which involves no technical code. Five Nights and Freddy's and Baba is you did this very well. Most game developers like programming, but not everyone likes it. Whether the syntax messes with your eyes, or you simply don't enjoy the process, visual programming can act just as well, even if other programmers don't like it. Points 3 through 6 are very good. Here are a couple other tips Don't re-invent the wheel. I see many people try to create video games using a regular programming language, if you're making a lot of the assets on your own, then please don't do this unless you have a huge team. It will take an eternity for very little output. The tools are there for us to use. Have a friend to reflect your game with. This sounds weird, but when making larger projects, having someone to talk with about your game and the development process can be very beneficial. They can provide excellent motivation and input that can change your game for the better. When you get bored of making your game, then don't work on it. There is this trap people fall into called 'the last 90%'. For bigger games, it's a long list of unplanned issues, most of which involve UI, localization, Translation, and *shudder* fixing bugs. But for smaller games, it's the last ounce of motivation to patch and polish the overall details. Come back later when you regain your passion and polish it, adding your new great ideas to your old great ideas.

*LESSON 7: Archive all your games, no matter how bad they're. You can later use them to check how far you've come*

I remember when I escaped tutorial hell. I wanted to make an inventory system, and watched like five different tutorials from different channels that I followed but I didn't like the way any of them did it, so I ended up making a super complete one from scratch. You could drag items around with the mouse, or use the keyboard, it also had a right click context menu that would show different options depending on the type of item, an even a sort button. It was an amazing feeling and I learned a lot.

4 year gamestudy degree later: Lesson 1: Yes, most likely, atleast in a way that you arent fully able to make the game that way you want if you don't have any experience. Understand that your 1st ever game idea will most likely be trash and TAKE THE FEEDBACK Lesson 2: Yep there is no escape, visual might be the way to go if actual coding is bit much but yes, there is no escaping it. Lesson 3: Yea have some kind of idea on what you want to make. have something you want to create before starting. Lesson 3 subs helps: -3 beta games is a good start, the 3rd can start to be a bit bigger project but trust me you will want to re-do EVERYTING about it when you grow more skilled. Recomend making at least 3 small projects and even perhaps let them go when you realize that you have learned so much that you want to redo every part of it. at this stage it's 100% fine to do so. Just don't make it a habbit to leave games half finished. This only counts for the 3 VERY first games you make. Othervise you will never learn to make actual game from start to finish and always start redoing it. -Watch tutorials man, if you don't have school just for the love of god watch them- Lesson 4: This is important. When you watch tutorials like "How to create snake AI" follow the tutorial but make a worm instead, so you will have to adapt your skills from the tutorial into something else and actually get use from it. Watching tutorial and just doing copy-paste will not lead into good results. Another example: Tutorial is "how to make cool door" then you make a trapdoor with the tutorial. kinda similiar but makes you understand the tutorial stuff much better. Lesson 5: Learning more stuff is ALLWAYS a good idea. Makes you better overall. Lesson 6: Make games that are fun for you. Don't make them for cash at start. The miracle game you make is the one that you really made for your self/friends and not for money. (read the story of FinalFantasy and Undertale) Undertale being the "beta test game" for Deltarune. good teachings. Just make games and move on when you are ready, don't stick with one game too long but also dont give up too easy. Make a big game if you want, but only then when you know you can do it.

I would add a Lesson 7: Game development is a multidisciplinary job. Game projects have programmers, artits, musicians, game designers writers, and more. Work around your resoucers if you have a very small team or you are a solo developer. For solo devs think about how much work will take to make a game all by yourself and how many skills you will have to master and how long it will take before even atempting it, so keep it as manangeable as possible.

"Sometimes you have to make The Witcher 1 and 2 before you can make The Witcher 3" - Tim Rodgers

yep i'm dumb because all i got here was opinions

I really dislike videos that clickbait you by insulting or threatening you, that feels like such a desperate move. But what can I say, the content surprised me. Great video, great lessons and a lot of conclusions that I came to as well in my ~2 years of hobby game dev. Lovely content man!

Ok let's see where I'm at... Lesson 1: Game idea prolly suck - Already aware it sucks cuz it's bland as hell (RPG story type sorta game, where the bugs I'm too lazy to fix were now features) Lesson 2: Cannot escape Programming - Currently making a game from scratch no Game Engine used (Cries in Java) Lesson 3: Go with a Plan - Made plans but barely keeps up on schedule, sometimes other plans aren't doable because it's above my skill level. Lesson 4: Avoid Tutorial Hell - I have one source or reference and the rest is being on my own Lesson 5: Explore new territory - With AI rising up, I managed to implement it into my game Lesson 6: Focus on process not on reward - Okay, I'm fine with this cuz I have no idea how to earn money so thought developing my first game is just a nice past time. Well I'll be fine I guess.

Lesson 7: Avoid game engine hell Most of the starters will think about what’s the best game engine and programming language they should use, It’s fine if you try some, But some people like me has been in what i call (Game engine hell), I was never actually making any progress but instead i was wasting my time trying every game engine that exists and overthink about how the performance of the game will be in every engine, Nothing is perfect so pick up what’s very popular and try it.

I love that the whole thing is very honest, and it actually puts me at ease a bit more about this. Highly appreciated that you made this.

I'm not even directly a game developer - I'm a 3D Artist in a games development pipeline, and everything in this video still correlates. I've been at this career for ages now. It took me probably 20,000 working hours before I really felt confident that I could "make just about any 3D model imaginable" from my amassed skillset - which was my big, lofty goal. And yet, I still watch an average of probably one tutorial every day - they just tend to be short and narrowly focused. I still get excited about and love the process of creating every single 3D model - I can think of few things better than being in the creative "flow" zone that programmers often speak of. If you're truly compelled to be a games developer, a games artist, or other creative professional, I don't think there's any force that can hold you back. Just expect to put in the work and, as Fredyy said, "Focus on the craft, not the reward".

Challenger route: Become a masochist and master C++, write your own engine and game from scratch. Hell route: Learn assembly and make game from scratch (rollercoaster tycoon style) 💀

Lesson 4 is such a huge lesson. Once you escape tutorial hell and start working on your own project you realize you havent learned anything watching all those long tutorials.

I’d like my 5 minutes back

Godoted with the sauce

Lesson #7: You cant escape art. I cant draw.

I feel like I needed this, I only started learning a few weeks ago and got a bit overwhelmed. Going to take it back to basics and simplify a plan. Thanks!

How to mostly git gud at game programming: Step 1: Actually embrace math. Learn the parts you are not familar with. Step 2: If step 1 fails, give up. Otherwise, Step 3: You are now gud.

Honestly, this video is an absolute gem, I've been making video games for the past.. 8 years or so, just sparingly for the fun of it, I'm the person who likes to jump straight into the problem and figure things as I go, during the process I've seen people stuck on tutorial hell and I've always gave the same advice: Make stuff on your own, just do something, anything, if you're afraid of being judged, don't show it, it's between you and your hard disk Another thing I've always said to people is: Don't sweat it, don't pressure yourself on making something perfect from the first time, just make something, you can always refine it and make it better Finally: Make Sure to FINISH the projects, it's very important unless you created the project for a specific feature / idea to prototype, aside of that, finish your project before moving on

At first, I thought this was going to be satire (mainly because of the title), but it wasn't. I appreciate your hard work and this has helped me throughout my game developer journey. Thank you!

If you do what you love and believe in - never give up! Because you only have one life, one chance, and a lot to learn, we all know it will be difficult. But "difficult" makes us stronger, so even if you're broken, get up, give yourself some rest, give yourself some love, and keep going. And maybe not tomorrow, but maybe soon you will break down the walls and make the world a little better!

i prefer using low level libraries, and i want to program game engine myself (its going pretty well recently) everyone says its a bad idea, but so far i learned so much more compared to the time i was using an pre-built engine not sure if i'll ever actually finish a game with my engine... also, real! 🥶🥶🥶👽

this video is so well put together, I was really suprised seeing that it doesn't have more views

0:22 jokes on you, I love programming

I learned a ridiculous amount when I started making my own systems that are usable in more than just one project. In GameMake: Studio, I wanted to make an RTS. The built-in A* pathfinding wouldn't remotely cut it for my goal, so I made my own pathfinding solution that solves for All-Source All-Destinations, adjusting the prebaked pathing when buildings are placed, and implementing steering behaviors where units will follow their path, but also avoid running into each other and move as coherent groups. On top of this I made my own 2.5D shadow system and 2.5D sprite system from scratch to give it more visual appeal. Hey, it's in development hell and I haven't touched it in almost 2 years cause I had to finish university, but I still learned some things! Get out of your comfort zone, that's my input. You learn insane amounts when you try to make something you think is out of reach. It probably is not as out of reach as you think.

The funny thing is i actually escaped tutorial hell in the matter of 2 days. It happened because I felt like tutorial code was very messy and was gonna get me into bad habits for making larger games, I’m sure it would be fine for those who care about speed for game jams or prototyping but I wanted to learn how to do things properly right off the bat. There’s also the problem of how I didn’t want to learn how to make an 8 way directional movment controller, I wanted to learn how to process inputs, I already knew right off the bat that I should be learning the principals and foundational parts of programming first so i spent a month researching programming basics and then another month learning my way around a game engine. Unfortunately though I had to take a long break afterwards for life stuff and I ended up forgetting a lot of the programming stuff like what the heck an Enum is but at least now I know it exists I guess. I kinda cycle what I do from programming to art back to programming as I thought Instead of making no progress when I get burnt out, I could just practice and entirely different skill instead. Currently im trying to make my way around tilesets as i wasn’t really feeling programming i decided why not learn to make a simple tileset instead, beats looking at simple shapes all day and im not a fan of using other people’s assets as recommended as it is for the learning process. Although with me being a more logical person who enjoys the programming side of things a lot more, I find art pretty hard, I’m determined though, I don’t want to be a god tier artist but I do aim to reach something like Hyper Light Drifter’s level of beauty, wouldn’t push myself further than that as a solo developer, like yeah it would be awesome to be able to have art as good as Hollow Knight or Eastward but it just isn’t that realistic for me and the assets would add a lot of time to development. Not like I’m in any rush though, I chose to do game development because of my love for problem solving but also my admiration for gardeners as dumb as that sounds, i always loved the idea of someone that would put a little love into their garden and plants every single day for very minor growth and after years of hard work, the garden grows into something lush a beautiful, i admire that kind of long term commitment but i hate bugs so i decided not become a gardener but something i would consider to be similar and also match my other interests of gaming and problem-solving

My man decided to speak the best language ever created : *F A C T S*

Nice video, everything said does not only apply to game programming but in overall programming. 👌

I never understood why many programmers dislike visual scripting so much? It's simply another form of logic that others are more adapt to pick-up. Game Creator for Unity is stellar, Blueprints are incredible, both allow artists to join the fun, why is this frowned upon? Sure some specific stuff will need deep programming help, but you can always outsource that if you really had to.

Brilliant video. Very motivating. Thanks dude! 👏 Could you make one for the seemingly thousands of people who don't know whether they should bother learning programming anymore, now that AI can (apparently) do it all faster and better?

One of the biggest mistakes I made in my first game was not organizing assets in the editor. Keep your project clean and title all assets properly it will help in the long run!

Yeah, I agree with the stuff in this video. I will definitely take notes from this when i start to do game development.

I've been a full-time tech artist for the last 5 years or so. I agree with all of the points in this video. I was lucky enough that I started on our in-house engine. It was rough to get into, but my understanding of the matter had increased greatly because of that. It is much easier for me to produce quality content if I understand all the ins and outs of a game engine.

I coded a simple 3D game engine myself using C++ and OpenGL, it taught me a lot about computer graphics, systems and how games work at a deeper level.

0:11 I wasn't thinking of GTA 6

Lesson 7: Always approach your games with the most basic start. Every game has the bare necessities it needs to be classified as a game. If you head in with big plans for your game at the get go you're going to get burned out fast. Focus first on what your game needs to be functional. For example, Super Mario is about getting to the end of the level, so if you're making a game like that make sure you can get to the end of a level first. Overworld, obstacles, enemies, pickups and all that comes later, but if you don't fix the core, barebones necessity your game needs to even be a functional game, you're going to get overwhelmed. So go through each feature of your game in tiny bite sizes, especially if you're a solo dev. This way you can keep making progress and will be a big boost to your own confidence especially at the start

Thank you! I have done scratch for about a year and am really good at it, but ive realizes the limitations of it so i tried out unreal engine... And i sucked at it so i seitched to unity, and i sucked at it, so i switched to godot... And you guessed it, i sucked at it, but now this video has gotten me back into game development and i thank you for that! Ill be doing more unity and keep on particing, once again thank you for the tips

1:32 Okay I won’t let my eagle control me 🦅 Jokes aside nice video bro, the tutorial hell is real

LESSON 4: Is one that I notice and its rly important to understand. I used to implement tutorials in my project and it starts to being mess. Use tutorials only for education purposes, dont even try to copy and paste tutorial into your project. Just understand them and use knowledge later.

As a game developer, I have to say: "It's true, all of it!". In fact I was thinking about making a very similar video, but now I don't have to, you basically word for word expressed everything I wanted to say.

Lesson 1: Your idea doesn't suck! Balance your ambitions, scope and time. If you're looking to make a good game, but you are impatient or procrastinate a lot or you don't have a lot of time, then make a short game with stylistic graphics. If you have enough time, you can try making something ambitious, but you should always try scaling down your ideas, if something you make gets too big, start over with a new idea and make sure that you are capable of executing it without giving up on it, keep the original idea for when you can complete it. Lesson 2: Pretty self explanatory, if you are a newb, you must know this, you cannot escape programming. I have known many newbs in my lifetime that try to escape programming by using visual scripting or using gamemaker code block type stuff, it's just pain, better to learn programming than to be forever scared of it. Lesson 3: Pretty self explanatory, you need an idea and a plan. Lesson 4: Read the documentation, watching tutorials for certain things like creating a base for your FPS controller or a base for a 2D controller is completely fine, but if you want to make something specific then you should always read the documentation to get the answers you need. Lesson 5: You don't have to do this L L L L Godot > ALL only do this if the project you are making requires something specific, like a certain platform. Godot runs on Windows, Linux, Mac so why use Unity or Unreal. Only use Unreal if you want to make super realistic games. If you're making a game for the Nintendo 3DS or something then use devKitPro and learn C or C++ etc. You won't be able to use Godot or Unity or Unreal on Nintendo 3DS or Nintendo 64, although you can use Godot 2 on 3DS but I wouldn't if I were you.

This video really helped out, i've been wanting to make games but didnt really wanted to code at that time, so i used scratch, but after a while i got bored of it so i decided to try Unity and it was sort of complex for me and i had no experience in C++ or Javascript, so i tried other game engines and i choose Game maker since the interface was good for me and i got sort of used to it, i tried without a tutorial first but failed miserably so i choose a tutorial and followed along and made a first game :D i hope i can get better and make progress on my own and work my way up, thanks for the context! Keep up the good work!!!

Being in tutorial hell sucks, but when you escape it, it's the most amazing feeling 😌👌

I like that the first point is to learn by doing. I don't make games but I do program and I honestly feel the best way to learn a new language or tool is to just build something with it and if you get stuck, research how to the thing your trying to do, do it and move on. I find the problems you struggle with the most on are the ones that end up teaching you the most. I think another thing to add is don't worry if your approach is not the best. It's better to have a badly coded, working application than trying to do everything perfectly and then giving up because it gets to hard and then having nothing

This was definitely something I needed to hear. Congrats to you sir for being so inspirational

Oh Man, That first lesson was the best ngl

People flocking here after Unity announce their stupid plan incoming in 3... 2... 1....

I like to try to make games using web techlogies like HTML, CSS and JS. There is a very good library called Phaser that helps with it, I have even deployed a game to a server and it is still there running.

How many multi-million dollar budget games have you worked on? I like to know how qualified someone is to talk about development. By the way, real developers do not use 3rd party "engines".

Marking this video not as a beginning of my journey, but more of a checkpoint. You told me many things i used to believe on, but had to be remindned. thank you.

0:32 yes we can escape programming !

3:13 as an aspiring Unreal...fiddler, I can confirm that documentation is very valuable. Be grateful for it.

This was a really nice video! I've personally already gotten these tips, and I can confirm they're very helpful. However, I don't much like how the title and thumbnail introduce the video. They make it seem much more negative than it really is :)

Tutorial hell, i always wanted to learn programming and would go on tutorials as I wouldn’t know ANYTHING except printing hello world and that, but I didn’t know how to use them and combine them, like in engine, so after 1st year in highschool where we are learning programming, i understood how it functions (on most basic level) and i was able to pick up godot and DO STUFF, went trough couple tutorials and after that always tried to figure it out with my own logic and knowledge, so i’d end up not knowing small thing and looking it up on browser seeing and understand code not copying it At the end i felt so PROUD of myself, game wasn’t even finished or good or anything but being able to actually make a game in my own made me sooo happy cuz i always wanted to do that

As a game design student I’m glad this video gives out a plan. Like I’ve made functional concepts before in engines but there’s a sense of stagnation once the assignment is done. This gives me something to aim for in relation to my own skills.

Whoa. This is one of the greatest videos of all time... No, seriously! So much of it applies to other crafts, yet it's still specific to game development. Simply brilliant!

I'm just an artist striving to create a hopefully cool experience. I'm not a programmer, although I've dabbled in coding here and there since UDK (Unreal Development Kit). I've noticed that it's much easier for me to purchase a ready-made project from the marketplace and use it as a foundation, modifying it with Blueprints as needed. I'm focusing on what I can excel at due to my skills, such as storytelling, level design, pacing, and world-building (because I make a living as an artist). If people enjoy the result and I can generate sufficient income, I can consider hiring a programmer for the next installment. The reality is: I want to make a game, not to become a programmer. That's the plan, plain and simple. Also, I kept the first game ridiculously small, as a vertical slice (I made two stupid little projects: an infinite running game with 3 characters, each one with a special skill. The other one is an adventure stealth game. And a ton of super little projects since UDK, with "savage squares" shooting things. Then I bought the Third Person Shooter Kit on Unreal marketplace and I'm finishing something decent now. The previous projects gave me a good idea of what I can do). Yeah! Agreed, mainly with 3. Tutorials are only good when you're in the learning stage, or if you're implementing something really new and don't know the logic of the thing.

I really enjoyed this video. I'm learning via a udemy course on the basics of coding simplistic games. When I am finished with the course, I already have ideas for better simplistic game ideas after the four type of games afterwards once I'm finished with the udemy class. I even enjoyed making this asteroid clone for our first lesson learning about classes with python. I already have plans on going back to that and eventually making it a full fledge game for my first one in the future.

I was stuck in tutorial hell one time, but shortly' very shortly after, I became able to get ideas for mechanics and get/generates ideas to code them. And programming is my fav part in gamedev, It is the whole reason I started.

"Your idea is bad " - feels like a stereotypical oversimplification that does not help anyone. There are no bad ideas. Just the inability of the developer to put them into practice, or to incorporate the public feedback (that's where we agree). But this is how YT videos work, you need an edgy hook right at the start, to prevent your audience from switching to something else. The rest of the advices are quite generic, nothing ground breaking.

1. No my game ideas don’t suck. But yours probably do. 2. I do much more than one job/career and no longer have time to learn all this shit. 3. Saying I need to learn to code to over-see a design is like saying you need to build your own unity to use unity, bet you never would.

I have bad performance on mobile idk what to do i already do batching and everything but it still runs at 17 fps do you know where i can found a full unity Projects to learn how they optimised?

hey thanks a lot this really help make the the process less stressful for me, i never really thought of it this way, i always got stuck in the watch tutorial then don't know what to do after phase lol so i really appreciate this thanks for the vid :)

Splendid explanation

I've worked in AAA studios for a bit now, and this 5 minutes video should be shown to every single person who's ever wanted to make a game. Straight up truth and facts.

thank you for sharing this video. i really needed something like this because i get easily overwhelmed and stressed when even looking at tutorials. i am trying to get more courage in exploring game engines (currently trying to learn Godot and even though people say it is beginner friendly, it overwhelms me and i feel like an idiot for even saying it). do you have a discord for this channel? it would be awesome if you did. keep up the good work!

You put into words why I am struggling to work on my games. I really don't want them to fail. But after this video, maybe it's good to let a few fail. Thanks for the perspective.

I thought you were going to say something important

What a pedantic title.

Yup all the advice is correct here. Been making games for seven years now and id say its all spot on. Well done Will watch more of your stuff

Lesson 1 is extremely important to keep in your mind always when developing. During a entrepreneur course the coaches and mentors talked about it all the time. It was even more important there than the skill of programming because the product in this case the game is the thing that's supposed to feed you. If you make a bad game and nobody buys it or plays it you will not get money from it and that will kill the whole studio. There we called lesson one "Kill your babies" because people get really attached to their games and they are like babies to them. We had a small indie company and in fact we had to kill our baby and close the whole damn thing

Faz um canal em portugues pra gente também po kkkkk

Well, now unity is dead soooo....

What would you recommend for learning the terminology of c#

The hollow knight mantis lord song in the background 0:43 💀

you're game idea probably sucks too

Chill with that title 💀

I bought a few courses on Udemy and I actively force myself to always try to go a few minutes ahead. For example when the tutor goes into explaining smth, I first try to figure it out on my own. I think that's the best practice for me and really helped me learn.

I have no knowledge or whatever related to coding and is planning on developing a simple 2D game. Where do you think should I start?

Can you pursue computer science even though the strand i choose is ict and is it okay even if im not good in math

That's some good advice. I'll just give up.

Lesson 4: Yeah I learned this one the hard way... When I realized I had become dependent on tutorials, and did not know what to do without them I kind of quit for a while. Got sort of back in because a new game idea started to brood in me which got me excited again to try it again.

I am learning to code from tutorials right now but some stuff doesn't make sense, so I experiment with things and my code based off theirs works just as well, never be afraid to experiment

Thank you so much. I'll follow all your lessons!

This is a great video. The best piece of information was without a doubt “Allow yourself to do hard things, just not in the hardest possible way” Perfect advice for game dev or pretty much anywhere in life.

the thing is, how do i learn how to code in certain programs like godot engine (i need to learn how to code in there because i want to make mods for a game called your only move is hustle and then maybe make my own game)

I just escaped tutorial hell few days ago i wanted to follow a tutorial for a shooter game but the internet stopped for days so i tried making the whole game by my own and i succed in that!

Thanks, Freddy! Solid advice!

My issue is that I don’t want to work on games alone as I’m learning how to make games but never have, it hard to make projects I don’t care about to eventually get to making my dream game! But at least I’ll have whole control and say over my game! I won’t have to convince anyone, teach anymore, or argue with anyone besides myself! Y’all understand right? Don’t u guys want full control and say over your game but can’t cause it was made with a team rather than yourself?

bro broke my ego in 0.01^-19 seconds

This is the best video I've seen on the topic. Blunt, accurate, but not condescending. Excellent job. I'm taking a slightly different approach. I don't plan to use any of the available engines, for various reasons. That means I have to learn everything. But instead of diving right in and trying to figure out how to draw bewbs with Vulkan I'm teaching myself the stuff that matters behind the scenes. For example, how to efficiently deal with random numbers, how to get a program to work with a config file or output a log, or how to write complicated equations into code. These are all things that are essential for a game. But they're all small enough that you can tackle them fairly easily. Learning how to output logs can be done with pretty much any trivial program you write. You can even write a program that does nothing but output logs; have it write the time at random intervals with a random number or the results of some calculation. Because these things are so small and simple, they help build confidence. But they still build skills you will need, so they give a sense of progress as well.

So I had multiple attempts at getting into unity, it never really worked. I followed tutorials until I got bored and tried developing my own ideas and of course struggled and gave up, it got to the point of me doing this so many times until I had enough knowledge to make a very basic game myself. From there I have made many prototypes of ideas I've had, and I never really noticed that I was independent until I realized I programmed an astar algorithm on c# all by myself (Its not great but it could navigate around walls). Before this I was programming python turtle games every lunchtime at school with friends which boosted my programming knowledge significantly, also I'm grateful that I also was learning blender so I could make pretty decent models and animations for my games. I still haven't completed any games yet and I still have a lot to learn but I can't wait to find out what projects I'll be working on in the future. Oh yeah, I also need to fix my problem of being overly ambitious, but I guess its what motivates me when making my games.

i like how it tells you to give up

That was great! Very informative and helpful. Thank you very much!

I'm not even going to finish watching the video, I'm just going to give up here before I waste anymore of my time trying to learn coding when its just not working for me (what happened that led up to this point for me) -I want to learn how to code but I don't know where to start -I try looking at tutorials to help me find out where to start -all the tutorials require you to already have experience in coding -I eventually find this video -now it tells me something completely different compared to everything else on the entire internet and just makes me feel more confused about where the fuck I should start and that is why I give up

The first tip crushed me cause my game idea is nothing but dumb with story telling begin wild but I'm determened to make that game come true and this will be a good help out tip video so thanks!

As a person who never had any plans to make games, this video is very informative!

Thank you, this video pushed me further!

I am a game dev, and I completly approve what's being said in that video !