Thanks for your interest in contributing to our projects. This repository is the public hub for our applications (issues, discussions, and docs), not the main source-code host.
- Improve docs – Fix unclear wording, add examples, or extend FAQs.
- Report issues – Bugs, crashes, performance problems, and documentation issues.
- Suggest features – New ideas or improvements to existing systems.
- Help other players – Answer questions or share tips in Discussions.
- Submit pull requests for docs – Small, focused improvements to the documentation and community guides.
Before making large changes, please open an issue or discussion so we can align on direction.
We use labels to keep issues organized and easy to triage. Some key labels you may see:
bug– Gameplay or UI defects.crash– Hard crashes, freezes, or fatal errors.multiplayer– Online, matchmaking, or co-op issues.performance– Low FPS, stuttering, or long load times.feature-request– New features or improvements.documentation– Docs, wiki, or in-game help issues.question– Clarification or general questions.
Triage and status labels:
triage– Newly filed and waiting for maintainer review.needs-info– We need more details before we can act.confirmed– Reproduced or clearly understood.duplicate– Already covered by another issue.fixed– Resolved in a released or upcoming build.wontfix– We do not plan to change this for now.known-issue– Tracked issue with known limitations or workarounds.high-priority– Issues we plan to address as soon as possible.
When filing an issue, please pick the template that best matches your situation. This makes it easier for us to apply the right labels and respond quickly.
When editing or adding documentation:
- Keep it short and direct. Favor clear sentences over long paragraphs.
- Use headings and bullet lists to make content easy to scan.
- Target both players and developers – explain concepts without heavy jargon.
- Screenshots and diagrams are welcome when they help clarify instructions.
- Keep examples generic and safe – do not include personal data or secrets in commands or logs.
- Keep pull requests focused on a small, coherent set of changes (for example, updating a single doc or section).
- Follow the existing tone and formatting of nearby content.
- Fill out the pull request template, especially the How to test or How to review section.
We may request changes or propose alternative approaches. This is normal and part of working together.
For open-ended ideas, playtest feedback, and questions, please use GitHub Discussions. Issues are best suited to track specific, actionable work.
By participating in this project, you agree to follow our Code of Conduct.