You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This is happening on a wide scale - I have noticed that the exact time down to the millisecond where players VIP flags are added, they are also kicked by this plugin. It appears to be a bug within the kick immunity logic - I have switched from one VIP system to another, and this is still happening.
2024-10-27 19:35:51.697 +00:00 [INFO] plugin:[VIP] Core Player 'Insurv [45xxxxxxx]' VIP information has been successfully updated 2024-10-27 19:35:51.697 +00:00 [INFO] plugin:Reserved Slots Player Insurv (765611xxxxxxxxxx) was kicked, because player with a reservation slot joined.
This has happened again, using latest version (still shows as v1.1.0 in the console btw). I will say this is the first time it has happened in 6 days though!
2024-11-02 22:19:52.519 +00:00 [INFO] plugin: [VIP] Core Checking feature: flags - [ "@css/vip" ]
2024-11-02 22:19:52.988 +00:00 [INFO] plugin: [VIP] Core Player 'Foul Play [60212659]' VIP information has been successfully updated
2024-11-02 22:19:52.988 +00:00 [INFO] plugin: Reserved Slots Player Foul Play (76561198020478387) was kicked, because player with a reservation slot joined.
I will attach some log snippets below.
This is happening on a wide scale - I have noticed that the exact time down to the millisecond where players VIP flags are added, they are also kicked by this plugin. It appears to be a bug within the kick immunity logic - I have switched from one VIP system to another, and this is still happening.
2024-10-27 19:35:51.697 +00:00 [INFO] plugin:[VIP] Core Player 'Insurv [45xxxxxxx]' VIP information has been successfully updated
2024-10-27 19:35:51.697 +00:00 [INFO] plugin:Reserved Slots Player Insurv (765611xxxxxxxxxx) was kicked, because player with a reservation slot joined.
Here is my config file:
Please let me know if you need any more information in regards to this, thank you!
The text was updated successfully, but these errors were encountered: