The query login for TerraBot requires at least the rights that are higher or at least equal to the admin rank, as TerraBot is an administration tool and therefore uses many functions for managing TeamSpeak.

Since TerraBot not only manages normal users but also admins and other high-ranking groups, it is necessary to set the rights accordingly at a high level.

The rights distribution of TeamSpeak is very complex and also needs to be approached with caution. For this reason, we will not go directly into the settings to create a query server group, but only specify the specific rights that TerraBot needs. In the section titled "", we have a guide on how to properly create a query login. Before creating a query login, you should first create a server group for the bot with the correct rights.

There are 2 different ways to create a server group correctly. The well-known method is to use the (default) admin query group, which is no longer used as the current default.

We use the 2nd method, which is currently the common assignment.

Steps to create this login

1. Copy an admin server group and name it after the bot
2. Adjust the permissions in the new admin server group for TerraBot
3. Follow the instructions in the section titled ""

Required server group rights for TerraBot

Standard values for the highest permissions are usually set at a power of "75". However, these may differ depending on the settings of the admin or the TeamSpeak provider. In our example, we assume the highest setting of "75". However, it should be noted that the "Needed-Power" of these rights must not exceed this.

Required rights

Retrieve information from TeamSpeak

Virtual Server

• "b_virtualserver_info_view"
• "b_virtualserver_channel_list"
• "b_virtualserver_client_list"

Server Group

• "b_virtualserver_servergroup_list"
• "b_virtualserver_servergroup_permission_list"
• "b_virtualserver_servergroup_client_list"
• "b_virtualserver_channelgroup_list"
• "b_virtualserver_channelgroup_permission_list"
• "b_virtualserver_channelgroup_client_list"

Channel

• "b_virtualserver_client_permission_list"
• "b_virtualserver_channel_permission_list"
• "b_virtualserver_channelclient_permission_list"

Client

• "b_client_info_view"
• "b_client_permissionoverview_view"
• "b_client_permissionoverview_own"
• "b_client_remoteaddress_view"
• "i_client_serverquery_view_power"
• "i_client_serverquery_view_power" = min. "75"
• "b_client_custom_info_view"

Execute permissions on TeamSpeak

Create Channel

• "b_channel_create_child"
• "b_channel_create_permanent"
• "b_channel_create_semi_permanent"
• "b_channel_create_temporary"
• "b_channel_create_with_topic"
• "b_channel_create_with_description"
• "b_channel_create_with_password"
• "b_channel_create_with_banner"
• "b_channel_create_modify_with_codec_opusvoice"
• "b_channel_create_modify_with_codec_opusmusic"
• "i_channel_create_modify_with_codec_maxquality" = min. "10"
• "b_channel_create_with_maxclients"
• "b_channel_create_with_maxfamilyclients"
• "b_channel_create_with_sortorder"
• "b_channel_create_with_default"
• "b_channel_create_with_needed_talk_power"
• "i_channel_create_modify_with_temp_delete_delay" = "86400"

Modify Channel

• "b_channel_modify_parent"
• "b_channel_modify_make_default"
• "b_channel_modify_make_permanent"
• "b_channel_modify_make_semi_permanent"
• "b_channel_modify_make_temporary"
• "b_channel_modify_name"
• "b_channel_modify_topic"
• "b_channel_modify_description"
• "b_channel_modify_password"
• "b_channel_modify_banner"
• "b_channel_modify_codec"
• "b_channel_modify_codec_quality"
• "b_channel_modify_codec_latency_factor"
• "b_channel_modify_maxclients"
• "b_channel_modify_maxfamilyclients"
• "b_channel_modify_sortorder"
• "b_channel_modify_needed_talk_power"
• "i_channel_modify_power" min. "75"
• "b_channel_modify_make_codec_encrypted"
• "b_channel_modify_temp_delete_delay"

Delete Channel

• "b_channel_delete_permanent"
• "b_channel_delete_semi_permanent"
• "b_channel_delete_temporary"
• "b_channel_delete_flag_force"
• "i_channel_delete_power" = min. "75"

Channel Access

• "i_channel_min_depth" = "-1"
• "i_channel_max_depth" = "-1"
• "i_channel_permission_modify_power" = min. "75"

Client Admin Permissions

