Wrath X
Member
- Oct 2, 2015
- 96
- 34
- 53
Have you got skin in your ts3 client ?So, it works for new version?? ....That's nice
For me didn't work though as i just tried!
Client Crash [till 3.0.19.2]
Alligatoras
Administrator
- Mar 31, 2016
- 2,570
- 12
- 2,855
- 381
Nope!, the default one, i have only edited on that the right side, so i can see the DB ID, and UID
It worked on 3.0.19.1 that i tested it, just doesn't work after the update!
Wrath X
Member
- Oct 2, 2015
- 96
- 34
- 53
I am not at home now, so I didn't test it. Btw how you edit the right side ?
Alligatoras
Administrator
- Mar 31, 2016
- 2,570
- 12
- 2,855
- 381
Go to your teamspeak 3 directory "TeamSpeak 3 Client" and open "styles/default" (or the skin you are using) and open the "clientinfo.tpl" with a notepad and edit the area you want! If you want to edit the server info or the channel info just open the other files "serverinfo.tpl" or "channelinfo.tpl"
Nýuu™
Member
- Nov 18, 2015
- 150
- 54
- 63
- Thread starter
- #28
Just to make this clear it still works on 3.0.19.2
just do it like this
a%%CLIENT_NAME%%
Look:
http://forum.teamspeak.com/threads/125574-Client-Freeze-caused-by-invalid-name
just do it like this
a%%CLIENT_NAME%%
Look:
http://forum.teamspeak.com/threads/125574-Client-Freeze-caused-by-invalid-name
Last edited:
Wrath X
Member
- Oct 2, 2015
- 96
- 34
- 53
Using skin still working for solution.Just to make this clear it still works on 3.0.19.2
just do it like this
a%%CLIENT_NAME%%
Look:
http://forum.teamspeak.com/threads/125574-Client-Freeze-caused-by-invalid-name
X-Ecutioner
Contributor
- Sep 16, 2015
- 183
- 121
- 175
For temporary relief, you can set a ban on that client name.
Tools > Ban List > Add
Name: .*%%CLIENT_NAME%%.*
Interpret IP/Name as: Regular Expression
Duration: permanent
Tools > Ban List > Add
Name: .*%%CLIENT_NAME%%.*
Interpret IP/Name as: Regular Expression
Duration: permanent
X-Ecutioner
Contributor
- Sep 16, 2015
- 183
- 121
- 175
It is not for me ; ) This is for those who likes to do this bug
- Jan 30, 2016
- 1,334
- 1,146
- 254
I didn't mean in a way you're abusing the exploit, I meant it as who would ever connect with a percentage sign in his name anyway? Even if this exploit was never found.
I don't think people would notice if "%" would be permabanned from all TeamSpeak 3 servers by default.
What I'm trying to say is you can also permanently ban that sign (%) instead of forcing an update on all clients.
X-Ecutioner
Contributor
- Sep 16, 2015
- 183
- 121
- 175
Yes , you never know
- Jan 30, 2016
- 1,334
- 1,146
- 254
Source?
- Apr 25, 2015
- 1,845
- 2
- 2,199
- 327
I am guessing he switched to the beta channel (settings) and reviewed the changelog.
- Jan 30, 2016
- 1,334
- 1,146
- 254
I am guessing he switched to the beta channel (settings) and reviewed the changelog.
What the fuck, I'm on beta and I ain't get no update, that's racist.
Alligatoras
Administrator
- Mar 31, 2016
- 2,570
- 12
- 2,855
- 381
I am guessing he switched to the beta channel (settings) and reviewed the changelog.
Guys...i am not in beta and i get the update!
Pretty sure that 3.0.19.3 is stable!
- Jul 18, 2015
- 635
- 588
- 157
- Jan 30, 2016
- 1,334
- 1,146
- 254
Found it, didn't get a notification when restarting, I'm even on beta channel.
Manually updated it.