Supervisor
Administrator
- Apr 27, 2015
- 1,863
- 2,546
- 335
Hey, here we can collect bugs in the current version of the two client. Maybe someone will be able to make use of it..
Please post the bug and the link to the source where you found it, also post whether it is client side or server side and the version where the bug exists
I'll start with the first one:
TS3 Client 3.0.16
Please post the bug and the link to the source where you found it, also post whether it is client side or server side and the version where the bug exists
I'll start with the first one:
TS3 Client 3.0.16
Link to sourcedante696 said:Private chats are build with checks for the UID and for the Client ID (not the databse id).
A Client ID isn't bound to users and will be available again for other users, when an user with the old Client ID has left the server.
This process takes ~10 minutes till the Client ID is released and ready to be used from next user who connects to teh server.
- The check for the UID prevents that other users send you a message in the same chat.
This did happen, when the client only checked for the client ID (which is avaiable for other users).
- The check for the Client ID is for the connection check
So your client checks and knows if that person is still online or just has returned.
Maybe the check for the client id does not check if that user has the same UID.
I will test that later that day. Thank you for reporting if we found a bug
------------merged------------
Yep, the check for "user disconnected" only seems to check for the client id and shows wrong status.
Client connected works fine.
A bug ticket for developers was created.
Last edited by dante696; 16-01-2015 at 11:31. Reason: bug approved
Last edited: