Reference

Commands

ExyliaProxyUtils registers no commands of its own; how the player-proxy: and console-proxy: prefixes run proxy commands from any Exylia plugin.

ExyliaProxyUtils registers no commands. Nothing is typed on the proxy to use it, and there is no reload: changes to config.properties apply on the next restart.

What it adds is the other way round: commands on the proxy, run from the backends.

Running proxy commands from a backend

Every Exylia plugin that runs command lists — rewards, menu actions, event prizes, punishment steps — accepts two prefixes that ExyliaLib sends to the proxy's commands module:

Prefix	Runs as	Example
`player-proxy:`	The player the line is about, with their permissions on the proxy.	`player-proxy:server lobby`
`console-proxy:`	The proxy console, logged with the server that sent it.	`console-proxy:alert Restarting in 5 minutes`

actions:
  - "player-proxy:server hub"
  - "console-proxy:send Steve minigames"

A leading / is optional: player-proxy:/server lobby works too.
The prefix is case-insensitive; the command is passed as it is.
player-proxy: needs a player. On a line run for nobody (a console reward, a schedule), it is refused.
A command the proxy does not have is refused with the proxy did not run "/<label>", which the backend logs, so a typo in a YAML file shows in the console instead of failing silently.

console-proxy: is root on the proxy

Anything that can put a line in a backend's configuration, or publish on the network's Redis, can run console commands on the proxy. Keep Redis on a private network with a password, and treat backend configuration as proxy-level access.

The commands your plugins add

Commands that reach across the network belong to the plugins on the backends and are documented there: ExyliaStaff's /tp and /staffadmin import, ExyliaSurvivalCore's cross-server TPA and /back, and ExyliaLib's /exylialib status, which shows whether the proxy is answering.

Something missing on this page? Tell us on Discord