Skip to content

Technical guide

Tune ExploitFixer packet limits from /ef logs

Read /ef logs and /ef checks to find the module behind packet alerts, then tune packet-limiter limits and watchdog budgets without disconnecting players.

Products and contents

An ExploitFixer alert means one module fired for one player at one VLS. It does not mean the global packet size limit is too low. Read the log first, find the module, and keep cancel-packets at its shipped default until you can test the exact client behavior on a staging server. The ExploitFixer product page lists the modules. This guide covers how to read them.

Confirm HamsterAPI before touching config

HamsterAPI is a hard runtime requirement. The descriptor lists it under softdepend, but startup aborts with HamsterAPI is missing or disabled. ExploitFixer cannot start. and logs a severe warning if the installed version is below 0.3.5. PacketEvents and ProtocolLib are optional decoded-packet adapters, set by PacketHooks.packet-events and PacketHooks.protocol-lib.

If the plugin isn’t running, no packet limit matters yet. Fix the dependency, then go back to the logs. The install and startup steps are in the ExploitFixer docs.

Read the evidence before opening YAML

  • /ef logs recent [page] prints player, module, VLS, date and reason for recent alerts.
  • /ef logs most [page] ranks players by alert count. Use it to find a repeat offender, not a noisy module.
  • /ef notifications toggles your own alerts. Players only.
  • /ef checks lists modules and their state. /ef checks disable <module> isolates one module while you reproduce the alert.
  • /ef checks needs exploitfixer.admin, and /ef logs needs exploitfixer.logs. The code checks both, but neither is in plugin.yml. Grant them to staff explicitly. Don’t assume op-like behavior.

Module toggles live in memory only. EFModule.setEnabled flips a field and doesn’t write YAML, so a restart restores the configured value. Re-enable the module when the test ends.

Know which file owns the number

Setting File Shipped default
Violations.cancel config.yml 25 VLS
Violations.reduce config.yml 20 VLS per second
packet-limiter.max_size modules/packet-limiter.yml 50kb
packet-limiter.tab_complete_limit modules/packet-limiter.yml 256
packet-limiter.max_pps / max_bps modules/packet-limiter.yml 4096 / 60kb
packet-watchdog.vls modules/packet-watchdog.yml 25.0 per logical packet
packet-watchdog.source-window-ms modules/packet-watchdog.yml 5000
packet-watchdog.duplicate-leniency modules/packet-watchdog.yml 3 failures in 2000 ms
packet-watchdog.budgets.packet modules/packet-watchdog.yml 1000 ms

The shipped Violations block has its own warning: don’t change those numbers, and don’t remove kick, cancel or notify. At 100 VLS, the default command list already includes kick and a one-minute tempban. That escalation is why a small threshold change can cause a ban wave. Tune module budgets before you touch global escalation.

Why cancel-packets stays false

cancel-packets defaults to false for a documented reason. Cancelling movement packets such as Pos and PosRot drops them from the HamsterAPI pipeline, which looks like an instant disconnect. Turning it on turns an alert into a failure the client can see.

PacketWatchdog also enforces a hard minimum of 100 VLS for punitive commands, whatever the global Violations.commands table says. The notify command works at any threshold. Don’t use this as a way to quiet alerts.

A tuning order that does not guess

  1. Collect a normal play sample, not an attack sample. Use /ef logs most to see whether one player dominates, and /ef logs recent for the module and reason.
  2. If the reason is one item, one book or one tab request, change the narrow key first: item_limits.lore (96), book_limits.pages (50), or tab_complete_limit (256).
  3. Disable only the suspect module with /ef checks disable <module>, reproduce, then re-enable it. If the alerts stop, you’ve found the owner.
  4. Change one value, run /ef reload, and check the same log view. /ef reload needs exploitfixer.admin.
  5. Raise max_size last, and only for legitimate traffic that keeps exceeding it. Hex-colored item names are a documented false-positive source.
  6. Keep Debug.enabled off in production. Turn it on briefly when the reason string doesn’t name a packet type, then turn it off.

Frequently asked questions

Should I raise the global packet limit when one alert fires?

No. An alert means one module fired for one player. Read the log to find that module first.

Does ExploitFixer need HamsterAPI?

Yes. HamsterAPI is a hard runtime requirement. Startup aborts without it.

Should I change cancel-packets?

Keep it at the shipped default until you can test the exact client behavior.