Can we have a little more inforamtions on this pluggin ?
If only with localhost this pluggin can be use on all server or I don't understand ?
Haw we can turn off the 25639 port ?
Printable View
Can we have a little more inforamtions on this pluggin ?
If only with localhost this pluggin can be use on all server or I don't understand ?
Haw we can turn off the 25639 port ?
It only binds on localhost, so only programs running locally on your pc can access it. Since clientquery is a plugin it can be enabled and disabled in the plugins dialogue, but there is no real reason to disable it, when it is not used it does not use up any CPU.
Ok thank you Peter.
Is there any documentation for this new feature? Can't seem to find any.
telnet or use putty to connect to the query and type help. They sort of explain themselves. if you need to know usage type help commandhereQuote:
Originally Posted by Stidor
lets hope they add more commands to it later.
@Stidor
For this pugglin you have doc in the pluggin folder of your client folder.
@MajorThorn
It's not for query port, this is for query pluggin.
Read the changelog of the beta 28 client.
You are wrong florian, what MajorThorn says is excellent advice. Just connect to the client query port with telnet and issue "help" and "help command". This documentation is of course based on the text files found in the plugins/clientquery_plugin/ folder.Quote:
Originally Posted by florian_fr40
Example usage on a linux shell:
Code:$ (echo help; echo quit) | nc localhost 25639
TS3 Client
selected schandlerid=1
TeamSpeak 3 Client :: ClientQuery
(c) TeamSpeak Systems GmbH
Command Overview:
help | read help files
quit | close connection
use | select server connection handler
clientnotifyregister | register to receive client notifications
clientnotifyunregister | unregister from receiving client notifications
clientlist | list known clients
currentschandlerid | server connection handler ID of current server tab
serverconnectinfo | server connect information
serverconnectionhandlerlist | list available server connection handlers
channelconnectinfo | channel connect information
channellist | list of all channels
sendtextmessage | send text message
error id=0 msg=ok
error id=0 msg=ok
ho yes, sorry, I just now understand what is really this pluggin. :oQuote:
Originally Posted by Peter
Effectively it's really convenient.
are there going to be more commands for the clientquery? like change nickname or sth like that?
This is the idea yes. The thing is there are so many possible commands that could be added :). It's hard for me to decide which ones to add when I have time to do some client query buffing.Quote:
Originally Posted by sKeLeTr0n
Checking it out now.
Very cool. Thanks!
Could I suggest a way to obtain the name of the server the client currently has selected?
Also for clientnotifyregister;
notification when someone joins/leaves the channel.
After looking into it further this is going to be perfect for a project I am working on.
If I may could I please suggest the following;
Notifications;
Users join/leave channel
Users change nickname
Channel the user is in changes name
Client changes selected server
clientlist
Possibly add a parameter to only return your own client info? (looking for a way to get my own nickname and client info)
Add in the users flags - are they headphones mutes/away/mic muted etc.
serverconnectinfo
Return the name of the server your client has selected
Nice to see the client query is proving helpful, I will see if I can add the features you requested, one thing i think is already present though:
"Add in the users flags - are they headphones mutes/away/mic muted etc."
Use the various clientlist options to display these values.
Great :-)Quote:
Originally Posted by Peter
I've checked out clientlist and can't seem to see any changes in the results if a user is muted. There's an -away tag but nothing for if mic is muted/headphones muted.
Try the "-voice" option.Quote:
Originally Posted by Stidor
Ah silly me! Thanks it most definitely is there. :-)
Very very nice! This is something I've been waiting for. :) I especially love the "talking" notifications, very useful for further processing. For my purposes, basically the only thing I miss is some kind of client join/leave notifications. Now the talking notifications report server and client id, but it may be tricky to convert the ids to actual nickname, to have client lists up-to-date. Of course the simplest would be to have the nickname right in the talk status change. :)