Help build RustyCore
There is more than one way to contribute. You can write Rust, reproduce a bug, investigate protocol behavior or make the documentation easier to follow.
Pick a starting point
| If you enjoy… | Try this |
|---|---|
| Writing and explaining | Improve a setup step or clarify a confusing guide |
| Testing and investigation | Reproduce an issue with the server revision and client build recorded |
| Rust development | Coordinate an open issue and implement its complete agreed scope |
| WoW internals | Compare a specific behavior with versioned reference source and captures |
Browse open issues, or ask where you can help on Discussions and Discord. Check the port plan before starting substantial work so dependencies and overlapping contributions are clear.
Your first pull request
- Follow server setup to build the project.
- Read the contributor guide and coordinate the scope on an issue.
- Work on a feature branch based on 3.4.3. Include affected consumers, tests and docs.
- Validate the complete change and record the results. Website changes also need the VitePress build.
- Open a PR into 3.4.3, explaining the problem, resulting behavior and verification.
Human and AI-assisted changes follow the same review requirements. The maintained contributor guide owns the detailed workflow and validation links.
Understanding the port
Our goal is full behavior parity with the TrinityCore-derived 3.4.3 server. For protocol, gameplay, persistence and runtime work, compare the complete operation with the exact versioned reference functions. Relevant client/server evidence fills gaps where the source is ambiguous.
Code being present, connected to production and verified against the reference are distinct milestones. Record what your change actually proves.
- Current state and evidence
- Versioned references
- Shared engineering guide
- Architecture and ownership
- Module development
Reporting problems
Use the issue forms. Include reproduction steps, expected and actual behavior, server commit and client build. Share only sanitized logs; keep credentials, private configuration and session data out of reports.