IndexOutOfBounds after leaving server on overnight

[redstonerti]

Stacktrace

https://pastebin.com/LqwifuM6

Actions to reproduce

giorkos@4.0.0-RC14-5f2027a1 => service list
[04.09 19:44:53.078] INFO : | Name          | Lifecycle | Address           | Node   | State
[04.09 19:44:53.078] INFO : _____________________________________________________________________
[04.09 19:44:53.079] INFO : | lobby-1       | RUNNING   | 192.168.1.3:44955 | Node-1 | Connected
[04.09 19:44:53.079] INFO : | maintenance-1 | RUNNING   | 192.168.1.3:44959 | Node-1 | Connected
[04.09 19:44:53.079] INFO : | parkour-1     | RUNNING   | 192.168.1.3:44958 | Node-1 | Connected
[04.09 19:44:53.079] INFO : | proxy-1       | RUNNING   | 192.168.1.3:25565 | Node-1 | Connected
[04.09 19:44:53.079] INFO : | skyblock-1    | RUNNING   | 192.168.1.3:44957 | Node-1 | Connected
[04.09 19:44:53.079] INFO : | survival-1    | RUNNING   | 192.168.1.3:44956 | Node-1 | Connected
[04.09 19:44:53.079] INFO : => Showing 6 service(s)
giorkos@4.0.0-RC14-5f2027a1 =>

I have 6 paper 1.21.8 servers running and one velocity proxy on an arch linux server. There were no players online, the only module installed is the Bridge module. I came back to a tmux screen full of OutOfBoundsErrors.

CloudNet version

giorkos@4.0.0-RC14-5f2027a1 => me
[04.09 19:46:52.379] INFO :
[04.09 19:46:52.380] INFO : CloudNet Blizzard 4.0.0-RC14 5f2027a
[04.09 19:46:52.380] INFO : Discord: https://discord.cloudnetservice.eu/
[04.09 19:46:52.380] INFO :
[04.09 19:46:52.380] INFO : ClusterId: 2cdbfd25--4d55--f1ba5de8ffcd
[04.09 19:46:52.380] INFO : NodeId: Node-1
[04.09 19:46:52.380] INFO : Head-NodeId: Node-1
[04.09 19:46:52.380] INFO : CPU usage: (P/S) .24/1.54/100%
[04.09 19:46:52.381] INFO : Node services memory allocation (U/R/M): 24576/24576/61440 MB
[04.09 19:46:52.381] INFO : Threads: 40
[04.09 19:46:52.381] INFO : Heap usage: 66/256MB
[04.09 19:46:52.381] INFO : JVM: Oracle Corporation 24 (Java HotSpot(TM) 64-Bit Server VM 24.0.1+9-30)
[04.09 19:46:52.381] INFO : Update Repo: CloudNetService/launchermeta, Update Branch: beta
[04.09 19:46:52.381] INFO :

Other

No response

Issue uniqueness

• Yes, this issue is unique. There are no similar issues.