WhisperControl

WhisperControl — whisper the bot to protect, come, go, patrol, mine

🧪 Beta preview — ships in 5.3 (Java beta channel). WhisperControl is part of the 5.x beta line and is off by default; it is not yet in the stable 4.1.0 release. To try it, run the beta channel (see Installation). The protect and goto verbs below are new in 5.3.

WhisperControl lets authorized players whisper the bot plain verbs and it acts — no Discord, no terminal, no command prefix. It doesn't re-implement movement or combat; it wires together modules the proxy already has (the Baritone pathfinder, KillAura, ElytraPilot, SpawnPatrol, AquariusMiner).

Command: whispercontrol (alias wc). It's a module — enable it with wc on.

Verbs

Whisper these to the bot in-game (e.g. /w <botname> protect):

Verb	What it does
protect	New in 5.3. Guard you — leash nearby, scan a 32-block sphere around you for hostile mobs and path to the nearest to kill it, and swap a worn elytra for a chestplate in combat range.
come	Come to you — walk if within comeFlyThreshold (default 200) blocks, else fly there. Accepts coords: come <x> <z> / come <x> <y> <z>.
goto <x> <y> <z>	New in 5.3. Go to exact coordinates. The coordinates never travel over Minecraft chat — see below.
patrol	Patrol a preset area (set with wc patrol … or the Discord panel).
mine	Mine a preset box (set with wc mine … or the panel) — drives AquariusMiner.
stop	Halt protect / patrol / mine / come and restore the elytra.
help	Whisper back the verb list.

protect (new in 5.3)

protect replaces the old follow verb. While protecting you, the bot:

• Leashes within followRadius blocks of you (default 32).
• Constantly scans that 32-block sphere around you for hostile mobs (~twice a second) and paths to the nearest so KillAura kills it; when the area is clear it leashes back to you.
• Swaps your elytra for the best inventory chestplate the moment it's in combat range — but keeps the elytra on while it's still travelling to you, so it never grounds itself mid-trip. The elytra is restored when you stop.
• Enables KillAura by default.

Tuning:

wc followradius <blocks>     # protect leash + hostile-scan radius (default 32)
wc killaura <on/off>         # whether protect also enables KillAura (default on)
wc chestplateswap <on/off>   # whether protect swaps elytra → chestplate in combat (default on)

⚠️ If you run protect with KillAura's targetPlayers setting on, whitelist the protected player — protect only forces hostile-mob targeting, it doesn't touch player targeting, so without a whitelist the bot could swing at you.

goto — coordinates that never hit chat (new in 5.3)

goto <x> <y> <z> sends the bot to exact coordinates. Coordinates are sensitive (often a base), so WhisperControl is built so they never travel over any Minecraft chat — public, whisper, or otherwise — when you drive it through the ProxyBridge companion mod:

• /pb goto <x> <y> <z> (in the mod) sends the destination to the bot over its HTTP API only. If you haven't registered a bot with an API token, it refuses rather than fall back to chat — so the coordinates can't leak.
• If you type the habitual /w <bot> goto <x> <y> <z> instead, the mod captures it before it leaves your client and reroutes it over the API (or blocks it outright if there's no API). Either way the in-game whisper is cancelled.
• On the bot side, the proxy's goto replies never echo the coordinates.

Without the mod, goto still works as a plain whisper verb (and wc goto <x> <y> <z> works from the terminal / Discord / HTTP API) — but only the mod gives you the off-chat guarantee. Like come, goto walks within comeFlyThreshold blocks and flies beyond it.

come, patrol, mine

• come brings the bot to you. Within render distance it uses your live position; out of range it can use a position your client reports over the API (see Cross-session position below), or you can pass coords.
• patrol / mine run against presets you set first:

wc patrol <x> <y> <z> <range>
wc mine <x1> <z1> <x2> <z2> <minY> <maxY>
wc panel                       # post an interactive setup panel to Discord

Authorization

WhisperControl is gated:

• RBAC enabled (perms enable on): each verb needs module.whispercontrol plus the underlying capability — module.killaura for protect, module.pathfinder for come/goto, module.spawnpatrol for patrol, module.aquariusminer for mine.
• RBAC disabled (default): only the account owner may command the bot.

Cross-session position (come / protect out of render)

A bot only sees players in its loaded chunks, so come/protect can target you from far away only if your client reports its position out-of-band. The ProxyBridge mod does this with /pb reportpos on, which POSTs your location to the bot's HTTP API (POST /position). It is off by default (it shares your location with the bot's owner). Reported positions are used to route toward you until you come into the bot's view, at which point it switches to tracking you directly.

Quick start

1. wc on — enable the handler.
2. Authorize: keep RBAC off to stay owner-only, or perms enable on and grant a member module.whispercontrol plus the verb perms.
3. For off-chat goto / out-of-range come: perms api on, perms token issue <member>, and have them run the ProxyBridge mod (/pb bots add …, then /pb goto, /pb reportpos on). Expose the API safely — keep it on localhost or behind a firewall/VPN, never open on 0.0.0.0.
4. Whisper the bot: protect, come, goto …, patrol, mine, stop.

Commands

wc on/off
wc followradius <blocks>          # protect leash + hostile-scan radius (default 32)
wc comethreshold <blocks>         # come/goto walk within this, fly beyond it (default 200)
wc killaura <on/off>              # protect also enables KillAura (default on)
wc chestplateswap <on/off>        # protect swaps elytra → chestplate in combat (default on)
wc goto <x> <y> <z>               # send the bot to coords (the off-chat path the mod uses)
wc patrol <x> <y> <z> <range>     # set the patrol preset
wc mine <x1> <z1> <x2> <z2> <minY> <maxY>   # set the mine preset
wc panel                          # post the Discord control panel