In terms of that "Activation License"... there are no plans to change the way TeamSpeak is licensed. Some of the existing license types have been re-named as 3.1.0 will introduce an entirely new accounting system (as we've announced earlier).
And what the hell is a "activation license"?
"default hosting license" (3.1.6) on the 3.1.7 renamed to "activation license".
@XRV-Webix
Are there any new information?
this is not accurate information, they are already half years say "within a few weeks"We will be releasing server 3.1 beta within a few weeks (barring any additional setbacks).
It's the official information. So, accurate one. Or do you know any of their devs that can provide you with a specific date? If so, make my guest.this is not accurate information, they are already half years say "within a few weeks"
It's the official information. So, accurate one. Or do you know any of their devs that can provide you with a specific date? If so, make my guest.
dante696;450489 said:There is no fixed release date yet**.
**Possibly first weeks in November.
Thats a good oneClever move.. He doesn't named a year.
Maybe this one helps you: http://www.teamspeak.com/en/licensing.html
Brraaahh....Maybe this one helps you: http://www.teamspeak.com/en/licensing.html
dante696 said:What do you expect when you did something we never gave any support? You did break your server at the moment you did it.
And we never gave any support, when user started to assign themselves Query group!
But anyways we will check that.
Update
I can reproduce this and will report to our developers. But i don't promise a fix for this.
Update 2
The same thing happens when you start a fresh 3.1 databse and just restart your instance.
I don't do hacking, you need to wait for a response from hackers (likely response in a few days)what do you say about the new accounting system? Now there will not be a hacked license?
I'm sorry i have tested your problem on phynixgaming with the admin server query but i don't have any errors...new feature or bug?
Clear server:
The same thing happens when you start a fresh 3.1 databse and just restart your instance.I'm sorry i have tested your problem on phynixgaming with the admin server query but i don't have any errors...