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.
This is how you write a critique! Thanks, it bothered me for so long reading dumb comments that never added any value to the video... I respect your view and since making this video I changed a lot about how I present my ideas. I was trying to say something like "think about your game ideas realistically" and it came across the way it did, which is my fault, but not my intention... Anyway, I agree with all your tips! I might even include them in future videos if that's ok with you.
I'm glad you said this. I wasn't a fan of the entire 1st point being "Hey you should consider the fact that your idea is trash". It really rubbed me the wrong way, a good idea or a bad idea is entirely subjective, and if you start telling people that the idea they have churning in their head is trash then you might have single-handedly killed a great idea before it could ever manifest.
@@badbeardbill9956 It depends on what defines a bad idea. I'd say it's impossible to really create a bad idea. If you come up with an idea from the heart, it can't be a bad idea. A bad idea usually sprouts when your objective is something like money or success. If you have a good idea for a game, the creation of the game is the objective, you want your thoughts to escape your head. If your idea is coming from you, if it is something you truly care about, do not throw it away, it's a good idea, you might not have the best way to execute it, but work hard and you will get there. If you do not really truly care about the game you're making, if it doesn't come from the heart, from originality, then it is good to let it go.
Just because it's bad doesn't mean you did something wrong. I think everyone misunderstood him and take themselves way too serious if you really think he meant "Your game Sucks!!" no he basically saying your first game most likely isn't gonna be some great masterpiece, so don't let yourself down.
I made a battle-city like game back in 2013 and I have no idea now how I made it "crash" (does it only outside the debugger) on purpose and load a totally different level sequence.
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.
Ahaha, I had the same experience about 2 years ago on ue4, glad you did it. I remember when I started writing my inventory with no tutorials, I really learned a lot, I guess in those days I really learned how to code
Same thing happened with me for combat systems. I saw a lot of combat tutorials online that taught me how to basically make one, but to create it in the exact vision I wanted it to be, I had to freestyle a bit & experiment a lot over the past couple days.
that sounds amazing! I’m going on that same path since I want to make an inventory system, too. Could you please help a fellow developer and list the tutorials you watched? Only if you can, pleaseee
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 completely get the statement of one's first ever game idea most likely being trash, but in my own personal opinion, that may not always be the case, especially if it's something you've spent over nine and a half years constantly working on and improving story-wise and gameplay-wise (aka what I have in mind.) I'm not saying what I've got is flawless by any means, but it's something I'm constantly thinking about every single day. I honestly don't care if it succeeds or flops, because it's not about that. It's about making my biggest dream in life a reality, even if no one else but me or my friends would play it
Lesson #4 about tutorials is definitely important. I picked up Godot to tinker around with in the past few weeks and have only put maybe 10 hours into it so far, but when following along with its "first 2D game" tutorial I made sure to deviate from the tutorial every time I got a new idea. For example: - My laptop's native screen resolution is weird (1366x768) which leaves less than 720p for actual game window space, so when the tutorial called for a 640x720 window I picked smaller dimensions (I think 480x540) just to make it fit on my screen. I then added some "padding" to more tightly clamp the player sprite from leaving the visible screen area. - Immediately after getting the player movement to work as instructed, I asked "now can I add _inertia_ to their movement?" It seemed easy enough: the code so far created a movement vector based on your input then added it to the player's position, so all I should need to do is create an _acceleration_ vector based on your input, add it to a persistent _movement_ vector and then update the player's position by _that,_ right? Well, yes, but this created a myriad of bugs and edge cases that I had to work out, before finding a built-in function which could do basically all this in a single call (eliminating 10-15 lines of code on my part). - After implementing the enemy spawn timer, I immediately decided to add a "difficulty ramp" where the timer ticks faster the longer the game progresses. - Then I decided to let the game's title screen spawn enemies as an "attract mode". Which caused a bug where the game could still declare "game over" upon collision with the player, but it didn't take long to find the properties that enable/disabled the collision detection events. Remaining ideas I want to try before calling the tutorial "finished": - Noting the tutorial provides 3 different enemy sprites (selected at random for each one spawned), I want to give each type slightly different movement rules. Maybe even incorporate this into the difficulty ramp logic (e.g. start with the simplest type and add variety as score increases). - Noting that one enemy type is called "flying" I also want to add a "jump" button to give the player an extra option to dodge enemies with. - I also want to add bonus points for "grazing" an enemy (getting in close proximity without actually touching).
3. The video creator starts off the video saying don’t expect to make the next GTA 6, but if someone wants to make GTA 6, they should make a simple stylized shooter game with a few levels. If someone wants to make Skyrim, they should make a simple stylized linear combat game with a dungeon or two. 4. I actually learned tutorials by following them to the tea. I tried what you wrote and failed miserably every time. Following tutorials as a complete beginner is already hard as it is when you don’t know how anything works. Adding a layer of difficulty on top of the existing difficulty just makes everything more difficult than it needs to be. Also, looking at and modifying other people’s code is also about as important as tutorials. Also, looking at other very simple solo developed games like Roblox games & Fortnite creator games should be what devs aspire to create and release if they’re very ambitious
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.
Yeah this is definitely something people undermine before going into it. Most solo devs either commission or make their own music which typically gives the game its own unique vibe. Hell, even game mods have teams dedicated to the gameplay, music, UI, etc.
There is an article called "The door problem" that goes into how all different roles in game development would handle doors and it gives a great insight into what sort of roles there are.
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!
@FredyyDev Nah, straight up bs. You don't help people by telling them their ideas suck and they shoukd give up, any thought process that led you there is wrong, and that's not an opinion
@@lexruptorI agree, what if they told the wright brothers their idea sucks and they should forget about it when they were just starting? What a shame, this youtuber has a huge ego.
@@animer_india i can make games, clicked this out of curiosity. This is a horrible video LOL, the video should of stated to make a very simplified game and expand it even if its not what you wanted to make but implement some of the complex idea's you have. It will save you a ton of headaches later after your practice and learning run mainly because you have to learn to design things modular to keep upgrading the project. Lots of information to process
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".
You are more experienced than me, so hearing that you still enjoy the process is cool... After all, that's what really matters isn't it? Years down the line, I would love to be interested in whatever I'm doing, that's more than what most people achieve tbh
@@estu548 Yes, I do. It's still not "industry standard" for some bigger studio pipelines, but it's becoming an increasingly common and accepted package across the board. Furthermore, it's accessible, free, and highly capable, so there are no costs or other barriers stopping you from diving straight in and beginning to learn (which is major!). Most of the skills you will learn - particularly in the beginning through intermediate stages, are highly transferable and apply generally to all 3D software packages. So learning Blender today would not prevent you from changing to a different software later.
@@estu548 Okay, not as far as experienced as the og poster, but I've been in a video game school for 4 years, been an hobbist for 4 and a pro for 2... Blender is getting better everyday! If your goal is to work in a small indie game dev, or as a solo dev, YEAH, learn blender. If your goal is to work on a big company... Learn blender, you might not use it at work, but it will only improve your skills, plus, more and more studios are starting to use it, so be one of the first in the party ;) . Blender have some flaws for sure (like the horrible texture paint mode that needs a hundred plugins to be decent) but overall, you'll learn everything you need to know, and will have great result without having to pay a single dime.
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.
On the other hand, a proper tutorial system can teach you a lot. Unity's "Learn Unity" course took weeks, but you can learn a lot from it. Random youtube "how to make X" tutorials though... yeah, avoid
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.
Lol, you're good 😅 About the schedule and idea stuff, don't beat yourself up. You can't do a task if you convince yourself it means the world... Dettach a little!
Hmm I am not sure what kind of ai you have implemented but I think you should keep in mind that AI art is being rejected in games on steam. Not sure how the lawsuits will subside but when the smoke clears other sites may do the same. If you are making it from scratch and take pride in that. Just remember that someone else made something from scratch too and then another person came along and created a code that could copy their work and basically put a price tag on it. Good luck.
"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.
for anyone that may feel discouraged from the title don't worry about it. Every twat has an opinion unfortunately and making video games is one of the MOST difficult things you can attempt. just keep going on dont let the small people put you down
Před 11 měsíci+88
I thought you were going to say something important
You do not need to draw. Just use Vector Leyers (shapes) to create what you want. For example, I use Krita and I do not draw at all because I only need to create simple android game. (For example, I created gold, shining, 3D button that looks awesome but does not fit for my game bc I am broke to create size I need and I only started 2 days ego).
Yepp. I feel you on this. I really like making small games becasue I enjoy coding. The problem is that I have a nice idea, i get all excited, start coding then want to create some basic sprites and I spend like 8 hours to create a few relly basic looking drawings. By the end of it I am not even motivated to continue coding so I just drop the idea. (1. No I don’t want to hire or ask others to draw my game because I create games only for myself. 2. Yes I draw only very basic placeholder stuff with no animations and shading and nothing and yet it still takes up like 90% of my time on a project. I simply nevet liked drawing and I can not say that I have any talent at it.)
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!
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) 💀
People act like things are harder then they are, my mother knows assembly, but can barely make google work. I think difficult is highly exaggerated in coding in general.
@@notthatguy3249 She used to program for airplane systems, infrastructure that's still running today. A game would be nothing for her. I think on the outside looking in, stuff seems hard. But humans aren't all that smart and are largely equally capable, less the savants, so, if she can do it, I'm pretty sure anybody can, just takes time and effort as do all things. She used to tell me about dudes she worked with who legit read programs in binary. Just huge books of zeros and ones they'd carry around and study for bugs, and then go back and correct issues one literally bit at a time. Effort yeilds amazing results, people are simple not aware that they have the ability, yet not yet have they given the effort.
@@honaleri Programming infrastructure for airplane systems sounds way easier to do in assembly than to program anything with a visual display out. I’ve used assembly, anything non-visual is fine, like any other programming language. When you have to create a window and render things inside it though, that’s tough. Also assembly is directly translated to binary instructions, if you work with assembly for anything in cybersecurity you’re probably gonna be looking at the hexadecimal or binary. (Usually hex, since it’s the same as binary but is faster to read through).
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!
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
Same thing here, I was so glad that I realized it soon enough. Looking back at those few days, I really feel like I escaped a trap, and I am grateful for it.
@@mmmcola6067 I assume you mean the garden thing. Comes with the existential mindset I suppose. I learnt to appreciate things better in my search for meaning as I inevitably realised appreciation is what I was missing all along. Now I try my best to love rather than hate, no good comes from hate, just more hate. Was a nihilist and now an absurdist but I didn't learn about those terms until I had already experienced them myself. They're interesting philosophical beliefs but without having believed them yourself at one point, they sound a bit crazy. Absurdism is essentially just nihilism with the negativity turned into positivity. If this wasn't about the garden, I'm so sorry lol
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.
It’s important to remember that the best game ideas are the ones that get finished. Someone with a mediocre game idea who actually sat down and made it is still better off than someone with a great game idea that never tried, or gave up on it. So don’t be afraid to just get started and make necessary adjustments as you go.
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 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.
It isn't frowned upon by any programmers. The point programmers make is that you can't use visual programming to make every last thing about your game. In the end, you have to dive into code in order to get every last functionality you're looking for, assuming your game has any level of complexity. Tutorials simply mention that if you are to be a "game developer", you have to pull off the bandaid early and just dive into code. "Outsourcing" as you mentioned isn't really relevant if you are personally trying to become a game developer. That's the only reason it *seems* frowned upon, tutorials teaching how to develop games simply mention that you won't get there limiting yourself to visual programing. For artists and such (and even game devs themselves) to quickly prototype, as you mentioned, makes visual scripting a massive asset, and no one is downplaying it's impact on game development.
Visual scripting has pros and cons. The ideal way to use them is to get a thing working the way you want, and THEN make it into a script. Its the best way to learn code, because it separates the functionality from the syntax and formatting, making both easier to digest. It bypasses the one-dev-only nature of many VS systems, the performance impact, and the potential lacking functionality of nodes as you learn scripting and optimizations. Learning code is inevitable, and using VS only is some kind of challenge for a reason. Webs of nodes are too hard to read and work with, and grouping can only help so much. The brain is trained like a muscle. Use the starter weights until you are comfortable, then advance. If your only goal is to lift small weights, thats fine too! You shouldn't justify yourself to internet sickos who don't even lift at all. That being said, Visual Scripting makes you a game designer, a game developer, but not REALLY a programmer... You don't HAVE to be a programmer, but you gotta stop insisting the entry-level stuff is objectively equivalent. 5lb weights wont make you a bodybuilder.
I use 90 percent VS when making my games. I can't actually code from scratch, but I can understand code when I read it and analyze it. Chat gpt is amazing when I'm trying to make code because I litterally say "this is what I'm trying to do why isn't it working?" It then gives me a detailed message of what might not be working and steps to correct it. I integrated steam achievements and leader board in just a day and I understand it much more because chatgpt helped me.
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
"Finish your project before moving on" This is SO important. In the same vein, do NOT overscale your project. Know yourself, your strengths and your resources. Plan according to that. You will not make the next Skyrim as an indie dev, hell you won't make the next mario either. Creating games takes a LOT of time and I personally tend to vastly underestimate the effort required to create something fully. So stick to a small scale, finish that project and if you want to, make it larger afterwards. But going in with the highest hopes is bound to result in failure. I... tested that for yall. You're welcome 😂
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.
bro after almost 2 years of gamedev I now have a giant backlog of functions I wrote myself. Text display, sprite display, state machines. I just move the folder to each new project and it gets larger everytime I need a new implementation. It feels fucking amazing.
@@americantoastman7296That's the best part actually, with the "tool" (in this case script) you created, you don't need to worry too much about creating new one, adjust your "tool" for your new game and you can now focus on the other stuff.
Pathfinding is ... its own can of worms to be dealing with. I remember one RTS (Warzone 2100) where pathfinding algorithms could make or break the experience of certain missions ... for example, the AI builds small groups of units at base to send out and harass the player with, BUT depending on which version you were playing (e.g. original retail vs. current open source) sometimes these units would logjam at various points (such as a base's entrance), which on the one hand meant you didn't get these small groups harassing you at intervals, but on the other meant you'd discover a HUGE snag of enemy units all at once the moment you set foot upon _their_ base.
These "tuts" where they wanna be like "your game idea sucks" are so dumb. Like, I happen to know my game ideas are NOT bad ones, in fact they'll topple the whole industry. These only serve to discourage people like me from doing it and actually making our game, using what's ultimately a subjective viewpoint - "how good a game idea is"
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.
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'm sure his game ideas suck too given that he doesn't actually show any of his own work on his channel. "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." A more apt comparison is saying that you need to learn music production in order to be a DJ.
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.
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
Bonus tip: if you ever make a game that is a massive success, release a sequel to it, some dlc for the sequel, end it on a cliffhanger and NEVER make a third game.
Better pro-tip: never release any sequels. 90% of sequels fail horribly, 9% of them become tolerable mediocre continuations (fans would have a love-hate relationship with it), and only 1% of them become successful.
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
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!
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.
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.
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?
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.
Good points, but I think you misinterpreted lesson 1 and 5... Or maybe I failed communicating. Lesson 1 is about managing expectations and realize that you have to learn game design too. Lesson 5 is about learning more each day and being able to understand the differences between engines.
@@BusinessWolf1 i disagree, the way fredyy phrased it sounded like any big game idea your brain comes up with will not work out. That does not seem like a good way to get into game development, as it is not true (Minecraft, Stardew, etc). Maybe don't start it as your first project but to say that you will never be able to make a game with high depth and good quality is not true.
@@FredyyDev the sentences "your game idea sucks" and "manage expectations and realize that you have to learn game design" are two very different sentences lol
@@thecolorblue7427 I should say: any big game idea you have before you even started to learn game development is likely bad, as in, misled, naive or too simplistic. Not because you are stupid, but because you don't understand what goes into making a game. Every game idea I ever had, had to be scaled down, even the ones I thought were "easy". And I never said every game idea is bad, that wouldn't make sense.
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!!!
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
"Learn by example" is related. The first time you open the IDE (especially if all you do is create a blank project) you will simply have NO idea where to find anything, or what is even expected of you to create literally anything at all. You kind of NEED something like that explained/shown to you, but once you've got that down then you can start working on the higher-level elements.
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.
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
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.
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! 🥶🥶🥶👽
I'm currently in my early stages, still working out how software works and the fundamentals of making games. My first project was a flappy bird clone, which I mostly followed a GMTK tutorial for. Now I'm working on a clone on a game called Super Crate Box, which is a bit more complicated to make, but it's very satisfying making progress on it without using many tutorials. So far the game runs exactly as intented, but my intended plan was shit. At this point, i'd rather that than if it didnt work at all
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.
It is good to not just let some things fail, but learn how to identify _when_ to let it fail. In the business/management world, this is a mantra called "fail faster".
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.
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.
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
I don't know if this was your intention but lesson 1 may be better said as not to fall in love with your ideas rather than saying that your ideas suck. What you might be saying is that the execution of the idea may not live up to the expectations set with the imagined idea. In other words, don't fall for a pipe-dream or expect the "oh haha this is just a little thing I'm working on" to eventually be uploaded on Steam.
Appreciate the “make 3 crappy games first” tip, what I really wanna make is a tycoon style game, but thinking a platforms, a top down shooter, and a tower defense game will be good stepping stones to learn from.
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.
Well, look, if your main focus is to be an artist and you don't have a problem relying on a team, than you are more than right to do so! Bring your vision to this world!
Yeah, the "I want to make a game" can be taken a few ways: are you the type who wants to "make" as in control/direct the _overall design_ of a game, or "make" as in _actually build_ the inner workings of a game? Note that for small personal projects it is feasible to be both.... For an analogy, it's like asking whether you want to be the design architect or the construction engineer. Sure, it may be the architect who gets the "name brand" recognition for the finished piece, but it's the engineer who ensures that your game doesn't crash when dozens-to-hundreds of physics objects start interacting with each other in real time, that your game doesn't miss player inputs when the performance unexpectedly dips, etc...
Funny how I started straight with leson 5, I jumped around way too much, even outside of gamedev (webdev, serverdev, ebedded, osdev..), but it allowed me to skip lesson 1 and 2, since I was allready so familiar with how to do big projects I could start with my game right away and I think it turns out pretty great
With that quite clickbaity thumbnail I didn't expect much from this video, but the advices you gave are really good. Though I'm fortunately past these, I'd definitely recommend this video to a beginner (and I probably will too).
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.
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.
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 :)
Sometimes I have too much fun with the title 😅 But that is also the game of youtube, right? However, if you feel like the title and thumbnail don't match the video, that is a problem too, it means people feel deceived. Thank you for the feedback, I will improve next time!
I'm currently on a hiatus for games, and just do features alone, like JS in a local file, without any libraries. One thing I can't get running is to make a button press run, while an input field is active, to run code; or just the button press itself. I mean, .click() does work, so having the button for the mouse is already there, but pressing "enter" just does nothing, and no example code on the internet works, not even in their demo.
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
Don't worry much about where to start, the important thing is the direction you are going, and I have a video on the works to help on that. And please finish the video if you want some proper motivation! Don't give up on me, dude, you got this
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!
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.
You draw in viewers with a toxic clickbait title and then demonstrate for 4 minutes that you don't really understand the game development community at all, but instead project your own flaws onto the viewers framing yourself as a paragon of indie game development when you have no credentials, larping as a full time game developer "job" you self admittedly got from a reddit post. I'm glad you're having fun making videos.
Let me correct you: I make an admitelly confrontational title (meant to be more of a joke), I don't claim to be better than anyone and instead I give advice that I would find useful to me about LEARNING game development and dealing with failure, and my job is real no matter where I got it from. Also, my channel is just starting, I have no obligation to show "credentials". And now you come into the story: you read a CZcams title and get offended, you mindlessly scroll through the video looking for flaws, you then watch the rest of my videos looking for more flaws and spend 20 minutes typing a comment that helps no one but your butthurt ego. Guess who's projecting here... I'm glad you had fun watching my videos tho!
@@FredyyDev Let me correct you: Nobody has to "look for flaws" they are in the video and I intended no anger even if it feels toxic to you (meant to be more of a joke). And now you come into the story: you read a CZcams comment and get offended and spend 20 minutes typing a comment that helps no one but your butthurt ego. Guess who's projecting here...
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".
My first attempt at making a game was me trying to jumpstart into an rpg horror game. Safe to say I cried. Like sure - I was copying the tutorial, but I didn't actually understand what each line of code did. Now I have not made another game since but I am trying to do a suspense rpg, and honestly I also recommend that when you watch tutorials, actually try to understand what each line does.
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!
If you are just starting, everything will look like alien tech! Take lesson 3 to heart, don't overwhelm yourself trying to learn the whole engine. Pick a game type you like and look for tutorials for that game type, dedicate to learning what the tutorial teaches... You will naturally have questions and an urge to understand more!
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.
![Eminem - Houdini [Official Music Video]](http://i.ytimg.com/vi/22tVWwmTie8/mqdefault.jpg)
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.
This is how you write a critique!
Thanks, it bothered me for so long reading dumb comments that never added any value to the video...
I respect your view and since making this video I changed a lot about how I present my ideas. I was trying to say something like "think about your game ideas realistically" and it came across the way it did, which is my fault, but not my intention...
Anyway, I agree with all your tips! I might even include them in future videos if that's ok with you.
I'm glad you said this. I wasn't a fan of the entire 1st point being "Hey you should consider the fact that your idea is trash". It really rubbed me the wrong way, a good idea or a bad idea is entirely subjective, and if you start telling people that the idea they have churning in their head is trash then you might have single-handedly killed a great idea before it could ever manifest.
That said you do benefit from being willing to drop ideas that don’t work or indeed suck.
@@badbeardbill9956
It depends on what defines a bad idea. I'd say it's impossible to really create a bad idea. If you come up with an idea from the heart, it can't be a bad idea.
A bad idea usually sprouts when your objective is something like money or success. If you have a good idea for a game, the creation of the game is the objective, you want your thoughts to escape your head.
If your idea is coming from you, if it is something you truly care about, do not throw it away, it's a good idea, you might not have the best way to execute it, but work hard and you will get there. If you do not really truly care about the game you're making, if it doesn't come from the heart, from originality, then it is good to let it go.
Just because it's bad doesn't mean you did something wrong. I think everyone misunderstood him and take themselves way too serious if you really think he meant "Your game Sucks!!" no he basically saying your first game most likely isn't gonna be some great masterpiece, so don't let yourself down.
*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 made a battle-city like game back in 2013 and I have no idea now how I made it "crash" (does it only outside the debugger) on purpose and load a totally different level sequence.
@@theloststarbounderdo you still have it
why Archive just use version control simple
You can also use them for the few good pieces of code that may be in there
And copy + paste "some" animation and the entire walking mechanics if you're making a similar game to one of them
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.
That is what it's all about!
Ahaha, I had the same experience about 2 years ago on ue4, glad you did it. I remember when I started writing my inventory with no tutorials, I really learned a lot, I guess in those days I really learned how to code
I made an inventory system with tutorials, but didn't like it so after reading your comment I will also make one myself.
Same thing happened with me for combat systems. I saw a lot of combat tutorials online that taught me how to basically make one, but to create it in the exact vision I wanted it to be, I had to freestyle a bit & experiment a lot over the past couple days.
that sounds amazing! I’m going on that same path since I want to make an inventory system, too. Could you please help a fellow developer and list the tutorials you watched?
Only if you can, pleaseee
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.
Thank you for this! Appreciate your insight and I definately agree!
I completely get the statement of one's first ever game idea most likely being trash, but in my own personal opinion, that may not always be the case, especially if it's something you've spent over nine and a half years constantly working on and improving story-wise and gameplay-wise (aka what I have in mind.) I'm not saying what I've got is flawless by any means, but it's something I'm constantly thinking about every single day. I honestly don't care if it succeeds or flops, because it's not about that. It's about making my biggest dream in life a reality, even if no one else but me or my friends would play it
Lesson #4 about tutorials is definitely important. I picked up Godot to tinker around with in the past few weeks and have only put maybe 10 hours into it so far, but when following along with its "first 2D game" tutorial I made sure to deviate from the tutorial every time I got a new idea. For example:
- My laptop's native screen resolution is weird (1366x768) which leaves less than 720p for actual game window space, so when the tutorial called for a 640x720 window I picked smaller dimensions (I think 480x540) just to make it fit on my screen. I then added some "padding" to more tightly clamp the player sprite from leaving the visible screen area.
- Immediately after getting the player movement to work as instructed, I asked "now can I add _inertia_ to their movement?" It seemed easy enough: the code so far created a movement vector based on your input then added it to the player's position, so all I should need to do is create an _acceleration_ vector based on your input, add it to a persistent _movement_ vector and then update the player's position by _that,_ right? Well, yes, but this created a myriad of bugs and edge cases that I had to work out, before finding a built-in function which could do basically all this in a single call (eliminating 10-15 lines of code on my part).
- After implementing the enemy spawn timer, I immediately decided to add a "difficulty ramp" where the timer ticks faster the longer the game progresses.
- Then I decided to let the game's title screen spawn enemies as an "attract mode". Which caused a bug where the game could still declare "game over" upon collision with the player, but it didn't take long to find the properties that enable/disabled the collision detection events.
Remaining ideas I want to try before calling the tutorial "finished":
- Noting the tutorial provides 3 different enemy sprites (selected at random for each one spawned), I want to give each type slightly different movement rules. Maybe even incorporate this into the difficulty ramp logic (e.g. start with the simplest type and add variety as score increases).
- Noting that one enemy type is called "flying" I also want to add a "jump" button to give the player an extra option to dodge enemies with.
- I also want to add bonus points for "grazing" an enemy (getting in close proximity without actually touching).
If I had a dollar for all the tutorials that I've watched, I'd be ballin'
3. The video creator starts off the video saying don’t expect to make the next GTA 6, but if someone wants to make GTA 6, they should make a simple stylized shooter game with a few levels. If someone wants to make Skyrim, they should make a simple stylized linear combat game with a dungeon or two.
4. I actually learned tutorials by following them to the tea. I tried what you wrote and failed miserably every time. Following tutorials as a complete beginner is already hard as it is when you don’t know how anything works. Adding a layer of difficulty on top of the existing difficulty just makes everything more difficult than it needs to be.
Also, looking at and modifying other people’s code is also about as important as tutorials.
Also, looking at other very simple solo developed games like Roblox games & Fortnite creator games should be what devs aspire to create and release if they’re very ambitious
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.
Yeah this is definitely something people undermine before going into it. Most solo devs either commission or make their own music which typically gives the game its own unique vibe. Hell, even game mods have teams dedicated to the gameplay, music, UI, etc.
I am almost all of the above except a programmer 💀
Artits
There is an article called "The door problem" that goes into how all different roles in game development would handle doors and it gives a great insight into what sort of roles there are.
"Sometimes you have to make The Witcher 1 and 2 before you can make The Witcher 3" - Tim Rodgers
Facts. Just look at where Fallout or GTA started
no shit
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!
In some other comment you'll find my thought process for the title, but hey, your opinion is valid too! Thanks for tuning in
@FredyyDev Nah, straight up bs. You don't help people by telling them their ideas suck and they shoukd give up, any thought process that led you there is wrong, and that's not an opinion
@@lexruptorI agree, what if they told the wright brothers their idea sucks and they should forget about it when they were just starting? What a shame, this youtuber has a huge ego.
@@lexruptor I agree
I think it was worded wrong. It was just missing a (probably) or smth
Bruh, it felt like loading screen tips
Lesson 7: Switching to your pistol is always faster than reloading.
Lesson 8: Headshots does more damage than bodyshots.
Lesson 9: The faster a gun fires, the more ammo it consumes per second.
Lesson 10: Reloading refills your guns ammo.
yep i'm dumb because all i got here was opinions
I can understand how you feel
@@animer_india i can make games, clicked this out of curiosity. This is a horrible video LOL, the video should of stated to make a very simplified game and expand it even if its not what you wanted to make but implement some of the complex idea's you have. It will save you a ton of headaches later after your practice and learning run mainly because you have to learn to design things modular to keep upgrading the project. Lots of information to process
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".
You are more experienced than me, so hearing that you still enjoy the process is cool... After all, that's what really matters isn't it? Years down the line, I would love to be interested in whatever I'm doing, that's more than what most people achieve tbh
Do you recommend learning blender for game graphics?
@@estu548 Yes, I do. It's still not "industry standard" for some bigger studio pipelines, but it's becoming an increasingly common and accepted package across the board. Furthermore, it's accessible, free, and highly capable, so there are no costs or other barriers stopping you from diving straight in and beginning to learn (which is major!). Most of the skills you will learn - particularly in the beginning through intermediate stages, are highly transferable and apply generally to all 3D software packages. So learning Blender today would not prevent you from changing to a different software later.
@@estu548 Okay, not as far as experienced as the og poster, but I've been in a video game school for 4 years, been an hobbist for 4 and a pro for 2... Blender is getting better everyday! If your goal is to work in a small indie game dev, or as a solo dev, YEAH, learn blender. If your goal is to work on a big company... Learn blender, you might not use it at work, but it will only improve your skills, plus, more and more studios are starting to use it, so be one of the first in the party ;) .
Blender have some flaws for sure (like the horrible texture paint mode that needs a hundred plugins to be decent) but overall, you'll learn everything you need to know, and will have great result without having to pay a single dime.
How do I gain a internship as a 3d game artist that uses blender?
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.
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.
On the other hand, a proper tutorial system can teach you a lot. Unity's "Learn Unity" course took weeks, but you can learn a lot from it. Random youtube "how to make X" tutorials though... yeah, avoid
Facts
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.
Lol, you're good 😅
About the schedule and idea stuff, don't beat yourself up. You can't do a task if you convince yourself it means the world... Dettach a little!
Making a game from scratch and picking Java is plain insane tbh.
I suggest you to use something like JMonkeyEngine, or LibGDX
@@KDSBestGameDevi like java
Hmm I am not sure what kind of ai you have implemented but I think you should keep in mind that AI art is being rejected in games on steam. Not sure how the lawsuits will subside but when the smoke clears other sites may do the same. If you are making it from scratch and take pride in that. Just remember that someone else made something from scratch too and then another person came along and created a code that could copy their work and basically put a price tag on it. Good luck.
"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.
for anyone that may feel discouraged from the title don't worry about it. Every twat has an opinion unfortunately and making video games is one of the MOST difficult things you can attempt. just keep going on dont let the small people put you down
I thought you were going to say something important
lmao
These are important but way to obvious
Lesson #7: You cant escape art. I cant draw.
You do not need to draw. Just use Vector Leyers (shapes) to create what you want. For example, I use Krita and I do not draw at all because I only need to create simple android game. (For example, I created gold, shining, 3D button that looks awesome but does not fit for my game bc I am broke to create size I need and I only started 2 days ego).
Yepp. I feel you on this. I really like making small games becasue I enjoy coding. The problem is that I have a nice idea, i get all excited, start coding then want to create some basic sprites and I spend like 8 hours to create a few relly basic looking drawings. By the end of it I am not even motivated to continue coding so I just drop the idea. (1. No I don’t want to hire or ask others to draw my game because I create games only for myself. 2. Yes I draw only very basic placeholder stuff with no animations and shading and nothing and yet it still takes up like 90% of my time on a project. I simply nevet liked drawing and I can not say that I have any talent at it.)
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!
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) 💀
People act like things are harder then they are, my mother knows assembly, but can barely make google work.
I think difficult is highly exaggerated in coding in general.
@@honaleri I would be astonished if your mother would be able to code a fully functional game in assembly
@@notthatguy3249 She used to program for airplane systems, infrastructure that's still running today. A game would be nothing for her. I think on the outside looking in, stuff seems hard. But humans aren't all that smart and are largely equally capable, less the savants, so, if she can do it, I'm pretty sure anybody can, just takes time and effort as do all things. She used to tell me about dudes she worked with who legit read programs in binary. Just huge books of zeros and ones they'd carry around and study for bugs, and then go back and correct issues one literally bit at a time. Effort yeilds amazing results, people are simple not aware that they have the ability, yet not yet have they given the effort.
@@honaleri
Programming infrastructure for airplane systems sounds way easier to do in assembly than to program anything with a visual display out.
I’ve used assembly, anything non-visual is fine, like any other programming language. When you have to create a window and render things inside it though, that’s tough.
Also assembly is directly translated to binary instructions, if you work with assembly for anything in cybersecurity you’re probably gonna be looking at the hexadecimal or binary. (Usually hex, since it’s the same as binary but is faster to read through).
Abselote darkness route: Learn binary and code the game using nothing but 1s and 0s
Godoted with the sauce
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!
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
Same thing here, I was so glad that I realized it soon enough. Looking back at those few days, I really feel like I escaped a trap, and I am grateful for it.
2 Cor 4:4, repent. Heil GOD
you are strangely philosophical. I like it
@@mmmcola6067 I assume you mean the garden thing. Comes with the existential mindset I suppose. I learnt to appreciate things better in my search for meaning as I inevitably realised appreciation is what I was missing all along. Now I try my best to love rather than hate, no good comes from hate, just more hate. Was a nihilist and now an absurdist but I didn't learn about those terms until I had already experienced them myself. They're interesting philosophical beliefs but without having believed them yourself at one point, they sound a bit crazy. Absurdism is essentially just nihilism with the negativity turned into positivity. If this wasn't about the garden, I'm so sorry lol
@@cheesymcnuggets Man, I wish I was you
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.
git: 'gud' is not a git command. See 'git --help'.
The most similar command is
gui
@@tuhkiscgibin6627 casul
You have to put a little of creativity too
It’s important to remember that the best game ideas are the ones that get finished. Someone with a mediocre game idea who actually sat down and made it is still better off than someone with a great game idea that never tried, or gave up on it. So don’t be afraid to just get started and make necessary adjustments as you go.
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!
Yes! I agree.
My man decided to speak the best language ever created : *F A C T S*
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.
It isn't frowned upon by any programmers. The point programmers make is that you can't use visual programming to make every last thing about your game. In the end, you have to dive into code in order to get every last functionality you're looking for, assuming your game has any level of complexity. Tutorials simply mention that if you are to be a "game developer", you have to pull off the bandaid early and just dive into code. "Outsourcing" as you mentioned isn't really relevant if you are personally trying to become a game developer. That's the only reason it *seems* frowned upon, tutorials teaching how to develop games simply mention that you won't get there limiting yourself to visual programing. For artists and such (and even game devs themselves) to quickly prototype, as you mentioned, makes visual scripting a massive asset, and no one is downplaying it's impact on game development.
Visual scripting has pros and cons. The ideal way to use them is to get a thing working the way you want, and THEN make it into a script. Its the best way to learn code, because it separates the functionality from the syntax and formatting, making both easier to digest. It bypasses the one-dev-only nature of many VS systems, the performance impact, and the potential lacking functionality of nodes as you learn scripting and optimizations.
Learning code is inevitable, and using VS only is some kind of challenge for a reason. Webs of nodes are too hard to read and work with, and grouping can only help so much.
The brain is trained like a muscle. Use the starter weights until you are comfortable, then advance. If your only goal is to lift small weights, thats fine too! You shouldn't justify yourself to internet sickos who don't even lift at all. That being said, Visual Scripting makes you a game designer, a game developer, but not REALLY a programmer... You don't HAVE to be a programmer, but you gotta stop insisting the entry-level stuff is objectively equivalent. 5lb weights wont make you a bodybuilder.
How does it help artists at all?
from my experience: its bloated, difficult to maintain and slow to implement
I use 90 percent VS when making my games. I can't actually code from scratch, but I can understand code when I read it and analyze it. Chat gpt is amazing when I'm trying to make code because I litterally say "this is what I'm trying to do why isn't it working?" It then gives me a detailed message of what might not be working and steps to correct it.
I integrated steam achievements and leader board in just a day and I understand it much more because chatgpt helped me.
Making games is easy and enjoyable. Selling them is very hard and annoying.
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
This problem is the biggest error for my brains.
"Finish your project before moving on"
This is SO important. In the same vein, do NOT overscale your project. Know yourself, your strengths and your resources. Plan according to that. You will not make the next Skyrim as an indie dev, hell you won't make the next mario either. Creating games takes a LOT of time and I personally tend to vastly underestimate the effort required to create something fully. So stick to a small scale, finish that project and if you want to, make it larger afterwards. But going in with the highest hopes is bound to result in failure. I... tested that for yall. You're welcome 😂
@@americantoastman7296 we all tested the higher bounds and failed honestly XD but still the "Don't overscale" advice should also be included
Honestly? That makes it your opinion.
I wouldn't say that the game idea itself sucks. You thinking you'll be able to execute it as your first game on your first try is probably what sucks.
People aren't bad at making games they are bad at being motivated, having willpower, and being thorough.
Being in tutorial hell sucks, but when you escape it, it's the most amazing feeling 😌👌
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.
That's genuinely awesome!
bro after almost 2 years of gamedev I now have a giant backlog of functions I wrote myself. Text display, sprite display, state machines. I just move the folder to each new project and it gets larger everytime I need a new implementation. It feels fucking amazing.
@@americantoastman7296That's the best part actually, with the "tool" (in this case script) you created, you don't need to worry too much about creating new one, adjust your "tool" for your new game and you can now focus on the other stuff.
Pathfinding is ... its own can of worms to be dealing with. I remember one RTS (Warzone 2100) where pathfinding algorithms could make or break the experience of certain missions ... for example, the AI builds small groups of units at base to send out and harass the player with, BUT depending on which version you were playing (e.g. original retail vs. current open source) sometimes these units would logjam at various points (such as a base's entrance), which on the one hand meant you didn't get these small groups harassing you at intervals, but on the other meant you'd discover a HUGE snag of enemy units all at once the moment you set foot upon _their_ base.
These "tuts" where they wanna be like "your game idea sucks" are so dumb. Like, I happen to know my game ideas are NOT bad ones, in fact they'll topple the whole industry. These only serve to discourage people like me from doing it and actually making our game, using what's ultimately a subjective viewpoint - "how good a game idea is"
lol welcome to the channel my dude
@@FredyyDev nah, I'd rather watch an hour of Brackeys or something, lame
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.
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'm sure his game ideas suck too given that he doesn't actually show any of his own work on his channel.
"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."
A more apt comparison is saying that you need to learn music production in order to be a DJ.
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.
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
Bonus tip: if you ever make a game that is a massive success, release a sequel to it, some dlc for the sequel, end it on a cliffhanger and NEVER make a third game.
volvo's tech tips
Better pro-tip: never release any sequels. 90% of sequels fail horribly, 9% of them become tolerable mediocre continuations (fans would have a love-hate relationship with it), and only 1% of them become successful.
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
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!
1.jpg
2.jpg
3.jpg
…
Seems clear to me!
If You Can't Get Viewers after this Inflammatory Video, Give Up
what
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.
This was definitely something I needed to hear. Congrats to you sir for being so inspirational
Thanks!
Yeah, I agree with the stuff in this video. I will definitely take notes from this when i start to do game development.
3:13 as an aspiring Unreal...fiddler, I can confirm that documentation is very valuable. Be grateful for it.
Finally, a free IQ test that's accurate. And i'm super dumb.
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.
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?
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.
Good points, but I think you misinterpreted lesson 1 and 5... Or maybe I failed communicating. Lesson 1 is about managing expectations and realize that you have to learn game design too. Lesson 5 is about learning more each day and being able to understand the differences between engines.
@@FredyyDev+1 he missed the point of lesson 1 entirely
@@BusinessWolf1 i disagree, the way fredyy phrased it sounded like any big game idea your brain comes up with will not work out. That does not seem like a good way to get into game development, as it is not true (Minecraft, Stardew, etc). Maybe don't start it as your first project but to say that you will never be able to make a game with high depth and good quality is not true.
@@FredyyDev the sentences "your game idea sucks" and "manage expectations and realize that you have to learn game design" are two very different sentences lol
@@thecolorblue7427 I should say: any big game idea you have before you even started to learn game development is likely bad, as in, misled, naive or too simplistic. Not because you are stupid, but because you don't understand what goes into making a game. Every game idea I ever had, had to be scaled down, even the ones I thought were "easy". And I never said every game idea is bad, that wouldn't make sense.
0:22 jokes on you, I love programming
how did you learned it?
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!!!
this video is so well put together, I was really suprised seeing that it doesn't have more views
We are getting more! Slowly but surely
Bro, this video was uploaded 17 hours ago....
Hey bro, look how far we've come!
Ikr@@FredyyDev
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
"Learn by example" is related. The first time you open the IDE (especially if all you do is create a blank project) you will simply have NO idea where to find anything, or what is even expected of you to create literally anything at all. You kind of NEED something like that explained/shown to you, but once you've got that down then you can start working on the higher-level elements.
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.
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
Nice video, everything said does not only apply to game programming but in overall programming. 👌
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.
"the true game is the friends that we've made in the path"
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! 🥶🥶🥶👽
You have guts, sir
@@FredyyDev Thank you, sir. i needed that kind of validation!
Low level is easier for me to learn because I'm setting up my own system, i don't need to learn how the engine works because i made it myself.
0:11 I wasn't thinking of GTA 6
the advice at the end about not becoming too attached to an idea is the most underrated game dev tip out there
I'm currently in my early stages, still working out how software works and the fundamentals of making games. My first project was a flappy bird clone, which I mostly followed a GMTK tutorial for. Now I'm working on a clone on a game called Super Crate Box, which is a bit more complicated to make, but it's very satisfying making progress on it without using many tutorials. So far the game runs exactly as intented, but my intended plan was shit. At this point, i'd rather that than if it didnt work at all
That's some good advice. I'll just give up.
don't 😰
Addtional Lesson. Never try to make a MMORPG
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.
It is good to not just let some things fail, but learn how to identify _when_ to let it fail. In the business/management world, this is a mantra called "fail faster".
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.
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.
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
I don't know if this was your intention but lesson 1 may be better said as not to fall in love with your ideas rather than saying that your ideas suck. What you might be saying is that the execution of the idea may not live up to the expectations set with the imagined idea. In other words, don't fall for a pipe-dream or expect the "oh haha this is just a little thing I'm working on" to eventually be uploaded on Steam.
Appreciate the “make 3 crappy games first” tip, what I really wanna make is a tycoon style game, but thinking a platforms, a top down shooter, and a tower defense game will be good stepping stones to learn from.
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.
Well, look, if your main focus is to be an artist and you don't have a problem relying on a team, than you are more than right to do so! Bring your vision to this world!
@@FredyyDev :)
(I also rely on a ton of programs and AI. But working with another human would be fantastic. Can't wait to have money to hire people.)
Yeah, the "I want to make a game" can be taken a few ways: are you the type who wants to "make" as in control/direct the _overall design_ of a game, or "make" as in _actually build_ the inner workings of a game? Note that for small personal projects it is feasible to be both....
For an analogy, it's like asking whether you want to be the design architect or the construction engineer. Sure, it may be the architect who gets the "name brand" recognition for the finished piece, but it's the engineer who ensures that your game doesn't crash when dozens-to-hundreds of physics objects start interacting with each other in real time, that your game doesn't miss player inputs when the performance unexpectedly dips, etc...
"I want to paint a house, not become a painter"
Well you're going to have to learn how painters work if you want to do a professional job...
Funny how I started straight with leson 5, I jumped around way too much, even outside of gamedev (webdev, serverdev, ebedded, osdev..), but it allowed me to skip lesson 1 and 2, since I was allready so familiar with how to do big projects I could start with my game right away and I think it turns out pretty great
With that quite clickbaity thumbnail I didn't expect much from this video, but the advices you gave are really good. Though I'm fortunately past these, I'd definitely recommend this video to a beginner (and I probably will too).
People flocking here after Unity announce their stupid plan incoming in 3... 2... 1....
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.
Teach me
Me too. It almost took up my entire lunch break to write it.
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.
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.
It's just a process of solving problems slowly on your own until you get good and start solving them faster
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 :)
Sometimes I have too much fun with the title 😅
But that is also the game of youtube, right?
However, if you feel like the title and thumbnail don't match the video, that is a problem too, it means people feel deceived.
Thank you for the feedback, I will improve next time!
@@FredyyDev No for sure. It's definitely good at getting attention. I don't have a big issue with it, just wanted to give feedback.
What a pedantic title.
maybe you just d_u mb brother
@@jimdajmiser3176My advice to you is to use a grammar checker.
I'm currently on a hiatus for games, and just do features alone, like JS in a local file, without any libraries.
One thing I can't get running is to make a button press run, while an input field is active, to run code; or just the button press itself.
I mean, .click() does work, so having the button for the mouse is already there, but pressing "enter" just does nothing, and no example code on the internet works, not even in their demo.
i thought this was gonna be a satire video, but these tips are actually valuable, wow, thank you buddy
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
Don't worry much about where to start, the important thing is the direction you are going, and I have a video on the works to help on that. And please finish the video if you want some proper motivation!
Don't give up on me, dude, you got this
Splendid explanation
Thanks!
As a person who never had any plans to make games, this video is very informative!
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!
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.
You draw in viewers with a toxic clickbait title and then demonstrate for 4 minutes that you don't really understand the game development community at all, but instead project your own flaws onto the viewers framing yourself as a paragon of indie game development when you have no credentials, larping as a full time game developer "job" you self admittedly got from a reddit post. I'm glad you're having fun making videos.
Let me correct you: I make an admitelly confrontational title (meant to be more of a joke), I don't claim to be better than anyone and instead I give advice that I would find useful to me about LEARNING game development and dealing with failure, and my job is real no matter where I got it from. Also, my channel is just starting, I have no obligation to show "credentials".
And now you come into the story: you read a CZcams title and get offended, you mindlessly scroll through the video looking for flaws, you then watch the rest of my videos looking for more flaws and spend 20 minutes typing a comment that helps no one but your butthurt ego. Guess who's projecting here...
I'm glad you had fun watching my videos tho!
@@FredyyDev Let me correct you: Nobody has to "look for flaws" they are in the video and I intended no anger even if it feels toxic to you (meant to be more of a joke). And now you come into the story: you read a CZcams comment and get offended and spend 20 minutes typing a comment that helps no one but your butthurt ego. Guess who's projecting here...
I probably needed to hear this. Ok… I definitely needed to hear this.
The DOOM soundtrack at the background of 5th lesson is just funny in this situation for some reason
I’d like my 5 minutes back
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".
lmaoo
Bro literally shows none of his work on his own channel. This is some Extra Credits tier nonsense.
My first attempt at making a game was me trying to jumpstart into an rpg horror game. Safe to say I cried. Like sure - I was copying the tutorial, but I didn't actually understand what each line of code did.
Now I have not made another game since but I am trying to do a suspense rpg, and honestly I also recommend that when you watch tutorials, actually try to understand what each line does.
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!
If you are just starting, everything will look like alien tech! Take lesson 3 to heart, don't overwhelm yourself trying to learn the whole engine. Pick a game type you like and look for tutorials for that game type, dedicate to learning what the tutorial teaches... You will naturally have questions and an urge to understand more!
Chill with that title 💀
Title that with chill
Though love
Faz um canal em portugues pra gente também po kkkkk
Kkkkkkkk quem sabe um dia
Thanks, Freddy! Solid advice!
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.
Well, now unity is dead soooo....