Stack* ... oops...

Turns out bluesky doesn't take too kindly to gif uploads. Here's a better resolution sample. #gamedev

This one is in Unity, but the concepts are similar enough in nature. It's also a good reference for how something like what I'm looking for may be implemented to a degree.

youtu.be/gdW_rXFE1Gk?...

Heck yeah it is! Glad to help you on your journey. The most important thing is that it evolves with you and your game.

All the articles on this describe it way too professionally, which unless you're in a big studio, isn't really that important. It's just important to pick the essentials for reference in development.

gamedevbeginner.com/how-to-write...

A design document is a written work of documentation that contains many facets of your game's designs and plans. Primarily, it will explain mechanics, themes, and plans for development. Anything about your game can be referenced from there. But, as an individual or team, it can be what you want.

Not enough people in the space and industry like to take a design document past a pitch.

Makes me feel bad for the passion people put into them only for it all to be ignored 25% into development.

Whether you're in a team or even by yourself, use design documents! People forget things, or may not even be on the same page for ideas. Or sometimes you innovate in the moment and want a place to put those passions. They're useful for everyone on the team or everything, engineering, art, writing.

I'm a little bit cheesy...

Thank you! GDScript feels a lot like other scripting languages and the GUI feels a lot like Unity's (albeit more intuitive). We'll get there!