HAARP Weather Control — Changelog

v3.2.5 — Opt-in: restrict who can control the weather

New: weatherControl permission gate (off by default)

On a multiplayer server, anyone could run /haarp <program> or /haarp cancel and change the weather for everyone — including the dramatic ones (Blood Moon, Void Storm). v3.2.5 adds an optional permission gate so admins can lock weather control to trusted players.

A self-documenting config is written to mods/haarp/haarp_config.json (under the active save) on first run:

• weatherControl: "everyone" (default — unchanged behavior) or "permission"
• controlPermission: the node to require when restricted (default haarp:control)

In "permission" mode, only senders granted the node (plus the server console/owner) can activate or cancel weather; viewing the menu, /haarp status, and /haarp help stays open to everyone. Upgrading changes nothing until an admin opts in. Mirrors the Turning Seasons v1.1.2 season-control gate.

Implementation notes

• The permission check is reflective (CommandSender.hasPermission, verified identical on Update 4 / 5 / 6) and fails closed — if the check can't run, control is denied, so a restricted server can't be bypassed.
• Denials are logged with the player name; the read-only command paths are never gated.

Compatibility & verification

• ServerVersion "*" — Update 4, 5, and 6 (pre-release). Sources compile cleanly against all three real server jars. Stub-leak scan clean; manifest.json at JAR root.