K.L.I.E

> Hmmm, is there a reason why the switch from maven to gradle is necessary? OK, it's rollback

The real reason is that maven suddenly failed to build indexes correctly on idea, which confused me a bit, so I changed it to gradle. Maybe it's a bug in...

bukkit events not compiling and not working have been fixed, and there is now a spigot example. [Example Plugin Source](https://github.com/user-attachments/files/17266528/PlugManX-Event-Example.zip) [Example Plugin Jar](https://github.com/user-attachments/files/17266545/PlugManX-Event-Example-1.0-SNAPSHOT.zip) [PlugManX-Event Jar](https://github.com/user-attachments/files/17266531/PlugManX-Event-2.4.1.zip) 

bukkit events not compiling and not working have been fixed, and there is now a spigot example. This example has been updated to the latest commit.  [Example plugin source](https://github.com/user-attachments/files/17268340/PlugManX-Event-Example.zip)...

Let me think about what to do

Already found a solution: Veloticy added a dummy plugin named **velocity** to the plugin list, which caused serverutils to crash. You only need to filter the plugin with id **velocity**...

There is also an error in the `net/frankheijden/serverutils/velocity/reflection/RVelocityEventManager.java`, velocity **removed** their `asyncExecutor` from `VelocityEventManager`, just use Executors to build your own asyncExecutor and replace the reflection method

The fixed ServerUtils has been successfully started and runs normally on my Velocity. (latest 3.4.0 build) It's been tiring enough today, I will create a merge request the next day,...

Abandon further repairs for the following reasons: 1. Command Cloud needs to be updated. 2. Lots of code to patch 3. The Command cloud of ServerUtilsUpdater needs to be updated...