Game Development

4246 readers

21 users here now

Welcome to the game development community! This is a place to talk about and post anything related to the field of game development.

Community Wiki

founded 2 years ago

MODERATORS

Ategon@programming.dev

Frank@programming.dev

LiquidityC@programming.dev

My biggest difficulty is choosing a language/framework/engine (programming.dev)

submitted 2 years ago by ICastFist@programming.dev to c/gamedev@programming.dev

5 comments fedilink hide all child comments

Which is somewhat ironic, because I know that "sit and just do it" is the ideal start. Think less about choosing, just pick it up and go.

But I end up spending more time looking up things and getting excited about them.

LOVE2D? Oooh, it's lua! It can even run on Android! DragonRuby? Oooh, simple and lightweight and fast! Oh wait, Godot just had a new update! Hey, maybe I should get back to programming Java, libGDX looks neat! Damn, Raylib feels like it does many things right! And on it goes...

I overwhelm myself with choices, start a bit then abandon at the second hard-ish hurdle (like menu/interface showing under the map despite lots of fiddling with the Z position, in Godot). So, yeah, just exposing my problem, I suspect I'm not alone in this.

you are viewing a single comment's thread
view the rest of the comments

[–] tatterdemalion@programming.dev 6 points 2 years ago

I think it's fine to engine hop a bit as long as you actually build something interesting in each one. Even if it's the same game every time, you're still learning different ways to do something. That's not a waste.

If your goal is to finish a game, you should maybe take notes about the engines you've tried and set yourself a deadline for choosing your favorite.