tapscrollWIKI

Installation

Drop the jar in, assign two permissions and open the GUI — Argus is running in under five minutes.

Argus v1.1.1Paper · Purpur · Folia-safe1.21 – 1.21.x

Argus has no hard dependencies. The MySQL driver is only downloaded if you actually switch storage to MySQL, so a default install touches nothing but its own folder.

  1. Drop the jar in

    Put Argus-1.1.1.jar into your server's plugins/ folder and restart.

    BASH
    # from your local machinescp Argus-1.1.1.jar user@server:/home/mc/server/plugins/

    Restart, do not /reload

    Argus registers GUIs and listeners at startup. /reload leaves half-initialised state behind. Use a real restart after every version change.

  2. Decide who is watched

    Nothing is scored until somebody holds argus.monitored. Give it to the ranks you want to supervise, and give yourself argus.exempt so the owner never appears in the list.

    BASH
    # LuckPermslp group moderator permission set argus.monitored truelp group admin permission set argus.monitored truelp user YourName permission set argus.exempt true

    argus.admin (default op) is what lets somebody open the GUI and run the sub-commands.

  3. Open the GUI

    Run /argus in-game. You get the overview of every monitored member, sorted by threat, with their star rating rendered as custom heads.

    An empty list on day one is correct — scores only appear once monitored staff take actions Argus cares about.

  4. Arm a honeypot (optional but recommended)

    Place a chest somewhere staff can reach but players cannot, look at it and run:

    BASH
    /argus honeypot add

    Anyone monitored who opens or breaks it is flagged immediately, at the heaviest weight in the system. See Honeypots for placement that actually works.

  5. Turn on alerts

    Open plugins/Argus/config.yml and set a Discord webhook so high-threat events reach you when you are not online.

    plugins/Argus/config.yml
    alerts:  min-stars: 4  discord:    enabled: true    webhook: "https://discord.com/api/webhooks/…"

    Then /argus reload.

Verifying the install

BASH
/argus verify

This walks the audit hash chain and reports either "Audit chain intact across the sampled entries" or the exact entry number where it breaks. On a fresh install with no entries it will report intact.

Upgrading

  1. Stop the server (not /reload).
  2. Delete the old Argus-*.jar. Leaving two versions in plugins/ is the single most common cause of "the update did nothing".
  3. Drop in the new jar and start.

Your data/ folder, honeypots and audit log are preserved across versions.

New config sections after an update

Argus does not rewrite an existing config.yml. New options added in an update fall back to their built-in defaults, which is safe, but they will not be visible in your file. To see and edit them, back up the file, delete it, restart to regenerate, then reapply your settings.

Network installs

For a BungeeCord or Velocity network where scores should follow a staff member between servers:

  1. Install the jar on every backend server.
  2. Point all of them at one shared MySQL database.
  3. Give each a unique network.server-id.

Full walkthrough on the Storage & network page.