• "i_client_kick_from_server_power" = min. "75"
• "i_client_needed_kick_from_server_power" = min. "75"
• "i_client_kick_from_channel_power" = min. "75"
• "i_client_needed_kick_from_channel_power" = min. "75"
• "i_client_ban_power" = min. "75"
• "i_client_move_power" = min. "75"
• "i_client_needed_move_power" = min. "75"
• "i_client_complain_power" = min. "75"
• "i_client_needed_complain_power" = min. "75"

Client Basics

• "i_client_private_textmessage_power" = min. "75"
• "b_client_server_textmessage_send"
• "b_client_channel_textmessage_send"
• "b_client_offline_textmessage_send"
• "i_client_talk_power" = min. "75"
• "i_client_poke_power" = min. "75"
• "b_client_set_flag_talker"

Client Modifications

• "i_client_permission_modify_power" = min. "75"
• "i_client_needed_permission_modify_power" = min. "75"
• "i_client_max_clones_uid" = min. "1"
• "i_client_max_channel_subscriptions" = min. "-1"
• "b_client_skip_channelgroup_permissions"
• "b_client_ignore_bans"
• "b_client_ignore_antiflood"
• "b_client_use_reserved_slot"
• "b_client_use_channel_commander"
• "b_client_request_talker"
• "b_client_avatar_delete_other"
• "b_client_ignore_sticky"

These settings are currently the necessary conditions for the bot to function properly. However, we want to emphasize that not all information may be accurate and additional permissions may need to be modified. As our bot continues to evolve, it's possible that this list may expand and new bound permissions will need to be added.

A query login gives an application the ability to connect to a Teamspeak without a client application. The queries are usually not visible for normal users and can only be seen by admins (as far as this is set correctly).

Even if you can't see the queries in Teamspeak, you occupy an official slot from Teamspeak. Since the update from the Teamspeak server version 3.4.1, it is also no longer provided by Teamspeak that a given query group can be assigned to normal clients. But this is not a big deal, because you can create a query login with normal server groups.

There are different types of bots that also need different server group permissions. It is already very important that you do not give a bot more rights than it needs and clarify this in advance.

It is also important that you create a separate identity for each bot to also have this bot under control without deleting other users or bots.

To be able to edit the server groups in more detail, you should first set the advanced rights system, which you can set under "Extras -> Options -> Applications -> Miscellaneous -> Advanced rights system"

We explain how to correctly create a query login and how to apply it.

---

Instruction

1. 
   Copy a server group that has the most server group rights that your bot needs. And name this server group with the name of the bot (For later control, it is good if each bot also has its own server group).
   "Rights -> Server Groups -> Select appropriate server group -> Right-click and copy -> Name copied server group after the bot"
2. 
   Adjust additional server group permissions that your bot needs.
   "Rights -> Server Groups -> Click the "wrench arrow" in the bottom left corner to get to the advanced server group setting -> Select appropriate server group -> Adjust necessary permissions"
3. 
   Create a new identity for the bot and name this identity after your bot.
   "Extra -> Identities -> Create -> Identity Name: (bot name) -> Nickname: (not relevant)"
4. 
   Connect to a new user with the new created identity on teamspeak under a new tab.It is very important that you are connected to your admin account and the new identity on your teamspeak.
   "Connections -> Click 'More' -> Server Nickname or Address on the bottom left: Your Teamspeak address -> Nickname: (not relevant) -> Identity: Newly created identity -> In new tab"
5. 
   In Teamspeak, in the tab at the top, now select your admin account and assign the new user with the new identity the newly created server group you want the bot to have.
   "Right click on the new user -> Set Server Group -> (click on the newly created server group)"
6. 
   Now select Sie at the top of the tab again your newly created user and create a new query login. Often the mistake happens that you accidentally create a query login with your admin. Make sure that you have really selected the newly created user in the tab.
   "Extras -> ServerQuery Login -> Name: Enter any login name (Make sure to avoid spaces or special characters) -> OK"
7. From Teamspeak you will now get your login name and associated password, which you can enter into the appropriate fields on the bot. Our recommendation, make a note of this query login, because you can not call them again later.

IMPORTANT: As soon as you create a new query login with the same user, all old data will be deleted and thus the bots will stop working.