3e825eaa40
Prism's metadata moves a native jar's classifier into its artifact name (com.mojang:jtracy:1.14.38:natives-windows becomes com.mojang:jtracy-natives-windows:1.14.38) and Prism stores libraries at their name's path, so every native jar of a Prism 26.3 install is in com/mojang/jtracy-natives-windows/1.14.38/jtracy-natives-windows-1.14.38.jar, not at the version JSON's path. The bytes and sha1 are Mojang's. Preparing from a linked Prism folder stopped on the first one (jtracy on Windows). horizon-prepare now looks there when the version JSON's path is missing; the copy is still checked against the version JSON's sha1. The missing-file hints no longer tell players of other launchers to install the official one. Reported by famescare on Discord. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>