Hello there,
I noticed unusual behavior when using extremely long temporary bans in the TS6 client and would like to bring attention to it.
In the TS6 client, it is possible to set a temporary ban duration of 9999 years. However, after saving the ban, this value does not appear to be processed correctly. Instead of showing a duration of 9999 years, the ban window states that the ban will expire in 9992 years, 4 months and 9 days.
This suggests that the configured duration is either internally recalculated incorrectly or limited by a maximum supported value.
There is also inconsistent behavior when the banned user attempts to reconnect. When connecting with the TS6 client, the user is informed that they are permanently banned.
When connecting with the TS3 client, the following message is shown:
This creates contradictory information. On one hand, the TS6 client displays the ban as permanent, while on the other hand, the TS3 client recognizes it as a temporary ban but appears unable to correctly process the remaining duration.
I tested this behavior on both a TeamSpeak 3 Server (version 3.13.7) and a TS6 Server (version 6.0.0-beta9). The same behavior could be reproduced on both server versions.
The expected behavior would be that a configured duration is either applied exactly as entered or, if 9999 years is not technically supported, the value should be limited or rejected with an error message. In addition, all clients should display the same ban type and a correct remaining duration.
It appears there may be an issue related to time calculation, value limits, or an overflow problem in compatibility between TS3 and TS6.
This can be reproduced by setting a temporary ban of 9999 years in the TS6 client and then attempting to reconnect using both the TS6 and TS3 clients.
I hope this information helps with investigating the issue.
Thank you.
. Appreciated.