Menú
Troubleshooting /arena commands, per-arena permissions, and debug modes
Instalar con Codex o Claude Copia este prompt, pégalo en Codex, Claude u otro asistente, y deja que revise la página de la skill y la instale por ti.
Basado en la clasificación ocupacional SOC
Troubleshooting format display, hover/click events, gradients, images in formats, and color permissions
Troubleshooting rule matching, replace vs rewrite, groups, and rule processing order
Troubleshooting channel system: messaging, range, modes, proxy, and Discord linking issues
Troubleshooting /tell, /reply, /ignore, PM formatting, social spy, and mail delivery
Troubleshooting command spy, transaction logging, and database log browsing
Troubleshooting Boss commands, PAPI placeholders, and permission issues
| name | corearena-commands |
| description | Troubleshooting /arena commands, per-arena permissions, and debug modes |
corearena.command.join.{arena} where {arena} is lowercase arena name. Users often miss that each arena has its own permission/arena start behavior depends on current state — on STOPPED: starts lobby (no player check). On LOBBY: force-starts but still needs minimum player count. Users expect it to bypass minimum requirementsDebug: [arena, next-phase], not Debug: arena. A plain string silently fails