Server: some problems with the User ID number for people that connect #1686
Replies: 7 comments 4 replies
-
I don't understand the issue. %lastuser% is the user who has been connected for the least amount of time. |
Beta Was this translation helpful? Give feedback.
-
@bearware101
I think he ment the ID will reset to number 1 after reach 4000 plus plus. Maybe, but I not really sure.
|
Beta Was this translation helpful? Give feedback.
-
For me is not a problem but I not sure how about him. 😊
|
Beta Was this translation helpful? Give feedback.
-
An ID is only an identified, not something which has to be coherent with a statistic or a previous identifier. |
Beta Was this translation helpful? Give feedback.
-
it seems @computertech1012 is requesting a new variable like %currentuser% which is the user that just connected. %lastuser% is the last user to connected, but not the current one. |
Beta Was this translation helpful? Give feedback.
-
Hi, Unofficial server, Name: Gelegar Bangsa Multimedia TeamTalk Server, Users: 17, Country: SG, MOTD: Hi Stats! Then here is one from the Green list. This is an example, every time someone connects it shows Ragu and he is user ID number 4056. Public server, Name: Indonesian TeamTalk Server (ID), Users: 45, Country: ID, MOTD: Hai, Until that person disconnects, every single user that logs in will get that he is the last person, when that is false information. My user ID to connect there was 277. So since that other person was having a higher number this is false variable so maybe now you understood about it. |
Beta Was this translation helpful? Give feedback.
-
Hi, |
Beta Was this translation helpful? Give feedback.
-
Hi,
I am not sure if I should convert this into an issue or not, because I don't know how really to explain the problem.
So, basicly if you are connected to a server, let's say you are user ID number 4000 or something like that, eventually, if you reconnect, or if other people reconnect, eventually the ID number get set back to 1, or 2, and then continuing to go up after that.
This could cause a problem if you are using the ID feature for having MOTD variables in the server.
I will give you an example.
Let's say that my user name is "User" and I am user ID 3211. After a while several people connect and disconnect, and eventually the server goes back to resetting the ID number starting from like either 2 or something like that. I really don't know how to reproduce. But I think @bear101 would probably understand this. Let's say someone eventually connects with the user ID of 10. The person that connected with user ID number 10 would get the MOTD but it would show it as saying that last connected user was the user in number 3211. So if the MOTD said that the last connected user was %lastuser% then it would say last connected user was the user of 3211. I hope you understood what I am saying, it resets after a surten number, and I don't think it's 3211 that it resets, that was only by example.
Also note that if user 3211 were to disconnect, it would then take who ever was connnected with the higher number. So if someone is connected with say userid 3125, then it would for the next user say that the last user was that one instead of saying that the last user was the person that just connected.
If they were to disconnect and no numbers were higher than them it would resolve, but it only happens if the user count or whatever you call the User ID is reset back to lower numbers, like 1 or 2 or 3 or whatever it resets to. And that's what I am noticing.
I apologize, because I really don't know how to explain this. But eventually the server count ID number for the users is reset after the server has been running a while and people have reconnected and what not. That is what I am gathering from the server end anyway.
If you don't understand, or need me to explain a better way let me know and I will do my best.
Thanks for reading!
Beta Was this translation helpful? Give feedback.
All reactions