this post was submitted on 19 Jun 2023
35 points (100.0% liked)
Asklemmy
44554 readers
975 users here now
A loosely moderated place to ask open-ended questions
If your post meets the following criteria, it's welcome here!
- Open-ended question
- Not offensive: at this point, we do not have the bandwidth to moderate overtly political discussions. Assume best intent and be excellent to each other.
- Not regarding using or support for Lemmy: context, see the list of support communities and tools for finding communities below
- Not ad nauseam inducing: please make sure it is a question that would be new to most members
- An actual topic of discussion
Looking for support?
Looking for a community?
- Lemmyverse: community search
- sub.rehab: maps old subreddits to fediverse options, marks official as such
- [email protected]: a community for finding communities
~Icon~ ~by~ ~@Double_[email protected]~
founded 5 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
I've worked a bit in serious gaming before, as back-end developer. Normally, you choose an engine that suits the needs (and resources) of the game you're making, and then you'll still do tons of scripting and possibly changes to the engine. In some cases, you might be forced by circumstances to use a certain engine, then you'll do even more alteration. In other cases, you might make your own engine, which is the most time consuning and complex but gives the best match with your aspirations for the game. It's made to measure after all. Either way, without coding it'll be impossible to make a game.
Since you have no experience coding, start small. I've seen many people with big dreams but little experience starting on a big project thinking their great engine-of-choice will carry them, and it just never works out. Do something simple like Pong to learn, then slowely go more complex each time you made something work. You can follow tutorials, but make sure you understand what you're doing, don't blindly copy-paste. Once you understand what you're doing, switching between (scripting) languages isn't too hard anymore.
I don't know what your aspirations are, but realise that fancy AAA games aren't something you'll teach yourself as a hobby project over night. 3D adds a lot of complexity, wanting to be able to make your own shaders and engine changes even more so. Game AI can also get quite complex, depending on how far you want to take it. Big games have a whole team of people specialising at different things for a reason, doing that all alone is hard. But for a hobby project without time limit it can be fun!
Take it one step at a time and have fun with it. Especially when it's a hobby, not your job. And remember, liking games and being a game dev are two very different things! I've seen a lot of people wanting to become game devs because they like games. And that's ok, as long as you're interested in the technical side of it. Because it is quite technical, games are some of the hardest things to program. You'll be doing a lot of math and stuff. So if you just like playing them, maybe ask yourself if development really what you want to do. But if you like the technical side, have patients and are willing to learn. Go for it! But start small and take it one step at a time.
It's hard to give more specific advice really. As with the engine choice, it all depends on whát kinda game you're making and what your aspirations are.