-
Notifications
You must be signed in to change notification settings - Fork 108
- Why can't I connect to the server?
- Why am I getting a TS3ConnectionFailedException?
- What is the difference between a voice and a query port?
- How do I create a Server Query login?
- Why can't I listen to channel chat for all channels?
- Why am I getting a command error by calling getClientInfo() on a ClientLeveEvent?
- What is the difference between an event's client and invoker?
- Why does ClientLeaveEvent only provide getClientId(), but not getClientUniqueId() or getClientNickname()?
- What's the difference between a Client ID, a Database ID, and a Unique ID?
Coming soon!
Coming soon!
The voice port is the port used for clients to connect to the server. Typically, a server's address is "www.xxx.yyy.zzz:1234" or "www.domain.com:1234," where the 1234 represents the voice port (default 9987) used to connect via client. The query port (default 10011) is the port used by query accounts to connect via Telnet. If your server is through a host, there's a chance your query is not the default. If that is the case, your host should let you know what your query port is when you receive your server. Otherwise, you can only find your query port within the "server.ini" file.
While connected to a TeamSpeak server through a client, go to "Tools" along the menu bar and select "ServerQuery Login" to initiate the dialog. Once open, input the name you wish your query to log in with and click "OK."
The next screen will display both the name and the password your query will use to connect.
Note that any query created will share its UID with the client that created it.
This issue is especially pronounced when privately messaging users from the query while the target user has an existing private conversation active with the creator.
First, it helps to understand that a query is essentially a text-only client. Like a normal client, your query can only be present in a single channel (and by extension, a single channel's chat) at a time.
Coming soon!
The invoker is the person causing the event to be triggered, while the client is the person being affected by the event. In the example of a ClientLeaveEvent triggered by kicking a client, the person being affected (the client) is the person leaving while the person causing the event (the invoker) is the person kicking the victim. If someone left of their own volition, they are still the client; there is just no invoker.
Why does ClientLeaveEvent only provide getClientId(), but not getClientUniqueId() or getClientNickname()?
Coming soon!
Coming soon!