FAQ

A one-command health report covering:

• Database connectivity
• Vault economy provider registration
• PlaceholderAPI and LuckPerms presence
• Network sync mode (sqlite/h2 = disabled, mysql = enabled)
• Discord webhook and reports webhook configuration
• Current maintenance state
• bStats status and update-checker status

It doesn't check WorldGuard directly — run /region setspawn once to confirm that integration is actually working.

No. It re-reads config/message/arena/kit/shop files. Java is compiled once at server start — any change to the plugin's actual code requires a full server restart.

You almost certainly ran /region from the wrong world. The plugin remembers whichever world you were standing in when you ran the command, and only searches that world for the named region. If your arena/spawn regions live in a dedicated world (e.g. arena_test), teleport into that world first, then run /region setspawn/setarena.

Check three things: regen.enabled: true in arena.yml, that /region setarena was actually run (which also takes the snapshot regen restores to), and that enough time has passed for regen.interval. You can always force one immediately with /region regen rather than waiting.

Spawn protection (no building, no PvP) only applies inside the spawn region — the arena is deliberately a free-build PvP zone that gets periodically wiped by regen instead. If you want a no-build arena, use WorldGuard's own flags on that region directly; alphawildsystem.build.bypass is the only plugin-side override, meant for staff.

Check the player's inventory has room — the shop has overflow protection and won't take payment for an item that can't actually be delivered. Confirm the item's price in shop.yml is what you expect; prices and contents are read fresh every time the menu opens, so a typo shows up immediately on the next /shop open, no reload needed.

That's this plugin's specific branding — a kit-PvP server's currency earned from kills rather than a general-purpose economy. Change currency.name-singular/.name-plural and format in economy.yml to rename it to anything else; the underlying Vault balance behavior doesn't change.

Expected — combat tag blocks every command except combat.allowed-commands (msg/reply by default) for combat.combat-seconds after the last hit landed. Add more commands to the allowlist in config.yml if your server needs it, or grant alphawildsystem.combat.bypass to staff who need to intervene mid-fight.

Check combat.kill-reward-ruby isn't set to 0 — that's the per-kill Vault credit, separate from the one-time milestone tiers claimed through /killrewards, which track the player's lifetime player_kills statistic instead.

Confirm chat.format-normal: true — if another plugin (TAB, etc.) has been set to own chat formatting instead, the gradient never gets a chance to apply. Also double-check the color option is still enabled/present in chatcolors.yml after any edits.

You're almost certainly on an offline-mode server without PacketEvents installed — install it (soft-depend, no config needed) for full fidelity. See Integrations → Chat deletion.

Confirm Vault is installed — the plugin only registers as the economy provider when it detects Vault on startup. /awild diagnostics shows the current registration status.

Run /awild reload (or restart). Every file except config.yml's simple scalars has no bundled-default layering, and none of them hot-apply on save — they only take effect after a reload re-reads them from disk.