Abasalt_Yar
Member
Hi, when someone connects to the server using nonsense names like emojis. if you are an old client, you'll crash.
What should I do ?
What should I do ?
Pending invalid parameter | nonsense names
- Thread starter Abasalt_Yar
- Start date
Do you have a screenshot?
I'm not sure what you mean.
I'm not sure what you mean.
Abasalt_Yar
Member
Seems like somebody is enjoying the UTF-8 codes and inserts some spaces as a name.
I'm seeing nothing wrong with that. The TeaClient should support such.
I'm seeing nothing wrong with that. The TeaClient should support such.
Abasalt_Yar
Member
Yeah, TeaClient is ok and but the other client ( the old version ) has problems. I've just tried to add some subscribe power to the welcome channel and kick everyone with other than ligal characters.
What's an "old" client for you?
Abasalt_Yar
Member
like Tea*Speak 3.1.10
DarcyElioT
Active member
Most people who buy protocol_key Their goal is to be able to connect all versions to the server and to be able to connect Tea*Speak versions to the server This can cause minor issues and bugs, but we can not force members to use TeaClient
It should actually support UTF-8 characters.
What's the disconnect message?
We don't support any third party software.
We only support the own TeaSpeak web/native client.
Abasalt_Yar
Member
disconnect message is (invalid parameter)
If so I need a trace log.
As well ensure you're using 1.5.0
As well ensure you're using 1.5.0
Abasalt_Yar
Member
Hmm, since I enabled the trace log It's not happening :/
But If it happened I'll let you know.
and thanks for the help
---- Automatically Merged Double Post ----
sorry, but do you know why this happened?
Dropping command packet because command assembly buffer has an underflow: pid: 47, bidx: 49, bcap: 32
almost 20~25 people has been disconnected because of this at the same time
Last edited:
"I need a trace log."
Abasalt_Yar
Member
Hi, sorry for mention.
check this, when the user joins. all the old clients drop.
---- Automatically Merged Double Post ----
---- Automatically Merged Double Post ----
*New clients can't see the emoji so they won't get crash and I made a plugin/script when someone joins with characters other than A-Z, the user gets banned for 30seconds. no effects
Last edited:
You can actiually add a regex ban which bans the "null" character.
Tbh I'm confused how this even gets allowed since non UTF8 characters will get dropped.
Tbh I'm confused how this even gets allowed since non UTF8 characters will get dropped.
Abasalt_Yar
Member
*New clients can't see the emoji so they won't get crash and I made a plugin/script when someone joins with characters other than A-Z, user gets banned for 30seconds
---- Automatically Merged Double Post ----
Non UTF8 characters are dropped in new versions
there is, user got banned after joining but it's not effecting.
---- Automatically Merged Double Post ----
Non UTF8 characters are dropped in new versions
Last edited:
Sure? In the screenshot you provided the user nor the character has been banned.
You could use this command:
This should disallow such characters within the name.
But I'll have a look and fix it.
You could use this command:
Code:
banadd name=.*\\0.*But I'll have a look and fix it.
Abasalt_Yar
Member
Oh, I'm using nodejs and I think you are talking about something else
DarcyElioT
Active member
This problem occurs when
The person who is doing the bug enters the server in seconds and crashes most of the copies
We can not do anything manually because we do not know what words and characters it uses
Because when this is done, old versions can not see it, causing a crash
If you come to add in Teaspeak files that the person who wants to enter the server can not use other authorized characters and ban his server very quickly, this problem will be solved
I think Ts3 prevented this bug like this
Because Ts3 once had this bug
Fixed in 1.5.1-b2