he/him

Nerd, programmer, writer. I like making things!

  • 35 Posts
  • 868 Comments
Joined 1 year ago
cake
Cake day: June 20th, 2023

help-circle

  • It’s kinda funny that Godot’s custom language GDScript is, at least on a surface level, pythonic (no list comprehensions, context managers, decorators, etc, it’s mostly syntactical similarities). But type hints do make it run faster!

    I was blessed to get to skip most of the old pains in python. I only had a handful of scripts that ever needed to be ported from 2 and they didn’t rely on any libraries. The ecosystem is easy to work with and I’m looking forward to working with Python for the foreseeable future






  • I agree with your post, lots of good advice! I’d add the general advice to pick an engine or framework, learn how to use it at a basic level, and do a bunch of game jams. Even if you don’t submit, nothing will teach you more than figuring out how to go from idea to small “finished” game in a short period of time. It won’t be easy, and your games will probably suck for a while, but if you stick with it you’ll have a solid knowledge base and skillset to start building more ambitious projects. Also there are longer game jams (Godot Wild is several weeks), be careful not to burn out like OP says.

    You don’t have to write your own engine. If you want to learn how games work behind the scenes knock yourself out, but I find that most people would rather make a game than a tool (which an engine inherently is).