docs(readme): protocol 4, and module-uo v1.0.1 in the quick start
The landing page is the project's front door, and both of its copy-pasteable values were stale. The installer handoff block printed "Protocol version 3". That block exists to be typed into Admin -> Shard, and protocol 4 shipped on 2026-08-19 as sidecar v2.0.0 and overlay v1.0.0. A stale number there comes back from the sidecar as a 409, which INSTALL.md's own troubleshooting table notes "looks exactly like your shard going offline". The module quick start still pointed at the v0.3.0 install manifest and MODULES=uo@0.3.0. module-uo is on v1.0.1; asset names verified against the release. Co-Authored-By: Claude <noreply@anthropic.com>
This commit is contained in:
@@ -134,11 +134,11 @@ Ultima Online that manifest is `module-uo-<version>.json` from the
|
||||
[Module-uo releases](https://gitea.whitlocktech.com/RunicGateway/Module-uo/releases):
|
||||
|
||||
```
|
||||
https://gitea.whitlocktech.com/RunicGateway/Module-uo/releases/download/v0.3.0/module-uo-0.3.0.json
|
||||
https://gitea.whitlocktech.com/RunicGateway/Module-uo/releases/download/v1.0.1/module-uo-1.0.1.json
|
||||
```
|
||||
|
||||
A compose-managed host can declare the set instead of clicking, with
|
||||
`MODULES=uo@0.3.0=<that URL>` — resolution at container start is idempotent and offline-safe,
|
||||
`MODULES=uo@1.0.1=<that URL>` — resolution at container start is idempotent and offline-safe,
|
||||
so a restart with the network down brings the site up exactly as it was.
|
||||
|
||||
> **The module system shipped on 2026-08-12** and this is now simply how the site works — a
|
||||
@@ -176,7 +176,7 @@ unprivileged account, and finishes by printing the four values to paste into **A
|
||||
```
|
||||
Base URL http://<shard-host>:8080
|
||||
WebSocket URL ws://<shard-host>:8080/ws
|
||||
Protocol version 3
|
||||
Protocol version 4
|
||||
Auth token 4f9c…
|
||||
```
|
||||
|
||||
|
||||
Reference in New Issue
Block a user