8fa3eef809
After installing a version (CLI install and update, the window's automatic install, MCP), when it is not prepared and another installed version with the same Minecraft version is, the launcher copies that version's prepared resources. Players who auto-updated to v2026.10.13.1 no longer prepare again, and can play it without their Minecraft folder. The prepared output depends on the Horizon version as well as Minecraft's: the manifest records the hashes of the vanilla exporter sources it was made with, and prepare_native_client.py writes every file and the manifest's schema. So resources are reused only when both versions have the same pinned jars in research-lock.json, the same prepare_native_client.py and the same exporter sources the manifest lists. They are copied (prepare rewrites files in place, so hard links would tie the versions together), into a partial folder renamed when complete. install and the MCP tool say when it is prepared already. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
27 lines
780 B
TOML
27 lines
780 B
TOML
[package]
|
|
name = "horizon-launcher"
|
|
version = "0.1.4"
|
|
edition = "2021"
|
|
license = "MIT"
|
|
description = "Downloads, prepares and starts Horizon builds"
|
|
|
|
[workspace]
|
|
|
|
[dependencies]
|
|
gpui = "0.2.2"
|
|
ureq = { version = "2", features = ["json", "tls"], default-features = false }
|
|
serde = { version = "1", features = ["derive"] }
|
|
serde_json = "1"
|
|
pulldown-cmark = { version = "0.12", default-features = false }
|
|
flate2 = "1"
|
|
tar = { version = "0.4", default-features = false }
|
|
zip = { version = "2", default-features = false, features = ["deflate"] }
|
|
dirs = "5"
|
|
self-replace = "1"
|
|
image = { version = "0.25", default-features = false, features = ["jpeg"] }
|
|
clap = { version = "4", features = ["derive"] }
|
|
horizon-theme = { path = "../crates/horizon-theme" }
|
|
|
|
[profile.release]
|
|
strip = true
|