diff --git a/HOSTING.md b/HOSTING.md
index 4c8e451..7479c14 100644
--- a/HOSTING.md
+++ b/HOSTING.md
@@ -7,7 +7,9 @@
 3. Add the mods from `modpack.md` (use the launcher's built-in Modrinth/CurseForge browser, or drop jars straight into the instance's `mods/` folder).
 4. **Set up the server first** — do the "The server" and "Pre-generate terrain before the party starts (Distant Horizons Full-mode)" steps below *before* continuing here.
 5. Launch the client, go to **Multiplayer → Add Server**, enter `minecraft.mivanchenko.de:25565`, and join for real. Set your preferred video settings (these land in `options.txt`). No manual flying pass needed — Distant Horizons is installed server-side (same build both sides) and streams accurate LOD data directly to any connected client with Distant Generation enabled, so coverage is automatic for every participant, not just something baked in by the host ahead of time.
-6. Quit the launcher, then export the instance via **right-click the instance → Export Instance** (don't blindly zip the raw folder — the exporter lets you pick what's included). Check: `mods/`, `config/`, `options.txt`, `servers.dat`. Uncheck: `logs/`, `crash-reports/`, `screenshots/`, `Distant_Horizons_server_data/` (not needed — each client builds its own via the server-side streaming), and any asset/library caches — those regenerate automatically on first launch and just bloat the zip. Name the result `modpack.zip`, with the instance's folder (`LANParty/...`) as the zip's top-level entry.
+6. Quit the launcher, then export the instance via **right-click the instance → Export Instance** (don't blindly zip the raw folder — the exporter lets you pick what's included). Check: `mods/`, `config/`, `options.txt`, `servers.dat`. Uncheck: `logs/`, `crash-reports/`, `screenshots/`, `Distant_Horizons_server_data/` (not needed — each client builds its own via the server-side streaming), and any asset/library caches — those regenerate automatically on first launch and just bloat the zip. Name the result `modpack.zip`.
+
+   **Important, learned the hard way:** Prism/Fjord's exporter zips the instance's contents (`instance.cfg`, `mmc-pack.json`, `minecraft/`, etc.) **directly at the zip root** — it does *not* wrap them in a folder named after the instance. If you just `Expand-Archive`/`unzip` that straight into `instances/`, Fjord won't recognize anything (no `instances/LANParty/instance.cfg` to find, just loose files sitting in `instances/` itself) and the instance silently never appears in the launcher. Before hosting it, open the zip and confirm the top-level entries are `LANParty/instance.cfg`, `LANParty/mmc-pack.json`, `LANParty/minecraft/...` — if instead you see `instance.cfg`/`mmc-pack.json`/`minecraft/` sitting at the root with no `LANParty/` prefix, re-zip with everything nested one level deeper under a folder literally named `LANParty` first.
 
 ## 2. The server: `mivanchenko.de` (always-on, not a box you carry to the venue)