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.

  • gnus_migrate@programming.dev
    link
    fedilink
    English
    arrow-up
    5
    ·
    1 year ago

    I completely understand where you’re coming from because I very much used to be very much the same way. Problems like this can be frustrating because you feel like you’re wasting your time, youre telling the engine the right thing but its not working and you feel like it’s taking time from other problems you could be solving.

    My advice: go easy on yourself. Write down all the other stuff you have to do so you dont forget it, and give yourself time to focus on that specific problem to see how you can solve it. Dont look at it as something blocking the other stuff that you have to do, look at it as just another task in your project.

    In the case of the Z axis issue, take a step back and start reading about the Z axis and how it works. Create a separate project and start playing with it to see how it works for yourself. Convince yourself that this feature is not broken, and if you still can’t make it work on a simple project at least you’ll have reduced the problem so that if you ask for help online, it’s more likely someone can spot the issue and tell you where you went wrong. If you do manage to make it work, at least you’ll have something working to compare your original code with and make it more likely to spot the problem.

    What differentiates an experienced developer from someone who’s learning, is that an experienced developer has already ran into and solved a ton of small problems like these. It’s a hurdle you need to overcome if you want to become effective at developing games.