Not sure if this goes here or not? but ive dabbled a little here and there with different things but i lack like every skill to make a game. Im wondering what aspect or skill is worth getting better at, for gamedev?
I cant code, i cant draw/3d art, i cant make music, im bad with ideas, etc.
Where do i even begin or what would you advise?
Get a journal started. Write and take notes, preferably digital notes. Get your head clear on what you’re trying to do. Maybe there are people out there who can execute a big undertaking by just bumbling forward on the thought/motivation of the day, but I haven’t met them.
Perhaps you’re trying to save time by asking others where to start, but I advise you to get used to making judgement calls on where you ought to put your attention.
Slow down and settle in. Work on it a little every day. Record your progress. Learn and practice.
And go easy on yourself. Everybody starts somewhere.
Game dev is multidisciplinary but let’s get real, you need to know to code. Without this you won’t get far. Realistically it will take you years to learn the fundamentals.
Instead of learning skills individually, learn them as you go! Just pick an engine - I’d recommend Godot - and get to work.
Here’s a nice challange about building increasingly difficult games: The 20 games challange.
You start with Pong, which is super easy to get the hang of. You could even follow a tutorial for that one and then try to use less and less tutorials as you go down the list.
Just get going instead of watching endless how-to videos, which is an easy trap for beginners. Actually starting a project and finishing one are two of the most important skills. You’ll quickly learn which parts come naturally to you and which ones you need to focus on.
As for creativity, once you’re done with each game, try to think of a twist to spice it up and add it to the game. It can be a simple thing, like e.g. with Pong using multiple balls or maybe adding obstacles - just test what’s fun and what’s not!
I second this! Even if you study game dev at college (if that’s an option for you), you won’t get around that part in the end. Picking your tools and iteratively learning how to use them is the way to go. The Internet is full of tutorials.
At best set yourself achievable goals (like cloning simple games) and keep your expectations low. Don’t try to do too many things at once and take your time learning.
Agree with this! It’s one of those things where if you want to learn to do it, just start doing. (Which it sounds like op is, so keep at that.) You find where the gaps are then focus on learning just enough to get past your roadblock.
Join a game jam.. You might not get far, but joining and trying will get you started down the road. A theme will be provided which can help get your ideas flowing, and you can use existing assets to pull stuff together along with tutorials.
For your first jam, you can even just make a physical game using cards or tokens from other sets to explore different ideas.
From there, pick a game engine and try a bunch of tutorials then pick something you want to make and use tutorials and documentation not as guides, but as references to achieve the thing you want to build.
Also, start small, like really small. Smaller than you think you need to. Pong and Snake are significantly easier than Battleship or Risk.
I second that. Many jams are meant to have participants team up. There’s nothing to win, so you can use it as a learning opportunity and let more experienced participants teach you a bit.
Global Game Jam might be the best bet here, as the site organizers often offer workshops in preparation for newbies. Unfortunately the last one was just a few weeks ago, so you would have to wait for almost a year for the next.
That Brackeys one I linked doesn’t have the same kinda workshop, but they do have a number of tutorials on their YT channel and it starts this Sunday.
I don’t think this is a good answer but a funny anecdote. I was pretty obsessed with video games starting with the NES. I got really good with computers, programming, etc and more than 10 years into being a professional software developer, I figured it was time to actually look at making a game, arguably the reason I got into coding to begin with. Turns out that so little about game development is actually coding these days, been that way for decades now.
There are so many parts to making a video game, as you mentioned. If you want to do everything yourself and from scratch, yeah you will need to understand code and physics/math formulas, etc. Maybe some graphic design for the world you’re creating, maybe some music and audio effects knowledge. But there are also game engines out there that will do virtually or literally all of this for you.
I guess my real point is, figure out what you enjoy doing, and how you can contribute that to making games. It doesn’t matter if you’re good at it or don’t even know where to start, the important part is that you do start and stick with it.
Did you actually end up doing game dev?
Little bit by myself, mainly some puzzle stuff in the browser. Turns out I really enjoy writing code than making games.
Look up the pros and cons of the different editors (Unreal, Unity, Godot). Pick one and start making the simplest of games. There’s some good tutorials that can walk you through things.
As you learn, you will probably find a specific aspect that you like a lot and you can concentrate on building your expertise for that. Might be coding, animation, shading, 3d modeling. Who knows.
The important part is to start using the software, but really aim for simple stuff for now and use good quality tutorials and courses. I used mostly YouTube and some Udemy.
Depending on your age/savings, this can give you a good idea in what to study if this is an option.
You can learn to do anything. You’ll have an easier time learning if you like doing it. So what do you like? Or: what would you want to try and see if you like?
Also: why do you want to make a game? What interests you about that?
Two options:
Mod games until you get better at those. Start small, replacing textures with minor changes.
Help manage a mod project and fill soft skills gaps that the team has. Don’t push the actual people working on the game too hard, help organise
