docs(readme): the module system shipped #3

Merged
whitlocktech merged 1 commits from docs/module-system-shipped into main 2026-08-12 23:05:26 +00:00
Showing only changes of commit bd2e1df84a - Show all commits

View File

@@ -141,10 +141,9 @@ 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@0.3.0=<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. so a restart with the network down brings the site up exactly as it was.
> The module system is landing: it lives on the website's **`edge`** branch and reaches `main` > **The module system shipped on 2026-08-12** and this is now simply how the site works — a
> as one cutover at the end of the current workstream. A `main` checkout today serves the > `main` checkout is a game-agnostic core with a Modules screen, and Ultima Online arrives as
> Ultima Online features from core directly and has no Modules screen — same site, same URLs, > the module above or not at all.
> nothing to install.
**A game that is not Ultima Online?** That is what the **A game that is not Ultima Online?** That is what the
[**Integration-kit**](https://gitea.whitlocktech.com/RunicGateway/Integration-kit) is for — [**Integration-kit**](https://gitea.whitlocktech.com/RunicGateway/Integration-kit) is for —