Pin lazymc to v0.2.10, fixing it never detecting Forge as ready

v0.2.11 has a confirmed open regression (timvisee/lazymc#65, #86):
it never recognizes a Forge server as online regardless of uptime,
so every connection just times out on the "still starting" screen
forever. forge=true alone doesn't fix it. 0.2.10 correctly detects
readiness (verified: "Server is now online" + successful relay).

server/setup-server.sh

@@ -67,13 +67,13 @@ mkdir -p "$SERVER_DIR/mods"
 echo "==> NOTE: copy the same mod jars from your client modpack's mods/ folder into $SERVER_DIR/mods/ (Create, Flywheel, Farmer's Delight + addons, JEI, etc.) before first boot."
 
 # ---- 2. Install lazymc ----
+# Pinned to v0.2.10, NOT "latest" — v0.2.11 has a confirmed, still-open upstream
+# regression where it never detects a Forge server as ready (timvisee/lazymc#65,
+# #86). 0.2.10 was the last version that correctly detects Forge startup.
+LAZYMC_VERSION="v0.2.10"
 if [[ ! -x "$BASE_DIR/lazymc" ]]; then
-  echo "==> Downloading latest lazymc"
-  api_url="https://api.github.com/repos/timvisee/lazymc/releases/latest"
-  release_json="$(curl -fsSL "$api_url")"
-  asset_url="$(echo "$release_json" | grep -oE '"browser_download_url": *"[^"]+linux-x64"' | cut -d'"' -f4 | head -n1)"
-  [[ -n "$asset_url" ]] || { echo "Could not find linux-x64 lazymc asset" >&2; exit 1; }
-  curl -fsSL -o "$BASE_DIR/lazymc" "$asset_url"
+  echo "==> Downloading lazymc $LAZYMC_VERSION"
+  curl -fsSL -o "$BASE_DIR/lazymc" "https://github.com/timvisee/lazymc/releases/download/${LAZYMC_VERSION}/lazymc-${LAZYMC_VERSION}-linux-x64"
   chmod +x "$BASE_DIR/lazymc"
 else
   echo "==> lazymc already present, skipping"