Skip to content

Plugin documentation

ExploitFixer quick start

Packet-level crash and exploit filter for Spigot, Paper, and Folia servers, built around the required HamsterAPI packet engine.

Documentation and contents

ExploitFixer inspects serverbound packets before they reach normal plugin handling. It ships 14 module files covering packet size limits, per-packet processing time, command blocking, book limits, and related crash vectors. HamsterAPI is the packet engine. PacketEvents and ProtocolLib are optional decoded-packet adapters.

Requirements

  • A Spigot, Paper, or Folia server. plugin.yml sets api-version: "1.13" and folia-supported: true. config.yml names all three as targets.
  • HamsterAPI installed and enabled. plugin.yml lists it under softdepend, but startup returns early without it. Treat it as a hard dependency.
  • HamsterAPI 0.3.5 or newer. Below that version the plugin logs a severe message but keeps starting.
  • Optional decoded-packet adapters, built against PacketEvents 2.13.0 and ProtocolLib 5.3.0. Neither library is bundled or required.
  • Java 8 build target.

Install

  1. Put the ExploitFixer jar in the server’s plugins/ directory.
  2. Put HamsterAPI in the same directory and confirm it is enabled.
  3. Deploy both on every Spigot/Paper/Folia server. The config banner reads INSTALL THE PLUGIN ON ALL SPIGOT/PAPER/FOLIA SERVERS!
  4. Start the server and check the console for the missing-HamsterAPI message below.

Configure

config.yml ships with these defaults:

PacketHooks:
  packet-events: true
  protocol-lib: true
Settings:
  locale: "en"
  web: "discord.gg/gF36AT3"
discord-webhook:
  enabled: false
  url: "https://discord.com/api/webhooks/<redacted>"
Violations:
  cancel: 25
  reduce: 20

Per-module settings live in plugins/ExploitFixer/modules/. Real defaults include max_size: 50kb and tab_complete_limit: 256 in packet-limiter.yml, plus limit-per-chunk: 32 in book-limit.yml. PacketWatchdog’s cancel-packets defaults to false. The shipped comment explains that cancelling movement packets can look to the player like an immediate disconnect. Punitive watchdog commands enforce a hard minimum of 100 VLS. notify works at any threshold.

command-blocker.yml exposes a bypass-permission string. Its default is exploitfixer.commandblocker.bypass.

Commands

Root is /exploitfixer, alias /ef.

Command Notes
/ef or /ef help Command list
/ef stats Player statistics
/ef notifications Player-only toggle
/ef reload Reload configuration
/ef config Edits user-config.yml overrides with confirmation
/ef logs [recent|most] [page] Detection registry
/ef checks Lists modules
/ef checks <enable|disable|toggle> <module> Toggles one module

Permissions

Node Default Status
exploitfixer.bypass.packetwatcher false Declared in plugin.yml
exploitfixer.admin — Checked in code; grant it explicitly
exploitfixer.notifications — Checked in code; grant it explicitly
exploitfixer.commandblocker.bypass — Module config default, not a manifest node

Do not describe exploitfixer.admin as an op-granted manifest permission. It has no default.

Troubleshooting

Symptom Cause and diagnostic
Startup aborts Console says HamsterAPI is missing or disabled. ExploitFixer cannot start. Install and enable HamsterAPI.
Severe version message HamsterAPI 0.3.5 or newer is required. Startup still continues.
Players disconnect when packets are cancelled PacketWatchdog’s cancel-packets was enabled. The default false avoids dropping movement packets from the pipeline.
Adapter appears inactive PacketHooks.packet-events or protocol-lib is false, or the library is not installed.