Define the exact test subject
Each result must name the edition, server software or loader, game version, runtime, template revision and relevant configuration. Broad labels such as ‘Forge supported’ hide the combinations that actually determine compatibility.
Run a repeatable lifecycle test
We must install the candidate from documented inputs and exercise the actions you will depend on.
- Install and first start
- Client connection and basic permissions
- Clean stop and restart
- Unexpected-stop recovery
- Representative gameplay or workload
- Backup creation and restore
- Upgrade test and rollback notes
Record evidence and limitations
We will preserve logs, configuration, the test date, and any limits we observe. We will test the combination again after a software, runtime, or template change when that change affects the result.
Passing this process does not guarantee that every third-party plugin, mod, add-on or client device will work.
Publish states people can interpret
Candidate and testing states are not orderable support claims. Supported will mean the documented combination passed the stated checks. Retired will identify combinations no longer recommended for new deployments.
See the current version-policy page