Admin Bypass

Table of contents

  1. How admin detection works
  2. Quick setup
  3. Asymmetric bypass
  4. Smurf alert routing
  5. Config reference

The admin bypass feature detects staff members and optionally excludes them from heart gain and heart loss. This prevents administrators from accidentally boosting or penalising their own heart count while testing combat, moderating, or running server events.

How admin detection works

A player is treated as an admin if any of the following is true:

  1. They have operator status and treat-ops-as-admin: true.
  2. They hold the configured permission-node (default: lifesteal.admin).
  3. Their UUID is in the allowed-uuids list.
  4. Their name (case-insensitive) is in the allowed-names list.

Detection is checked at login and cached for the session. Use /lifesteal reload after changing the allow-lists.

Quick setup

In admin.yml:

enabled: true
treat-ops-as-admin: true
permission-node: "lifesteal.admin"
allowed-uuids: []
allowed-names: []
bypass-heart-loss: true
bypass-heart-gain: true

With these defaults, any operator is exempt from both heart gain and loss.

Asymmetric bypass

You can bypass only loss (so admins test freely without getting punished) while still allowing gains:

bypass-heart-loss: true
bypass-heart-gain: false

Or bypass neither (admins play at full lifesteal risk, detection only used for smurf alert routing):

bypass-heart-loss: false
bypass-heart-gain: false

Smurf alert routing

Set restrict-smurf-alerts-to-admins: true to send smurf detection alerts only to detected admins rather than to every player holding lifesteal.alert:

restrict-smurf-alerts-to-admins: true

When false (default), all players with lifesteal.alert receive live smurf notifications regardless of admin status.

Config reference