FAQ

A one-command health report covering:

• Database connectivity — a live connection check, run off the main thread
• Vault economy provider registration
• PlaceholderAPI presence
• LuckPerms presence
• Network sync mode (sqlite/h2 = disabled, mysql = enabled)
• Discord webhook configured?
• Reports webhook configured?
• Current maintenance state
• bStats status (and whether a real plugin-id is set)
• Update-checker status (up to date / update available / disabled)

Run it right after installing, and again after changing any integration config, to confirm everything actually connected instead of just assuming it did.

No. /as reload only re-reads YAML config/message files. Java is compiled once at server start and can't be swapped out from under a running process — any change to the plugin's actual code requires a full server restart.

By design — the world/duration arguments on /time and every day/night preset are entirely optional and additive. Calling a preset with zero arguments (e.g. plain /day) uses the sender's current world and leaves the daylight-cycle gamerule untouched, identical to the command's original behavior before multi-world/duration support existed.

/ban bans one account. /banip bans that account and blocks the IP address it was last seen on — any other account (an alt, a fresh account) connecting from that same address gets turned away too, with a kick screen naming the originally banned account. Both create the same kind of ban entry under the hood, so /banhistory, /checkban, and /unban all work identically for either.

No — /ban-ip is registered as an alias that routes to the exact same command, and is force-claimed on server start so it always wins over vanilla Minecraft's own built-in /ban-ip (which would otherwise write to a separate banned-ips.json file completely outside this plugin's punishment system).

Check warn.escalation.rules in config.yml. Each rule watches warns whose reason text contains specific keywords, and once a player crosses a threshold within a time window, automatically applies a punishment. If this is surprising, either the reason text is matching a keyword you didn't expect, or a rule's threshold is lower than intended — see Commands → Warn escalation for the exact config shape.

You're almost certainly on an offline-mode server without PacketEvents installed. Signed (secure-chat) messages always delete perfectly with Minecraft's real delete packet. Unsigned messages are simulated by redrawing chat — without PacketEvents, only Alpha-system's own tracked messages survive that redraw, so anything another plugin broadcast during that same moment won't reappear. Install PacketEvents (soft-depend, no config needed) for full fidelity — see Integrations → Chat deletion.

No, in either mode. With PacketEvents, replay is sourced from each viewer's own real packet history — a private message was only ever sent to its two participants, so it can only ever be replayed back to them. Without PacketEvents, private messages are tracked with an explicit per-viewer visibility list rather than a permission node, which has the same guarantee.

No — sqlite is the zero-config default and is all you need for a single server. MySQL is only required if you want cross-server punishment sync and network-wide /maintenance across multiple servers sharing one database.

Run /as diagnostics to confirm the database actually connected — a typo in host/port/credentials will silently leave the plugin unable to reach MySQL, and network features stay disabled until it does. Also confirm every server in the network points at the exact same database (host + database name), not separate databases of the same name on different hosts.

Confirm Vault itself is installed — Alpha-system only registers as the economy provider when it detects Vault on startup, and does nothing silently if Vault is missing. /as diagnostics shows the current registration status directly.

Requires both PlaceholderAPI and LuckPerms installed — Alpha-system reads %luckperms_prefix%/%luckperms_suffix% through PlaceholderAPI rather than depending on LuckPerms directly. Missing either one, the placeholders silently resolve to an empty string instead of erroring.

Run /as reload (or restart). Unlike config.yml, message files have no bundled-default layering — but they still only take effect after a reload re-reads the file from disk, they don't hot-apply on save.