Contributor guides
Start by building the checkout and selecting the Minecraft target you want to edit. Read the architecture before changing a compiler, native runtime or game boundary, then choose verification that exercises the affected behavior.
Work on the project
- Build and run Toolchains, Minecraft targets, and the standalone playground.
- All-addon dev stand Run Create, Sable, Propulsion, and Aeronautics together.
- Maintain addons Standalone builds, integration boundaries, and lifecycle tests.
- Verification Choose focused checks and understand release gates.
Understand the internals
- Architecture Compiler, native runtime, actor host, and ownership.
- Module and package guide Put changes in the layer that owns their behavior.
- Native test coverage Find evidence at Rust, FFI, JVM, and game boundaries.
Measure performance
- In-world VM benchmarks Profile the server cost of real and headless computers.
- Performance reports Recorded workloads, measurements, and optimization evidence.
Repository workflow
Follow the repository’s working guidelines. Use GitHub issues for reproducible bugs and architectural work. Include the relevant verification commands and results with a change; visible UI changes benefit from screenshots.