TeamSpeak Query servernotifyregister

[Scordo]

Hello,

some notifications like:

- notifyclientleftview
- notifycliententerview

are sent twice when registering for server and channel using:

servernotifyregister event=server
servernotifyregister event=channel id=1

Would you please ensure to only send a single notification?

Thanks,
SCO

[ScP]

When you register to server and channel events and a client connects/disconnects to/from the channel your ServerQuery client is currently residing in, the server will send the notifycliententerview and notifyclientleftview events twice.

[MuhChy]

Already reported and in our bugtracker

[orDian]

The notifyregister is kinda broken, the events are sent twice.
This was tested on Linux amd64 server 3.0.11.1 and server 3.0.11.3.

When you notifyregister on all channels: servernotifyregister event=channel id=0
You get 2 notification with the same values:

notifyclientmoved ctid=1 reasonid=0 clid=1
notifyclientmoved ctid=1 reasonid=0 clid=1
notifyclientmoved ctid=24 reasonid=0 clid=1
notifyclientmoved ctid=24 reasonid=0 clid=1

When you register on one channel, this happens, the correct behavior:

servernotifyregister event=channel id=24
error id=0 msg=ok
notifyclientmoved ctid=24 reasonid=0 clid=1 //Client ID 1 switched to channel ID 24
notifyclientmoved ctid=25 reasonid=0 clid=1 //Client ID 1 switched to channel ID 25

You can see the notifcation only being sent once.

This brings us to another "bug", you can only notifyregister on 1 channel.

servernotifyregister event=channel id=24
error id=0 msg=ok
servernotifyregister event=channel id=25
error id=0 msg=ok

Both times the query response was OK.
But if the user switches from channel ID 1 to channel ID 25, nothing happens. Only the first notifyregister on a channel is being processed.

It would be awesome if this can be fixed: Messages being sent double when notifyregister on channel id=0 and being able to notifyregister on multiple channels at once.


Suggestion
Also the best implementation I can think of is using a channel to id(ctid) and a channel from id(cfid).
For example:

servernotifyregister event=channel id=24
error id=0 msg=ok
notifyclientmoved ctid=24 cfid=25 reasonid=0 clid=1 //Client ID 1 switched to channel ID 24 from channel ID 25.
notifyclientmoved ctid=25 cfid=24 reasonid=0 clid=1 //And back again.

This is used in the event "notifycliententerview" and "notifyclientleftview" which is triggered if the client connects or disconnect from the channel that is registered.
Which is rather odd because no notifyclientmoved is triggered. What would make it more consistent.

[dante696]

Update
Server 3.9.0 will change this and only print one message

---Original report below---

This is a known old bug and this will not be fixed.

The effort of men power for the result would be to great.

[numma_cway]

YaTQA ignores duplicate consecutive lines. Also, the "from ID" can be retrieved by clientlist and then maintaining a list of users and their channels.

[fox_news]

I'm currently trying to re-do the event system for my teamspeak bot and found out that you can subscribe to all channel events at once with:

servernotifyregister event=channel id=0

It works outstandingly! However, I'm receiving duplicate responses from the server:

notifyclientmoved ctid=59244 reasonid=0 clid=107
notifyclientmoved ctid=59244 reasonid=0 clid=107
notifyclientmoved ctid=59247 reasonid=0 clid=107
notifyclientmoved ctid=59247 reasonid=0 clid=107
notifyclientmoved ctid=49742 reasonid=0 clid=107
notifyclientmoved ctid=49742 reasonid=0 clid=107
notifyclientmoved ctid=59244 reasonid=0 clid=107
notifyclientmoved ctid=59244 reasonid=0 clid=107
notifyclientmoved ctid=57922 reasonid=0 clid=107
notifyclientmoved ctid=57922 reasonid=0 clid=107
notifyclientmoved ctid=59246 reasonid=0 clid=107
notifyclientmoved ctid=59246 reasonid=0 clid=107

Is this a bug or intended and how do I fix this?

[dante696]

This is a known old bug and this will not be fixed.

The effort of men power for the result would be to great.

You need to filter the second line on your own to get it solved.