Your cart is empty
Looks like the spiders padded through here. Pick a plugin and it will show up here. Continue shoppingDoctor & Dashboard
Check the health of a Phoenix plugin for a support ticket, and connect a server to the web dashboard.
On this page
This page covers Phoenix Crates, Phoenix Duels, Phoenix Lobby and Phoenix Shop. Both features are admin commands.
#Doctor
The doctor checks the plugin and prints one screen. Each line is marked OK, WARN or FAIL with a short fix underneath. Phoenix Lobby and Phoenix Shop write PASS instead of OK. WARN is something worth fixing, FAIL is something that is broken.
| Command | Permission |
|---|---|
| /crates doctor | phoenixcrates.command.doctor |
| /pduels doctor | phoenixduels.admin |
| /plobby doctor | phoenixlobby.admin |
| /pshop doctor | phoenixshop.admin |
#What It Checks
Every plugin checks these:
| Line | What it checks |
|---|---|
| License | Valid, running on the saved license while our servers can't be reached and for how long, or not loaded and why. A free jar has no license to check. |
| Server | The server software and version, Folia, Java and the players online. |
| Database | The database type, and how long it takes to answer. A slow answer is a WARN, no answer a FAIL. |
| Add-ons | The loaded add-ons, and the ones that did not start. |
Each plugin adds checks of its own:
| Plugin | Extra checks |
|---|---|
| Phoenix Crates | Version, broken rewards, crates placed in worlds that are not loaded or of types that no longer exist, add-ons older than the ones that ship with the plugin, hooks, keys waiting to be delivered. See Health Check. |
| Phoenix Duels | Version, Bedrock support, arenas and maps, modes without arenas, kits, queues, hooks and WorldEdit. |
| Phoenix Lobby | Modules, the proxy link, the servers your menus point to, the lobby spawn, hooks and broken config files. |
| Phoenix Shop | Bedrock support, currencies, broken config files, shop items with a bad material or price, chest shops in missing worlds or without a container, the auction house. |
#Sending the Report to Support
Crates and Duels also save the report as a text file in the plugin folder with doctor file, ready to attach to a support ticket:
| Command |
|---|
| /crates doctor file |
| /pduels doctor file |
Phoenix Lobby and Phoenix Shop have no file option. Copy the lines from the console instead. The Crates report never contains your license key, database password or address.
#Server Dashboard
The web dashboard shows what happens on your server on phoenixplugins.com: activity, counts and the current setup of the plugin. It is on by default and talks to api.phoenixplugins.com, so the server needs outbound HTTPS access. A server is not tied to your account until you link it.
#Linking a Server
Run the link command. The plugin prints a link and a code that expire after a few minutes. In chat the link is clickable. Open it while logged in to your account to connect the server.
| Command | Permission |
|---|---|
| /crates dashboard link | phoenixcrates.command.dashboard |
| /pduels dashboard link | phoenixduels.admin |
| /plobby dashboard link | phoenixlobby.admin |
Without link, the command shows the connection status: whether the server is registered with the dashboard, when data was last sent, how many events are waiting to be sent and the last error. If the dashboard is switched off, the command says so.
#What It Sends
Every plugin sends the same server details about once a minute:
- The plugin, its edition and version, and your license key if the jar has one.
- The server software, server version and Minecraft version.
- The players online and the maximum.
- The names of the installed add-ons.
On top of that, each plugin sends its own activity. Player names and UUIDs are part of it, which the console also says when the dashboard starts.
| Plugin | Activity | Overview of the setup |
|---|---|---|
| Phoenix Crates | Crates opened, keys given, rewards won, rare rewards that are broadcast. | Every crate with its rewards, weights and linked keys, and every key. |
| Phoenix Duels | Matches that ended with the players, results, kills, deaths and elo changes, deaths in FFA, players joining a queue. | Modes, maps and the queues. |
| Phoenix Lobby | Players joining and leaving, server transfers, queue requests, menus opened. | The servers on your network with their players, when the proxy is linked. |
Events that cannot be sent are kept on disk and sent later, for up to 30 days.
web-dashboard.enabled in config.yml turns the dashboard off for that plugin.