CannonRTP Commands and Permissions

CannonRTP registers its commands under the cannonrtp namespace.

• Root command: /cannonrtp
• Aliases: /crtp, /wc

/wc is the short alias most admins will use, but the underlying permission node is cannonrtp.admin for every subcommand.

Admin Commands

Command	Sender	Description
/cannonrtp	Any	Shows the help header followed by every registered subcommand the sender can use
/wc help	Any	Same as /cannonrtp -- prints the help listing
/wc create <id>	Player	Creates a brand new cannon config and places the first instance at your current location
/wc create <id> <display_name>	Player	Same as above, but sets a custom display name (underscores become spaces)
/wc place <id>	Player	Appends another placement of an existing cannon at your current location
/wc remove <id>	Player	Removes the nearest placement of <id> in your current world (config file is kept)
/wc delete <id>	Any	Deletes the cannon's config file outright
/wc target <id> <world>	Player	Changes the cannon's target landing world
/wc center <id>	Player	Sets the cannon's search center to your current location
/wc list	Any	Lists every placement with display name, status, queue size, and last status detail
/wc status	Any	Same output as /wc list
/wc probe	Player	Tests whether your current location would pass all enabled protection checks
/wc reload	Any	Reloads global config, every per-cannon config, tasks, and protection adapters
/wc setup	Player	Opens the Nightbreak-style content browser menu (lists installed and downloadable cannon packages)
/wc downloadall	Any	Downloads every available CannonRTP content package from Nightbreak
/wc updatecontent	Any	Downloads updates for outdated CannonRTP content packages (alias: /wc updateall)

CannonRTP does not ship a separate first-time /wc initialize menu -- it has no preset modes. The first time an admin joins after install, a Nightbreak chat warning prompts them to run /wc setup.

All admin commands require cannonrtp.admin.

See the Content Packages page for details on what /wc setup, /wc downloadall, and /wc updatecontent actually manage.

create vs place vs remove vs delete

One cannon config (plugins/CannonRTP/cannons/<id>.yml) can drive many in-world placements. create makes the config and seeds the first placement. place appends another placement to an existing config. remove deletes one placement (the closest one to you in your world) but keeps the config. delete deletes the config file outright, removing every placement.

Player Interaction

There is no player command to activate a cannon. Players use CannonRTP by walking into the cannon's trigger radius (triggerRadius, default 1.75 blocks).

Permissions

Only two permission nodes are registered in plugin.yml:

Permission	Default	Description
cannonrtp.admin	op	Required for every admin subcommand
cannonrtp.use	true	Required before a player can trigger any cannon

How cannonrtp.use works

If a player lacks cannonrtp.use, the cannon silently ignores that player. No denial message is sent for this base permission check -- they simply walk through the cannon area without launching.

Per-Cannon Permission Gate

Each cannon config can also define a requiredPermission field.

• If requiredPermission is blank (the default), the cannon only checks cannonrtp.use.
• If requiredPermission is set and the player has cannonrtp.use but lacks the per-cannon node, CannonRTP sends the configured noPermission message including the cannon's display name. The message is throttled to once every three seconds per player per cannon.

Tab Completion

Commands that take a cannon <id> argument tab-complete from the list of known cannon config ids. Commands that take a <world> argument tab-complete from the list of currently loaded world names.