Fixes and Improvements:
- BotShield now performs a compatibility check for Paper before establishing a connection to the backend servers.
- An internal module responsible for verifying Paper compatibility previously misidentified server cores when using Paper 1.8, which prevented BotShield from starting correctly.
- BotShield no longer utilizes the SpigotMC API for update checks. Instead, it retrieves update information directly from our backend.
- Resolved a bug within an internal module that affected on BungeeCord and Velocity servers.
NOTE:
Support for the Latency component has been disabled on versions earlier than 1.9. This change is unrelated to BungeeCord or Velocity servers. The reason is that Paper 1.8 (and its forks) lack the specific event required for the Latency component to function properly. If you are running Paper 1.8 (or its forks) with BotShield installed directly on the server (not via a proxy), the system will operate as expected, except for the Latency component.