I started a technical journal on GitHub. Figured I’d make a post about the it here, since it will often be relevant to Defold.
For example, the first entry for October 5, 2024 outlines my first experience contributing to the Defold source code. I hope these kinds of writeups inspire others to contribute as well. Even just implementing a single feature is a highly valuable learning experience, and not too complicated if you have a reasonable software development background.
I’m also writing a sort of post-mortem or reflection on a game prototype I made over the course of 25 days. I’m starting again from scratch, which I’ll be posting about as well. If you’re interested in seeing how I organize and architect a relatively large game project, then perhaps consider following along.
If that sounds interesting to you, then feel free to check it out. If not, then that’s okay too! Happy Defolding.
I suppose I’ll update this thread with posts that are related to Defold.
October 7, 2024 Scripts or Modules? It’s an Architecture Decision, Moreso Than a Data Decision
A common problem for Defold users is struggling to decide what data goes where, whether some logic might be better suited to live in a script versus a module, which scripts should be responsible for managing which modules, or some other organizational problem that inevitably results in major refactors, stunted progress, and drained motivation. In this entry, I’ll try to explain how I solved this recurring problem, such that it’s no longer a recurring problem.
