graveyard

.gy help	send the command list back to your chat privately
.gy status	show current install id, relay connection state, and your operator tier
.gy ping	send a test packet to the relay and return the response time in ms
.gy version	print the build hash and the unique id bound to this install

.gy relay	show relay url, last successful check-in timestamp, and auth state
.gy relay flush	immediately push any queued payloads to the relay without waiting

.gy mark <player>	silently tag the player. if they ever show up on another install, you'll know who sent them
.gy scan	list every player on this server who is currently carrying a tag
.gy trace <player>	look up where a tagged player's tag originated — install id and timestamp
.gy log [n]	show the last n tag events on this install (default 20)
.gy purge <player|all>	remove tags from a player or wipe all tags recorded on this install

.gy ops	list all usernames with operator access on this install
.gy ops add <username>	grant a minecraft username access to plugin commands on this install
.gy ops remove <username>	revoke access from a username
.gy ops sync	pull the current operator list from the relay dashboard immediately

.gy reload	reload config from disk
.gy unload	detach the plugin from server memory. leaves nothing in logs or on disk

all commands are typed in chat — not as slash commands.
the chat event is cancelled before it reaches the server log or other players.
only you receive the response, sent as a private client message.

default trigger prefix: .gy — configurable per install in config.yml
access: username must be listed in the install's operator list on the dashboard