I'd also recommend you make a one-page and a 10-page document about your game. The one-page will summarise the entire game, briefly, efficiently and it will be your vision of what the game will be. The 10-page will go into detail, and you can do a longer document if your game is complex. These 2 documents are essential if you're designing your first game - it will be a reference point when you're not sure what to do next, and it will ensure that you don't stray too far from your original goals, it will also prevent you from biting off more than you can chew

Tip 1: Only worry about mechanics in your first game.

2:22 Personally, Scratch also helped me learn the general idea of why to write certain code, not what to write.

“Tutorials won’t make the game for you and you shouldn’t use tutorials to make your entire game.” Now that’s a good DAMN quote that can be applied to anything creative.

"Don't learn the engine to make a game, make a game to learn the engine." I will use that as my college quote.

i love how its "How to make YOUR dream game with no experience", step one, get experience.

6:40 the ‘’EACH’’ was personal

aha, those grade 1-5 scratch lessons are finally becoming useful !!

Man, I think RPG Maker is underrated sometimes. The community for it is so vast and varied, you can get VERY creative with it. Of friggin course it's not as limitless as other engines, but I don't think it's as limited as people make it seem.

Game Dev here:

8:30 this is so true. I started out in scratch in middle school, and I wasn't that good at coding, I made a snake game, and that was about it. Just recently I coded a neural network into scratch

If you are going for 3D then Godot is really good for that learning by doing without tutorials approach because all the documentation is build in to the built in code editor meaning it's very easy to get the info you need right away. Also GDScript is just kinda great to use.

8:27 just time stamping this quote due to its shear awesomeness