Staged rollouts
A new release does not reach every server at once. It goes out in waves:
| Wave | Share of servers | Moves on after |
|---|---|---|
| 1 | 5% | 24 hours without a rise in errors |
| 2 | 25% | 24 hours |
| 3 | 100% |
Which servers are in wave 1 is decided by a hash of the server token, so it stays the same between
releases. If you always want to be early, use the beta channel instead.
Health signal
Section titled “Health signal”During a rollout, servers on the new version report startup failures and plugin exceptions (counts
only, no stack traces unless you enable telemetry.stack-traces). If the error rate is clearly above
the previous version, the rollout pauses and the release is pulled from the waves that have not got it.
Servers that already updated keep the version. /forgerelay rollback <plugin> puts the previous jar back.
Downloads
Section titled “Downloads”Since 1.2.0 ForgeRelay downloads a delta against the jar you already have, usually a tenth of the full size. If no delta exists for your version, it downloads the full jar. Mirrors in each region serve the same files; ForgeRelay retries on another mirror after a timeout (1.3.1).