• 0 Posts
  • 97 Comments
Joined 2 years ago
cake
Cake day: June 15th, 2023

help-circle



  • Structlog actually bit me like this! Had a dict that I manipulated:

    expectation spoilers

    expected a copy, but actually modified the original dict. Just did a my_dict.copy() (IIRC - I don’t remember whether I needed a deep copy or not)

    edit: goeie shit, Bas! Leer je de studenten wel debuggen en unit testing? Dat was echt gemis toen ik klaar was bij de HU, en vooral unit testen zou veel hebben geholpen tijdens het maken van mijn code.
















  • Start with pen and paper - no computer, because that’ll just distract you.

    Write down what kind of game you want to make. Sketch out what you want your player to see when they play the game (top down, third person, first person; which UI elements should they see? Health? Mana or power bars? Selected items?). Does it have a story of sorts? What kind of setting (future, past, fantasy, sci-fi). 2D or 3D? What kind of visual style are you going for (realistic, cartoony, abstract?).

    This will be your Game Design Document. You don’t have to get it perfectly at the first go - iterate over it, scratch things that you feel won’t work.

    Once you have something that looks like a minimally viable product (MVP), THEN you can start making something in Godot, Game Maker, or Love2D. Because now you have something to follow along. Try to get something out ASAP, because feedback from people who are not you is important. Maybe you made something that feels fun to you, but no one else likes it - you would want to know that as soon as possible, not after toiling away for 5 years.

    Do not start caring about “what is the fastest programming language”. Even the slowest of languages are fine, because you’re learning how to build a game, not how to program like a pro.