Java Instrumentation API not working

Stacktrace

Paste your paste link or the raw stack trace here. DO NOT REMOVE THE BACKTICKS!

Actions to reproduce

Run a PandaSpigot instance

CloudNet version

10.12 22:43:43.212] COMMAND: CloudNet Earthquake 3.4.5-RELEASE-0f8f0d7 by Dytanic & the CloudNet Community [10.12 22:43:43.212] COMMAND: Discord: https://discord.cloudnetservice.eu/ [10.12 22:43:43.213] COMMAND:
[10.12 22:43:43.213] COMMAND: ClusterId: 5b5b34f2-7f15-427b-93ae-def50bcfad75 [10.12 22:43:43.213] COMMAND: NodeId: Node-1 [10.12 22:43:43.213] COMMAND: Head-NodeId: Node-1 [10.12 22:43:43.214] COMMAND: CPU usage: (P/S) 100/0/100% [10.12 22:43:43.214] COMMAND: Node services memory allocation (U/R/M): 768/768/13953 MB [10.12 22:43:43.214] COMMAND: Threads: 35 [10.12 22:43:43.215] COMMAND: Heap usage: 39/456MB [10.12 22:43:43.215] COMMAND: Loaded classes: 6005 [10.12 22:43:43.215] COMMAND: Unloaded classes: 0 [10.12 22:43:43.215] COMMAND: Total loaded classes: 6005

Other

One of my clients reported a issue about our server software unable to start on CloudNet, we use the Java Instrumentation API and it looks like it's not being initialized, it's failing on the null check. What we should do in order to fix this? Screenshot from 2023-12-10 17-32-09 (EDIT: Seems to happen with PandaSpigot aswell)

Issue uniqueness

[X] Yes, this issue is unique. There are no similar issues.

CloudNetService / CloudNet