Three command surfaces

WN Discord exposes the same functionality across three distinct surfaces:

Permission-gate vocabulary

These terms recur through every table below.

! text commands

A ! text command is not a separate, independently-implemented command set. Every ! command is the exact same command object registered for the / surface, driven through a text-interaction adapter instead of a real Discord interaction. Argument parsing, subcommand resolution, and every permission gate run identically for both surfaces. The only two things that differ between ! and / for a given command are reply visibility (see above), and hubOnly enforcement: a hubOnly command is never published as a slash command to a nation's own linked Discord server, but ! dispatch is guild-agnostic by design, so the dispatcher re-checks hubOnly itself and silently treats the message as unrecognized (falls through to chat relay) if typed outside the hub guild.

Every top-level namespace below is reachable via !, subject to the hubOnly rule.

/nation, act on and look up a nation

Permission: everyone (not adminOnly, not hubOnly). Every subcommand but info/activity checks the invoker's linked Minecraft account inline and prompts to link if absent. invite, kick, create, leave, and disband call the API directly and work even while offline; everything else bridges through a real in-game command execution and needs the linked player online.

Examples

/nation info name:Ironhold
/nation invite player:Steve
/nation accept nation:Ironhold
!nation info Ironhold
!nation invite Steve

/nation-settings, configure your nation's settings, home, and applicants

Permission: everyone; every subcommand bridges to a real in-game command, so every one needs a linked account and the player online. Split from /nation purely because of Discord's 25-subcommand cap.

/nations, browse, rank and compare every nation

Permission: everyone, fully public and read-only; every subcommand reads the Warring Nations API directly, no account link or online player needed at all.

/diplomacy, manage your nation's alliances and enemies

Permission: everyone; every subcommand bridges in-game (link + online required).

/war, declaring, tracking, rallying, and (staff) resolving wars

Permission: the parent is not adminOnly, a public namespace. approve/deny are the one exception: each has its own inline admin check (still visible to everyone in Discord's picker, but refused at runtime for non-staff). See war presets for the mechanics these commands act on.

Examples

/war declare nation:Ashenreach
/war status
/war propose-peace nation:Ashenreach
!war declare Ashenreach
!war stats Steve

/account, your Discord to Minecraft identity

Permission: everyone. link/unlink are only registered when account linking is enabled server-side; whoami/whois always register (read-only). None uses a dispatcher-level requireLink flag, each checks the invoker's link status inline itself so /account link keeps working for someone with no link yet.

/server, live server status

Permission: everyone, fully public.

/help, command reference / man page

Permission: everyone. Backed by two non-command interaction handlers (not directly invocable): a category-select handler and a Prev/Next pagination button handler for command lists too long for one page.

/bets, pari-mutuel betting on active wars

Permission: everyone (no adminOnly, no hubOnly).

/dashboard, live navigable dashboards

Permission: everyone; the top-level command is built with publicReply(true) - replies here post visibly to the channel, not ephemerally, because these are meant as shared multi-user surfaces.

The dashboards' interactive buttons/modals gate independently of the slash command itself. Navigation and tab selects need no permission. Propose peace/terms and Declare war need a linked account and the DECLARE_WAR nation permission for one of the warring nations (Declare war works offline). Propose alliance / Create bloc / Invite to bloc need a linked, online account with MANAGE_DIPLOMACY. Adjust treasury is Discord staff only (invokerIsAdmin(), re-checked at modal submit, logged to the op-audit-log channel) - across /bets, /dashboard, and /gov combined, this is the only Discord-staff gate; everything else in these three namespaces is gated on Minecraft-side account linkage and delegable in-game nation permissions. Appoint role needs MANAGE_ROLES, online; Appoint governor needs MANAGE_SETTINGS, online.

/gov, nation government entities, roles, and proposals

Permission: everyone (deliberately not adminOnly, since that would also force hubOnly and break usage on a nation's own server). Mutating actions gate on the same delegable in-game MANAGE_GOVERNMENT_PERMISSION nation permission.

Examples

/gov entities nation:Ironhold
/gov create-entity nation:Ironhold kind:council name:High Council
/gov grant id:4f2e8b91-6a3d-4c7e-9b1a-2d5f8e0c1a7b role:Councilor player:Steve
/gov vote id:4f2e8b91-6a3d-4c7e-9b1a-2d5f8e0c1a7b choice:yes

/whitelist, server access control

Permission: adminOnly + hubOnly (explicit) at the top level, staff-only, hub guild only.

/staff, staff-only intel and operations

Permission: adminOnly + hubOnly (explicit) at the top level. Dashboard/bridged subcommands additionally require the staff member be online and actually op'd in-game - Discord's adminOnly only controls Discord-side visibility, the in-game bridge re-checks separately.

/config, view and change wndiscord's settings live

Permission: adminOnly + hubOnly (explicit) at the top level, every subcommand inherits this, none has an additional inline check.

/setup, guided walkthrough for configuring the bridge

Permission: adminOnly + hubOnly (explicit).

/debug, diagnostic snapshots of the bridge, mods and server

Permission: adminOnly + hubOnly + ownerDiagnostic bypass (explicit) - the mod author's own Discord ID can run these even without staff permissions, defensible because every one of the 11 subcommands is strictly read-only.

/nationserver, manage this nation's own linked Discord server

Registered only when per-nation-servers is enabled server-side. Permission: adminOnly with an explicit hubOnly(false) - the one command that opts out of the adminOnly-to-hubOnly default, because its whole purpose is running inside a nation's own server, where "admin" means that nation's in-game leader/co-leader, not Discord staff. Every subcommand additionally re-checks at runtime that the invoking guild is actually a linked nation server; otherwise it no-ops with an error.

In-game /discord commands

A completely separate command surface: a Minecraft command tree rooted at /discord, registered in-game (not through Discord at all). Three subcommands (reload, debug, config) are gated through this mod's own permission-node catalogue: nodes wndiscord.reload, wndiscord.debug, wndiscord.config, each defaulting to vanilla op level 2 with no permission plugin installed. A server running a permission plugin (LuckPerms, etc.) via NeoForge's permission API can grant or restrict each node independently, e.g. delegating /discord debug to a helper without also granting /discord config.

list, get, set under config, and nationserver's three children, carry no individual permission requirement of their own - they inherit the parent literal's permission predicate (for config) or have none at all beyond the in-handler leader/co-leader check (for nationserver).

Command counts

Verified against source.