Skip to content

Before Contributing (Code)

Jump to bottom
Tony edited this page Aug 5, 2026 · 8 revisions

If you're not experienced with contributing to Github projects, I recommend watching a few tutorial videos first and getting familiar with the concepts.

Team

  • Toni (gdscript) is the project lead. Reach out to her if you need help with Github/Godot.
  • drywall is good with Blender. Idk just sayin.

Branches

When creating a new branch (for making a specific change), base it on ###-Next and name it ###-slop-yourbranchnamehere

Main

The Main branch contains the latest "stable" code. This is the code that made it past playtesting without any critical issues.

XXX-Next

This is the unstable code. ###-Next is numbered according to the current "checkpoint" we're working on. Checkpoints try to achieve a limited collection of project goals.

Slop and Tidy

New branches for implementing stuff should be based on ###-Next.

  • The naming convention should be ###-slop-yourbranchnamehere Cleaning up your code as you go is advised, but sometimes we gotta refactor anyway.
  • These branches are named ###-tidy-specificnamehere

Coding Style

I developed my coding style during Godot 3. They didn't have a standardized coding style back then so everyone made up their own. Here's mine:

https://github.com/programnoir/GDTemplate/wiki/Coding-Style-Guidelines

I'm expecting some deviation in contributions, but the more everything matches up, the better.

Clone this wiki locally