this post was submitted on 03 Aug 2023
12 points (80.0% liked)
Open Source
31200 readers
160 users here now
All about open source! Feel free to ask questions, and share news, and interesting stuff!
Useful Links
- Open Source Initiative
- Free Software Foundation
- Electronic Frontier Foundation
- Software Freedom Conservancy
- It's FOSS
- Android FOSS Apps Megathread
Rules
- Posts must be relevant to the open source ideology
- No NSFW content
- No hate speech, bigotry, etc
Related Communities
- !libre_culture@lemmy.ml
- !libre_software@lemmy.ml
- !libre_hardware@lemmy.ml
- !linux@lemmy.ml
- !technology@lemmy.ml
Community icon from opensource.org, but we are not affiliated with them.
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
Honestly, I think biting the bullet and trying your hand at coding will be worth your time. Visual scripting typically fall into two camps: code but it is visual (in this case it is just slower, more cumbersome and harder to read) or limiting (this may be fine depending on your needs, but you may also outgrow it). A middleground could be coding where the vast majority is done for you. For example in Godot, there are many nodes that are fully built and just need your custom settings. There are even freely available nodes in the asset store if you need more. Then, if you need some behaviour that does not yet exist, you just code that little part, which will be a great learning experience in of itself.
My biggest tip though, regardless of the approach you take, is keep it simple. Your first game should be ridiculously simple. For example, the first game I made was a 2d scroller spaceship shooter where there were only asteroids as "enemies". I could then add onto that to test my coding skills, and eventually it was fairly fun, even if it had simple roots.