Commands

General /as, /alphasystem

Utility

Admin Inventory

Both edit GUIs have a "clear everything" button gated behind its own permission (alphasystem.invedit.clear / alphasystem.enderchestedit.clear) with a confirm-before-you-wipe screen — clearing can't be triggered by a misclick.

Teleport

Player preferences /settings

Every player can use these with no permission setup. Preferences are saved per player and survive restarts. The full guide, including what each toggle does and how to customise the menus, is on Player settings.

Chat

Punishments features.punish

Warn escalation

Config-driven, under warn.escalation.rules in config.yml. Each named rule independently watches for warns whose reason contains any of its keywords, counts only ones issued within its own window-days, and once a player crosses threshold, automatically applies punishment (mute/jail/ban) for duration. Add as many rules as you want — they don't interact with each other.

warn:
  duration-days: 15
  escalation:
    enabled: true
    rules:
      spam:
        keywords: ["spam"]
        threshold: 5
        window-days: 5
        punishment: mute
        duration: 24h
        reason: "Reached {threshold} spam warnings within {window} days"
      griefing:
        keywords: ["grief", "destruction"]
        threshold: 5
        window-days: 4
        punishment: jail
        duration: 24h
        reason: "Reached {threshold} griefing warnings within {window} days"
      toxicity:
        keywords: ["toxic", "racism", "racist"]
        threshold: 4
        window-days: 3
        punishment: ban
        duration: 1d
        reason: "Reached {threshold} warnings for toxicity/racism within {window} days"

Presets

Under punishment-presets.<ban|mute|jail|warn>.<key> in config.yml — each preset has its own reason and duration. Run /ban <player> <preset-key> instead of typing a reason to use one; tab-completion suggests configured preset keys as the second argument automatically.

punishment-presets:
  ban:
    hacking:
      reason: "Using hacked client / unfair advantage"
      duration: permanent
    advertising:
      reason: "Advertising another server"
      duration: 7d

Broadcast

The three broadcast commands use CMI-style flag syntax (-flag:value) mixed directly into the message text — flags are parsed out before the rest is sent as the message. -cmd/-pcmd run console/player commands when the bossbar's timer completes; -cancel:name still works as an older way to cancel.

Named visuals and cancel

• Give a visual a name with -n:name on any of the three commands. Names are not case-sensitive.
• Cancel it with cancel <name>, cancel last for the most recent one, or cancel all.
• Reusing a name replaces the earlier visual and clears it from every player who was seeing it.
• -permanent keeps it across restarts and shows it to players who join later. It needs announcements.permanent.enabled in config.yml.
• Defaults for duration, colour and fade timings come from the bossbarmsg, titlemsg and actionbarmsg sections of config.yml, and a flag on the command always wins.

/bossbarmsg all -n:restart -sec:30 -c:RED Server restarts in {time}
/bossbarmsg cancel restart

/restart in detail

Actually relaunches the server process (same java binary, JVM flags, jar/args) before shutting down — so it restarts instead of just stopping, no wrapper script needed. Disable with restart.relaunch-process: false if your host already handles restarts (or would kill the child process anyway, breaking this).

While counting down, an atmospheric storm effect runs by default: rain, fog particles drifting around each player, and lightning flashes far away and high in the sky — purely visual/audio, nothing can ever hurt anyone or set fires. See Configuration → Restart to tune or disable it.

Warps

Private warps additionally require as.warp.<name> (or as.warp.* for every private warp), granted per-warp through your permissions plugin — not registered in plugin.yml since the set of warps is dynamic. Teleports have a movement-cancellable warmup (warps.countdown-seconds); alphasystem.warp.bypasswarmup skips it. The GUI itself is fully config-driven — see Configuration → Warps GUI.

Economy Vault provider

Alpha-system registers itself as the Vault Economy provider — no separate economy plugin needed. Balances are fully cached in memory (instant responses for Vault's synchronous API) and persisted to the database on every change. Amounts accept shorthand suffixes: 1k, 2.5m, 1b, 1t.

Time & Weather

Both commands override vanilla's own built-in /time and /weather — force-claimed on server load, so Alpha-system always wins regardless of plugin load order.

Staff Tools

/maintenance in detail

• on / off — kicks every online player without bypass, and gates new joins with a configurable message. Bypass = whitelisted (add/remove) or server op.
• The server-list MOTD automatically swaps to a maintenance message while active.
• server <name> on|off and network on|off broadcast the toggle to every server sharing the same MySQL database — require database.type: mysql. Plain on/off (no target) always stays local only, network or not.
• On/off state and the whitelist persist in their own maintenance-state.yml (not config.yml), so they survive config reloads/edits. Message templates and the MOTD text live in config.yml's maintenance section — see Configuration → Maintenance.

Durations & World Targeting

Shared syntax across every command that takes a duration or targets a world.