Merge pull request #1132 from ludovic111/feat/switch-to-0-2

🤖 Agent: merged after verify passed. Go-day step 5 (docs/versioning.md): Ludovic said go on 2026-10-23 ("tu peux envoyer la 0.2"). The bridges are out (v2026.10.22 and launcher-v0.17.0), and the latest stable is v2026.10.22.07, built after the freeze. The launcher redesign (#1269) and the mod browser are merged.
This commit is contained in:
Ludovic Marie
2026-10-23 02:16:49 +02:00
committed by GitHub
6 changed files with 11 additions and 4 deletions
+1
View File
@@ -0,0 +1 @@
0.2
+3 -1
View File
@@ -240,7 +240,9 @@ If the new game crashes or doesn't come up in time, the server goes back to the
and puts the world back as it was just before the switch (the world the new game left is kept in
`backups/`). `horizon-server rollback` goes back to the release before by hand, keeping the world as it is
(it backs it up first). `--version vX.Y.Z` installs a given release, and `--archive FILE --version NAME` an
archive you have, such as your own build. A stopped server is switched and starts on the new release next
archive you have, such as your own build. A server still on a release from before the last dated one doesn't know
that 0.2 comes after the dated releases and says it is up to date: run `horizon-server update --version v0.2.0`
once ([versioning](versioning.md)). A stopped server is switched and starts on the new release next
time. Set `HORIZON_NO_UPDATE_CHECK=1` in the server's environment to turn the check off.
Coming: `console` (attach to a server running in the background), `ban` and `pardon` as their own
+1 -1
View File
@@ -2661,7 +2661,7 @@ dependencies = [
[[package]]
name = "horizon-launcher"
version = "0.1.5"
version = "0.2.0"
dependencies = [
"clap",
"dirs 5.0.1",
+1 -1
View File
@@ -1,6 +1,6 @@
[package]
name = "horizon-launcher"
version = "0.1.5"
version = "0.2.0"
edition = "2021"
license = "MIT"
description = "Downloads, prepares and starts Horizon builds"
+4
View File
@@ -62,6 +62,10 @@ Only if you say yes, and each kind has its own switch. Everything is off by defa
Often. Every change players can see is released automatically after it is merged, so new versions can come out several times a day. On the **Alpha** channel the launcher installs each one as soon as it is built; on **Stable**, the default, it installs a tested build about once a day. See [Install](/docs/install#updating).
## What do the version numbers mean?
Since 0.2, every release has a number: 0.2.0, then 0.2.1, 0.2.2 and so on, one for each release. The game and the launcher are both on 0.2 and count on their own, so you can play Horizon 0.2.7 with launcher 0.2.3. A bigger step, such as 0.3, is announced when it comes. Releases before 0.2 were named after the day they came out (2026.10.19.15); every 0.2 release is newer than all of them.
## How do I report a bug?
See [Logs, crashes and bug reports](/docs/troubleshooting).
+1 -1
View File
@@ -35,7 +35,7 @@ The game opens on vanilla's title screen. Your worlds, options and logs live in
## Updating
- **Horizon.** The launcher looks for a new release when it starts and every four hours while it is open. With **Install new versions automatically** on (the default), it installs one and moves you to it if you were on the newest. New releases come out many times a day, and old versions stay installed until you remove them on the **Versions** page.
- **The launcher.** It updates itself from its own releases, then shows **Restart** in its footer.
- **The launcher.** It updates itself from its own releases, then shows **Restart** in its footer. A launcher from before 0.2 (0.16 or older) updates twice in a row: first to 0.17, then to 0.2. Then it installs Horizon 0.2 like any update.
## Stable and Alpha