Skip to main content
Minecraft’s vanilla .dat files only store a fraction of a player’s data. Most progression is stored across various third-party plugins. SentryWipe solves this by offering a deeply customizable hooks system via hooks.yml. SentryWipe supports three execution modes for external plugins: API, MAPPED, and RAW.

Execution Modes Explained

Recommended whenever supported. Uses SentryWipe’s internal API directly against the target plugin’s API.
  • Pros: Fastest, safest, and most stable option. Not affected by command changes, aliases, or server lag.
  • Supported Plugins: luckperms, vault, placeholderapi

Native API Hooks

These hooks are hardcoded into SentryWipe for maximum efficiency.

LuckPerms

When enabled, SentryWipe will strip the player of all parent groups, tracks, and individual permission nodes, effectively returning them to the default group.

Vault

When enabled, SentryWipe directly modifies the player’s economy balance via the Vault API (setting it to 0). This is far safer than running economy commands.

Configuring MAPPED Hooks

MAPPED hooks define a dictionary of actions.
hooks.yml
If you ever change Essentials’ base command (e.g., using essentials:delhome), you can modify it safely here without waiting for an update to SentryWipe.

Creating RAW Hooks (Custom Plugins)

RAW mode is an incredibly powerful feature. It allows you to build custom integrations for plugins SentryWipe doesn’t natively know about. We have included several raw templates for popular plugins like mcmmo, auraskills, and jobs, but you can create your own!

Example: Wiping PlayerPoints

Example: Wiping GriefPrevention Claims

Example: Wiping SentrySettings

How to Trigger Custom Hooks

Once you have defined a hook in hooks.yml (for example, griefprevention), you must add it to the actions list of your desired preset in presets.yml.
presets.yml
Now, whenever the full preset is run, SentryWipe will execute the commands defined under the griefprevention hook.

Last modified on July 18, 2026