How to Contribute

A contribution is anything that makes the sources, the tools or the guides better: a bug fix, a new feature or game system, a new tool or editor, a port of content between versions, a guide, a translation. Bug fixes are only one kind. See What Counts for the full list.

The workflow

Create a Git account on the community Git server and link it to Discord with the Archivist bot.
Pick a task from the issue board, or bring your own idea. Tasks are labeled easy, medium, or hard. Leave a comment so others know you are working on it. For a bigger feature or a new tool, open an issue first and describe the plan, so nobody builds the same thing twice.
Fork the repository and create a branch for your task.
Make your change. Keep it focused on one task.
Test it. Build it and check that it works in game, or explain in the pull request why it cannot be tested yet.
Open a pull request. Describe what you changed, why, and how you tested it. Link the task.
Respond to review. A team or Core member reviews it. Small fixes are normal.
Merged. Your contribution counts, and the bot updates your tier.

Good pull requests

One task per pull request.
A clear title, such as Fix crash when equipping gear in training mode, Add guild storage window or New tool: costume preview.
For a new feature or tool: what it does, how to set it up (configs, DB changes), and its limits.
Screenshots or logs when they help.
No unrelated formatting changes.
No passwords, IPs, keys, or database credentials.

Not sure where to start?

Ask in the Discord help channel. Documentation and small fixes are a good first step; new features and tools are just as welcome once you know your way around.