Exception in a plugin's event handler (Could not pass event)
- Platforms
- Paper · Purpur · single server
- Verified
- Verified
- Confidence
- Confidence 85%
What it looks like in the log
Any one of these lines is enough. The agent matches them locally, on your server.
logs/latest.log
[ERROR] Could not pass event
Symptoms
- A plugin feature that reacts to player actions (clicks, joining, chat) does not trigger
- In the log: “Could not pass event <Event> to <plugin> vX” and a stack trace
Cause
A plugin's event handler (listener) threw an exception. Paper keeps running, but the plugin's action for that event was not carried out.
Possible causes
- A plugin bug (NullPointerException and the like in its classes)
- The plugin accesses a disabled plugin or an unavailable resource
- Incompatibility with the server version, or a conflict with another plugin that modifies the same event
How to fixLow risk
- Use the evidence to identify the event (the name after
Could not pass event) and the plugin (afterto); the exception is on the next line and inCaused by:. - If the trace points to a disabled plugin or the database, deal with that cause first (errors earlier in the log).
- Update the plugin; in case of a conflict, temporarily disable the plugins listening to the same event one at a time to find the culprit.
- Report it to the plugin author with the full trace and versions if the error reproduces on the latest version.
Translated from the Russian original; log lines are quoted verbatim.