If you have a plugin that is misbehaving and altering events on your server, this plugin can help you figure out which plugin is causing the issue. Simply edit the configuration file to target the events and methods you want to track, and the plugin will log information about which events were cancelled and by which plugin.
To use the plugin, you'll need to find the event class you want to track. You can do this by going to
https://hub.spigotmc.org/javadocs/spigot/ and navigating to the location of the event. For example, the
PlayerInteractEvent will be located in the
org.bukkit.event.player package.
Once you've found the event class, copy the fully qualified class name (e.g.
org.bukkit.event.player.PlayerInteractEvent) and add it to the plugin's configuration file, along with the methods you want to track (e.g.
isCancelled). An example configuration for tracking the
PlayerInteractEvent and the
isCancelled method would look like this:
Code (YAML):
exact:
InteractEvent:
class
:
"org.bukkit.event.player.PlayerInteractEvent"
methods
:
-
"isCancelled"
Note that the InteractEvent key can be named anything, but it's used to identify the event in the plugin's internal tracking.
In addition to tracking specific events and methods, the plugin also includes an option to track all cancellable events. To enable this feature, set the listen-to-all-cancellable option in the other section of the configuration file to true.
Once you've configured the plugin, save the configuration file and restart or reload the server to start tracking events. The plugin will log information about cancelled events, including the name of the plugin that cancelled the event.
It's important to note that this plugin is intended for debugging purposes only. If you don't need to track events and their cancellations, you don't need to download or use this plugin.
If you have any questions or need assistance, you can contact me at
[email protected].