[Discussion] TeamSpeak Server 3.6.0 beta

[dante696]

Server 3.6.0 stable was released a moment ago.
https://forum.teamspeak.com/threads/138675

-----------------------------------------------------

Here you can leave your feedback and discuss about server 3.6.0 beta release.
The full details about that version can be found in our release thread.

[Dialog]

But there is nothing to discuss, we all expect to see news about TS5 and NPL, isn't it more important then serverquery ?

[dante696]

We understand that you'd like to get feedback about TS5. But the development from server doesn't stop just because TS5 is also in development.

Please use this thread for TS5 related posts.
In post #1 in this thread there is the latest news/status about the NPL.

[Dialog]

We understand that you'd like to get feedback about TS5. But the development from server doesn't stop just because TS5 is also in development.

News ETA was Q4 2018, now we in 2019 and still nothing. Of course it is good to maintaine server, fixing bugs, etc... but really want to see the future of TS, atleast alpha version.

In post #1 in this thread there is the latest news/status about the NPL.

NPL is the same as Sponsorship license, so vice versa. Seems like we never gonna get more 32 slots for free, exept "not official" TS3 server versions.

[numma_cway]

The result of queryloginadd makes no sense.

Oh, and documentation omits that sid is returned for users bound to a virtual server.

Could you remove the requirement to be on the corresponding server before being able to run querylogindel?

Could you allow the global-type syntax of queryloginadd while on a virtual server?

[dante696]

queryloginadd never gave us a different cldbid in reply. As shown in example with use 1 in queryloginadd.txt.
Was server 26 selected before and how did you select it? (port or sid= or just the number).
Is there any how to available?

When adding a login to an existing client the sid is shown in output.
Like you have it in your picture.
And sid 0 is shown when this was a global login.

For technical reasons and for some security thoughts we did choose that global logins can only be added, removed or just listed when sid 0 is the selected one.
Same counts for user's on a virtual server. You only can interact with them when server was selected before.
This is something we'd like not to change in near future.

[numma_cway]

queryloginadd never gave us a different cldbid in reply.

Maybe you should have me join your testing.
The cldbid issue is caused by an integer overflow on your end (in Words, 80134=14598).

When adding a login to an existing client the sid is shown in output.
Like you have it in your picture.
And sid 0 is shown when this was a global login.

Documentation says that sid was not shown for local logins. This was the reason for my post.

Anyway, there's already an updated version of YaTQA out now.

[dante696]

We will fix both things in next beta update or in stable release (and inform in release thread in that case).

We are glad that you still test out the beta versions and give us your feedback.

edit
Here is an example of the 2 fixes.

queryloginadd client_login_name=integer_ov cldbid=80000
cldbid=80000 sid=1 client_login_name=integer_ov client_login_password=J7UjL9JF

--------------------------------------------------------

queryloginadd.txt

Example:
...
...
  use 1
  queryloginadd client_login_name=test2 cldbid=5
  cldbid=5 sid=1 client_login_name=test2 client_login_password=CMSJ5qXk
  error id=0 msg=ok

Edit 2
Beta 2 is live. Download links can be found in release thread.

[DalexHD]

All my bots seems that arent working correctly...
serverGroupAddClient seems that sometimes tells me: "ErrorID: 512 | Message: invalid clientID".


Fix: If it's query group, it would not add correctly. It whould say "ErrorID: 512 | Message: invalid clientID".

[dante696]

What is the bot doing there?

I guess it tried to add an existing user into a Query group?
If this was the case then your bot tried something unsupported. We always said this and now the server rejects this.

[DalexHD]

I have tested with yatqa, and yep, doesnt add any query group to any client. It will show "ErrorID: 512 | Message: invalid clientID".

http://prntscr.com/m9420z

The problem it's not with servergroup type, the problem it's with "clientID";

http://prntscr.com/m9438f

[dante696]

That's the desired behavior of the command when it's about Query groups.
The client you are trying to add belongs to another Server ID so the client can not be found different server.

Only global logins (created on sid=0) can be added into Query groups.


edit after post above mine got edited
Make sure the client exists on selected virtual server.
Make sure sgid=1986 is not a Query group.

[DalexHD]

I have never changed the server ID. It has been always 1
http://prntscr.com/m943uc
It stoped working since last time... I updated this server at every version for more than 1 year with out any problem...

If the servergroup is not query, it work... But why it has stoped working since last update?

[dante696]

If the servergroup is not query, it work... But why it has stoped working since last update?

It's what I wrote before. The server will not do this any longer.
While adding a new feature we also removed something we never wanted user to do.

We never gave support and warned to stop this.
Clients do not belong into Query groups. Only global ServerQuery logins do.

When you need a bot with Query permissions on your server do following.

1. Create a new login on sid=0
2. Add this new created cldbid into an existing Query group.
3. Login with that new created login
4. Select the server

[DalexHD]

Okay. On the next relaese you need to add a way to hide specified servergroup from ts3 client interface.
Before your last update, I use query group to hide from that list. Just to make it prettier and more clear on the client servergrouplist dropdown.