DwJaAtFb

1JTS3ServerMod
2Author: Stefan Martens
3
4E-Mail:
5info@stefan1200.de
6
7Homepage:
8http://www.stefan1200.de
9
10
11-= Table of Contents =-
12Copyright
13Information
14System requirements
15How to prevent a flood ban on the TS3 server
16General Informations about Installation and Usage
17Set up bot (all Operating Systems)
18Run bot on Linux
19Run bot on Windows
20Update the JTS3ServerMod
21How to get Channel ID / Client Unique ID / Client Database ID / Server Group ID / Channel Group ID
22How to get the query login credentials for the bot
23Needed Permissions for the bot
24Visibility of the bot on Teamspeak
25Different Message Types
26Global message variables
27Usage on Teamspeak Server / Chat Commands
28Logfile
29You need help?
30Credits
31
32
33-= Copyright =-
34This program is free for use, but please notify me if you find a bug or if you have some suggestion.
35The author of this program is not responsible for any damage or data loss!
36It is not allowed to sell this program for money, it has to be free to get!
37The modification of the file content of all included files of the JTS3ServerMod, including this manual, are not allowed!
38Decompiling is not allowed! Using parts of the source code in other programs is also not allowed!
39The commercial use, that means you get money for a Teamspeak 3 server or a bot of the JTS3ServerMod,
40is only allowed with a written permission from the author of the JTS3ServerMod!
41
42Teamspeak 3 is developed by TeamSpeak Systems GmbH, Sales & Licensing by Triton CI & Associates, Inc.
43More information about Teamspeak 3: http://www.teamspeak.com
44
45Launch4j was used to create the Windows executables of the JTS3ServerMod. Launch4j use the BSD/MIT license.
46More information about Launch4j: http://launch4j.sourceforge.net
47
48procrun can be used to install the JTS3ServerMod as a Windows service. procrun is an Apache Commons product and use the Apache license.
49More information about procrun: http://commons.apache.org/proper/commons-daemon/procrun.html
50
51dnsjava library is used by the Hosting Edition of the JTS3ServerMod. dnsjava use the BSD license.
52More information about dnsjava: http://www.dnsjava.org
53
54
55-= Information =-
56This program adds some functions to the Teamspeak 3 server. Here is the feature list:
57- Auto Move member of specified server groups to specified channels, if they don't have an own default channel set.
58- Channel Notify, get a message if a client joins a specified channel.
59- Server Group Notify, get a message if a member of specified server groups joins the server.
60- Server Group Protection to kick people which are unauthorized member of a protected server group.
61- Bad Nickname Check to kick people with a bad name from the server.
62- Bad Channel Name Check to delete or rename channels with a bad name.
63- Move idle users to another channel and sends a text message.
64- Kick idle users with a custom kick reason.
65- Send a warning message if someone is idle.
66- Inactive Channel Check can delete channels, which are unused for many hours/days.
67- Move to a specified channel if client status is away (after some seconds idle),
68  can move back if not away anymore.
69- Move to a specified channel if client status is headphone or microphone muted (after some seconds idle),
70  can move back if not muted anymore.
71- Move recording users to another channel and sends a text message.
72- Kick recording users from server with a kick reason.
73- Send a message every X minutes to virtual server or a special channel.
74- Send a welcome message to every connecting client, can send a special welcome message to specified server groups.
75- !lastseen chat command to see somebody's last online time.
76Anything can be configured in a config file.
77
78Another features are:
79- Many bot instances for different Teamspeak 3 servers in one bot process
80- Automatic reconnect after connection to Teamspeak 3 server lost
81- Chat commands which allows you to send messages, get client information, change configurations, reload config file, quit the bot and much more.
82- Create own plugins using Java programming language.
83- Slow Mode to use the bot (with limited features) without changing the query_ip_whitelist.txt file.
84
85
86-= System requirements =-
87This program was tested on Windows and Linux (even without X server).
88On Mac OS X 10.4+, Solaris and FreeBSD it should run too, but it was not tested. If you can test it, please send me an e-mail.
89All you need is a Java SE runtime environment version 5 or newer.
90You can get the latest official versions for Windows, Mac OS X, Linux and Solaris from http://www.java.com/en/download/manual.jsp
91Mac OS X 10.4, 10.5 and 10.6 users may have it already installed.
92FreeBSD Users should look at http://www.freebsd.org/java/ to learn more about Java on FreeBSD.
93
94Linux users should install the Java package from the operating system,
95so you get security updates using your package management software very easy.
96To install it very easy, just use the jts3servermod_startscript.sh as root with the java argument.
97Before you can use this script the first time, you have to go into the directory of the JTS3ServerMod
98and allow this script being executed:
99chmod +x jts3servermod_startscript.sh
100After you did this, just do:
101./jts3servermod_startscript.sh java
102This will check, if java is already installed, and if not, it can do this for you.
103If the automatic installation is not working:
104An example on Debian or Ubuntu: apt-get install openjdk-8-jre-headless
105An example on CentOS or Fedora -21: yum install java-1.8.0-openjdk-headless
106An example on Fedora 22+: dnf install java-1.8.0-openjdk-headless
107An example on OpenSUSE: zypper install java-1_8_0-openjdk-headless
108Depends on the used distribution version, the OpenJDK version from the examples does not exist.
109In that case just replace the 8 from the package name with an 7 or 9.
110The package gcj-jre (GNU Java) will not work!
111
112Maybe you want to limit the maximum heap memory that Java use. This can be useful on a virtual server.
113You can do this by using java command line arguments for the java virtual machine.
114If you want to use 30 MB ram as maximum, you can start the bot like this:
115java -mx30M -jar JTS3ServerMod.jar
116Notice: If you choose a to low value, the bot may not run or is not stable. Useful values are between 30M and 50M.
117I did no long time tests on this. The bot needs less ram if you disable the client database cache and using only one bot instance.
118
119Teamspeak 3 server 3.0 or newer is needed, but I recommend always to use the newest version.
120And of course a possible connection to the Teamspeak 3 server.
121
122Make sure, that the IP address of the bot is white listed using the query_ip_whitelist.txt file of the Teamspeak 3 server.
123For more information check out the topic "-= How to prevent a flood ban on the TS3 server? =-" in this readme file.
124
125
126-= How to prevent a flood ban on the TS3 server =-
127If the bot gets banned after connecting to the TS3 server, check the log file of the bot.
128If you see the following line in the log file (the number might be different), the solution should work:
129de.stefan1200.jts3serverquery.TS3ServerQueryException: ServerQuery Error 3331: flood ban
130
131Solution:
132You should add the IP address of the machine running this bot to the Teamspeak 3 server query_ip_whitelist.txt,
133or the anti spam feature of the Teamspeak 3 server will ban this program very often for some minutes.
134If the bot runs on the same machine as the TS3 server, you can set 127.0.0.1 in the bot config as address of the TS3 server.
135Because 127.0.0.1 is white listed by default.
136
137But if you are unable to change the query_ip_whitelist.txt, try to set the bot_slowmode to 1
138in the bot server config file. This slows down the bot connection speed and disables some features.
139
140
141-= General Informations about Installation and Usage =-
142Just fully unpack this ZIP file, keep the directories as they are at the ZIP file.
143It is not necessary to put this bot into the same directory as the Teamspeak 3 server,
144this bot is a standalone program which just connect to the Teamspeak 3 server telnet query port.
145
146By default there are two main config files, JTS3ServerMod_InstanceManager.cfg and JTS3ServerMod_server.cfg.
147The JTS3ServerMod_InstanceManager.cfg contains all informations about virtual bot instances,
148which should be started. In this file you can setup more virtual bot instances, if you want to have the bot
149on more TS3 servers. The JTS3ServerMod_server.cfg contains all bot settings of a virtual instance.
150Each virtual bot instance need an own configuration file.
151If you add a new bot to the JTS3ServerMod_InstanceManager.cfg you should copy the server1 directory and rename it like server2.
152After you did this, change the config file path to the new one at the new added bot in the JTS3ServerMod_InstanceManager.cfg file.
153
154So open both config files and change it to fit your needs. Everything is explained there.
155For more information about the config files read documents/ConfigHelp.html!
156But make sure that you save both files in ANSI format (encoding ISO-8859-1) and not unicode.
157Important: All other config files (like the advertising, record, idle and welcome messages)
158are saved in unicode (without BOM) by default. You can change this encoding in the main config file.
159
160Since this is a command line tool, it needs a shell to display messages on it.
161Of course it runs also without an active shell window, simple open the logfile to get all informations.
162
163On Windows you can just open the cmd.exe or use the provided EXE files.
164Linux users can run this tool even without X-Server, no GUI will be opened.
165If you want to use an X-Server, just start this tool within a Terminal / Shell.
166Mac OS X users should open the Terminal too.
167
168If you put the JTS3ServerMod.jar and the config directory (containing the file JTS3ServerMod_InstanceManager.cfg)
169in the same directory, you can simply start the server mod by enter
170java -jar JTS3ServerMod.jar
171
172On virtual servers you should limit the needed RAM of Java.
173More information at the topic "-= System requirements =-", recommended is the following value:
174java -mx30M -jar JTS3ServerMod.jar
175
176If you want to save the JTS3ServerMod_InstanceManager.cfg and JTS3ServerMod_InstanceManager.log at
177a different location or just with a different name, you can use the -config and -log argument, like this:
178java -jar JTS3ServerMod.jar -config cfg/instance.cfg -log log/instance.log
179
180Another argument is -help, which only displays a list of command line arguments and quits.
181
182It is possible to set an app.home environment variable by adding the argument -Dapp.home=PATH_TO_JTS3ServerMod
183while starting the JTS3ServerMod. This way you can use the variable %apphome% at the configfile and logfile path,
184which will be replaced by the app.home path. If no app.home environment variable exists,
185the variable %apphome% will be replaced with an empty string.
186
187Examples:
188java -Dapp.home="D:\My Services\JTS3ServerMod\" -jar JTS3ServerMod.jar
189java -mx30M -Dapp.home="/home/username/my services/JTS3ServerMod/" -jar JTS3ServerMod.jar
190
191
192-= Set up bot (all Operating Systems) =-
193Check first if you already have installed Java.
194You can check this by writing the following command at the Console / Terminal / Command Prompt:
195java -version
196You should get the output of the Java version. If not, you must install Java first.
197For more informations related to this check the section "System requirements" in this readme file.
198
199After you did this, just fully unpack the ZIP file, where you found this file.
200It is not necessary to put this bot into the same directory as the Teamspeak 3 server,
201this bot is a standalone program which just connect to the Teamspeak 3 server telnet query port.
202In the directory config you will find all configuration files of this bot, which must be changed to fit your needs.
203
204Important settings at the config file JTS3ServerMod_server.cfg,
205you must set them right to make sure that the bot will work:
206ts3_server_address
207ts3_server_query_port
208ts3_server_query_login
209ts3_server_query_password
210ts3_virtualserver_id / ts3_virtualserver_port
211bot_slowmode
212
213By default all functions are disabled. Activate them at the bot_functions line like you want.
214For more information about the functions read documents/ConfigHelp.html!
215But be careful with the following functions, because wrong configuration can make big problems:
216BadNicknameCheck
217BadChannelNameCheck
218InactiveChannelCheck
219ServerGroupProtection
220
221If one or more persons should be bot admins, you must set one of the following settings:
222Bot Full Admin (all admin commands, only persons you trust!): JTS3ServerMod_InstanceManager.cfg -> bot_fulladmin_list
223Bot Admin (only admin commands of the virtual bot instance): JTS3ServerMod_server.cfg -> bot_admin_list
224
225Now all important settings are done. Save all files, but make sure that you save both files
226in ANSI format (encoding ISO-8859-1) and not unicode. All other config files (like the advertising,
227record, idle and welcome messages) are saved in unicode (without BOM) by default.
228You can change this encoding in the config file JTS3ServerMod_server.cfg -> bot_messages_encoding.
229
230To start the bot read the according section:
231Run bot on Linux
232Run bot on Windows
233
234
235-= Run bot on Linux =-
236The first time start the bot like described at the topic "General Information about Installation and Usage".
237As soon as everything is running like you want, stop the bot (e.g. using Ctrl + C) and go on with this topic.
238
239The best way is to use the included jts3servermod_startscript.sh script.
240Just go into the directory of the JTS3ServerMod and allow this script being executed:
241chmod +x jts3servermod_startscript.sh
242After that you can start the JTS3ServerMod by using:
243./jts3servermod_startscript.sh start
244
245To stop the JTS3ServerMod just do:
246./jts3servermod_startscript.sh stop
247
248Further arguments of the script are: restart, status and java
249
250If you run into problems, check the section "System requirements" in this readme file.
251It is possible to reduce the amount of the heap memory which java use.
252This is important on Linux VServers.
253If the script should do that for you, just open the file jts3servermod_startscript.sh with a text editor you like,
254go to line 6 and change
255JAVA_COMMANDLINE_PARAMETERS=""
256to
257JAVA_COMMANDLINE_PARAMETERS="-mx30M"
258
259Also make sure that your system don't run into the open files limit if you have very much bots running at the same time.
260Check the open files value using the following command: ulimit -a
261You need around two files for each virtual bot instance. Example: 200 bots need at least an 400 open files limit.
262Using the following command you can change that limit: ulimit -n <new limit>
263Changing this value has an effect to all processes on your system!
264Sometimes this setting reset to the default value. Please check how you can make the new value permanent.
265
266
267-= Run bot on Windows =-
268First way is to start the bot as normal application on Windows.
269To do this just run JTS3ServerMod-Windows_NoWindow.exe.
270All outputs of the bot will be saved to the log file, which will be created by the bot.
271Of course you can put a shortcut of the JTS3ServerMod-Windows_NoWindow.exe to the Windows Auto Start directory,
272to start the bot on Windows login, but make sure that the "Start in" directory is the JTS3ServerMod directory.
273To open the Windows Auto Start directory, just press the two keys Windows + R and enter: shell:startup
274
275If wanted, you can run the bot as a Windows Service, this allows the bot to run in background without a logged in user.
276
277To create a Windows service with the Apache procrun tool, I prepared a small script which do anything for you.
278In the tools sub directory you find the script InstallWindowsService.cmd.
279If you want, you can edit this script to change the config and logfile path or to change the name of the service.
280But it should also work without changing anything, the default service name is JTS3ServerMod.
281Just run this script with Administrator permissions (right click on it and start as administrator).
282
283The last step is to start the service like displayed at the end of this script.
284
285Important:
286The service needs the absolute path to all config files. But my script sends the current path to the JTS3ServerMod.
287This allows to use the variable %apphome% at the path in all config files.
288If the path is not available (maybe the JTS3ServerMod was not started using the service),
289%apphome% will be replaced with an empty string.
290
291
292-= Update the JTS3ServerMod =-
293Sometimes you should check my homepage, if there is a new version available for the JTS3ServerMod.
294You can also activate the bot_update_check in the config/JTS3ServerMod_InstanceManager.cfg file,
295to notify all clients on the bot_fulladmin_list about a new JTS3ServerMod version, as soon as they connect to the TS3 server.
296
297In most cases you only have to replace the JTS3ServerMod.jar file, while the JTS3ServerMod process is stopped.
298But you should take a look into the config/JTS3ServerMod_InstanceManager.cfg file, if there are new values,
299which you like to copy over to your own file. But in most cases that config file changes are optional and not required.
300
301I recommend to start the JTS3ServerMod with the argument -updateconfig after
302replacing the JTS3ServerMod.jar file, that updates all bot configuration files!
303Whole command: java -jar JTS3ServerMod.jar -updateconfig
304Notice: This -updateconfig will also delete all lines of removed or renamed functions in the bot configuration files!
305
306
307-= How to get Channel ID / Client Unique ID / Client Database ID / Server Group ID / Channel Group ID =-
308The easiest way to get the Channel ID, Client Unique ID and Client Database ID is
309to install a very nice extended info pane template of dante696:
310http://forum.teamspeak.com/threads/73296-Release-Extended-Client-Info
311
312If you don't want to install it, you can use the bot to get the Channel ID.
313Just get the bot running and use the chat command !getchannelid <part of the Channel Name> to get the Channel ID.
314As an example: !getchannelid away
315If you don't change the default value -1 of bot_channel_id you don't have to know any Channel IDs on first bot start!
316But make sure that you are a bot admin or full admin, or you can't use the command.
317
318To copy the Client Unique ID of a client just open the Permissions window of your TS3 client and search for the client
319you need within the server groups and make a right click on it. Now you see the context menu entry Copy UniqueID to clipboard.
320Just click it and paste it where you need it.
321On smaller TS3 servers you can also use the menu entry Permissions -> List All Clients, also here you can copy it
322with a right click on the client. But with more than 100 clients on that TS3 server this it not really usable.
323
324The Server Group ID and Channel Group ID will be displayed in the Permissions window after clicking on the TS3 Client menu entry
325Permissions -> Server Groups
326Permissions -> Channel Groups
327Next to the group name you see the ID of the group. Of course you have to be connected to the server.
328
329A small problem is the Client Database ID, because TS Systems removed almost all ways to get it using the TS3 Client.
330Currently it is only possible with the optional extended info pane template.
331But since JTS3ServerMod 5.3 you can use the Client Unique ID for the chat commands too.
332The bot recognize automatically if you use the Client Unique ID and request the Client Database ID from the TS3 Server.
333
334
335-= How to get the query login credentials for the bot =-
336If you host the TS3 server on your own, the easiest way is to use the serveradmin login credentials of the TS3 server.
337This already has almost all needed permissions and you don't have any problems with the identity of the bot.
338
339If you don't host the TS3 server on your own or don't like to use the serveradmin account,
340you can create new query login credentials with your TS3 client, you just need the permission: b_client_create_modify_serverquery_login
341But first create a new TS3 identity for the bot. If you don't do this,
342the bot is connected with your identity, which confuse all TS3 clients.
343
344To create a new identity, click on Settings -> Identities -> Add
345Enter a name for the identity, something like TS3 bot or JTS3ServerMod. Copy the new Unique ID and close that window.
346Now connect to your TS3 server with your TS3 client using this new identity.
347Click on More if the identity setting is not visible at the Connect window.
348After you did this, connect again as Server Admin, if not already, and open the Permissions -> Server Groups window.
349Choose the Server Group you want to use for the bot, like the Server Admin group, and add the new identity to this Server Group
350by clicking on Add and paste the new Unique ID here. Make sure that this server group has all needed permissions,
351look at "Needed Permissions for the bot" in this readme file for a list.
352Connect again with your TS3 client using the new identity, if not still connected.
353If you connected to your server multiple times, make sure that the connection tab with the new identity is activated!
354Now click on Tools -> ServerQuery Login and enter the login name, you like to have.
355Write down the login name, you have chosen, and the password you got from the TS3 client.
356Use this new details for the bot now. Make sure that you don't use this identity with your TS3 client anymore.
357But keep it saved, because you can use it to change the query login password, if necessary some day.
358
359
360-= Needed Permissions for the bot =-
361If you use the serveradmin query account, all permissions are already set.
362Self-created query accounts might need additional permissions, even if they are in the Server Admin group.
363
364Make sure that the following permissions are granted for the query account of the bot (in brackets why this permission is needed):
365- b_channel_delete_flag_force (Bad Channel Name Check)
366- b_channel_delete_permanent (Bad Channel Name Check)
367- b_channel_delete_semi_permanent (Bad Channel Name Check)
368- b_channel_delete_temporary (Bad Channel Name Check)
369- b_channel_join_ignore_password (Allow joining all channels)
370- b_channel_join_permanent (Allow joining all channels)
371- b_channel_join_semi_permanent (Allow joining all channels)
372- b_channel_join_temporary (Allow joining all channels)
373- b_channel_modify_name (Bad Channel Name Check)
374- b_client_channel_textmessage_send (Advertising)
375- b_client_ignore_sticky (If you work with sticky groups)
376- b_client_info_view (Welcome Message)
377- b_client_remoteaddress_view (To display the IP address)
378- b_client_server_textmessage_send (Advertising)
379- b_group_is_permanent (The bot stay at this group after reconnecting)
380- b_virtualserver_channel_list (Always needed)
381- b_virtualserver_channelgroup_client_list (chat command !removechannelgroups)
382- b_virtualserver_client_dbinfo (Some chat commands)
383- b_virtualserver_client_dblist (Always needed)
384- b_virtualserver_client_dbsearch (Some chat commands)
385- b_virtualserver_client_list (Always needed)
386- b_virtualserver_info_view (Always needed)
387- b_virtualserver_notify_register (Always needed)
388- b_virtualserver_notify_unregister (Always needed)
389- b_virtualserver_servergroup_list (Always needed)
390- i_channel_join_power (Allow joining all channels)
391- i_channel_modify_power (Bad Channel Name Check)
392- i_client_complain_power (Many functions if complain is enabled)
393- i_client_kick_from_channel_power (Bad Channel Name Check)
394- i_client_kick_from_server_power (Many functions)
395- i_client_move_power (Many functions)
396- i_client_permission_modify_power (Server Group Protection)
397- i_client_poke_power (Many functions if poke is chosen as message mode)
398- i_client_private_textmessage_power (Always needed)
399- i_group_member_add_power (Server Group Protection)
400- i_group_member_remove_power (Server Group Protection)
401
402The "Guest Server Query" group also needs:
403- b_serverquery_login (To connect)
404- b_virtualserver_select (To connect)
405
406Additional optional permission, grant it for the query account of the bot or the "Guest Server Query" group.
407If set to the "Guest Server Query" group, it applies to all virtual TS3 servers:
408- b_serverinstance_permission_list (Displaying missing permission names in log)
409
410
411-= Visibility of the bot on Teamspeak =-
412By default the bot will be invisible on the Teamspeak 3 server, because it is just a telnet client
413and not a real Teamspeak 3 client. With default permission settings it is easy to make the bot visible
414for Teamspeak 3 server administrators. Just open the Teamspeak 3 client Bookmarks -> Manage Bookmarks ->
415select the server entry and click on More, if not already. Now activate the option "Show ServerQuery clients".
416Now you should be able to see the bot in the Teamspeak 3 client. If still not,
417check the permissions like I wrote in the next paragraph.
418
419If you also want to allow other server groups to see the bot, just add the permission
420i_client_serverquery_view_power to that group. Use a higher value than the i_client_needed_serverquery_view_power of the bot.
421But every client still need the setting in the options to see the bot.
422
423
424-= Different Message Types =-
425You can choose different message types for the most functions of the bot,
426check the default JTS3ServerMod_server.cfg file for this.
427Currently there are chat and poke valid, at some functions you can also use none to disable sending a message.
428Depends on Teamspeak 3 server limits, you can only use 100 characters for a poke message,
429including spaces and BBCode. Chat messages have a much higher limit at 1023 characters,
430also including spaces and BBCode. You should pay attention to this limits, or the bot can't send
431any message and you will find an error in the logfile of the bot.
432
433If a message will be send as kick reason, the maximum character count for the kick reason is 80.
434
435
436-= Global message variables =-
437If enabled in bot configuration, you can use the following global variables for all messages:
438%SERVER_NAME% - Server name
439%SERVER_PLATFORM% - Server platform (Windows, Linux, ...)
440%SERVER_VERSION% - Server version
441%SERVER_CREATED_DATE% - Server created date
442%SERVER_UPTIME% - Server uptime in days, hours, ...
443%SERVER_UPTIME_DATE% - Server uptime as date
444%SERVER_UPLOAD_QUOTA% - Server upload quota
445%SERVER_DOWNLOAD_QUOTA% - Server download quota
446%SERVER_MONTH_BYTES_UPLOADED% - Uploaded data in current month (filetransfer and avatar)
447%SERVER_MONTH_BYTES_DOWNLOADED% - Downloaded data in current month (filetransfer and avatar)
448%SERVER_TOTAL_BYTES_UPLOADED% - Uploaded data all times (filetransfer and avatar)
449%SERVER_TOTAL_BYTES_DOWNLOADED% - Downloaded data all times (filetransfer and avatar)
450%SERVER_MAX_CLIENTS% - Server max clients (slots)
451%SERVER_RESERVED_SLOTS% - Server reserved slots
452%SERVER_CHANNEL_COUNT% - Current channel count
453%SERVER_CLIENT_COUNT% - Current client count
454%SERVER_CLIENT_DB_COUNT% - Full client count of the TS3 database
455%SERVER_CLIENT_CONNECTIONS_COUNT% - Server client connections count
456Most server information are not updated instantly, they will be updated every 60 seconds.
457If you don't need this variables, disable the global message variables in your bot configuration to save performance!
458
459
460-= Usage on Teamspeak Server / Chat Commands =-
461Since version 1.0 it is possible to use some bot commands in the chat of the Teamspeak 3 server.
462You can use the server, channel or private chat. Of course you have to be in the same channel for the channel chat.
463Too many commands exists to list them here. Just do in Teamspeak server, channel or private chat: !bothelp
464This displays a list of all commands. To check if the bot is running, you can also type: !botinfo
465To be a bot admin, you must enter your public unique ID of your client in the bot config file.
466There is also a list of all bot commands in documents/ChatCommandHelp.html
467
468Since bot version 3.1 there are two different bot admins possible.
469You can set full admins in the JTS3ServerMod_InstanceManager.cfg file,
470normal bot admins are set in each virtual bot instance config file for every server.
471Full bot admins can use all bot commands on every bot instance, only add persons you trust!
472Normal bot admins are limited to the own bot instance and cannot use the following commands:
473!exec, !execwait, !botquit, !botinstancelist, !botinstancestart, !botinstancestop
474
475
476-= Logfile =-
477This program creates a logfile with the name JTS3ServerMod_InstanceManager.log.
478But this program will also run and work, if it cannot write or create this log file.
479The logfile of the InstanceManager contains informations and errors about starting and stopping virtual bot instances.
480
481Each bot instance can create an own log file, this can be set in JTS3ServerMod_InstanceManager.cfg for every virtual bot instance.
482By default the log file is named JTS3ServerMod_server1.log for the first virtual bot instance.
483A virtual bot instance logs all actions on Teamspeak server and of course all errors while doing this.
484
485
486-= You need help? =-
487Of course you can write an email to me and try to explain your problem (what happens when?).
488But please add config and log files of the bot to your email.
489
490If you need more information how to setup the bot correctly, please make sure that you read this file completely.
491More information about the bot config files are written down in the documents/ConfigHelp.html file.
492Make sure that you read that too.
493
494
495-= Credits =-
496For bug reporting, sending suggestions and testing a thanks flies to:
497- 130ng0
498- ADM24
499- Adam M.
500- Ahmet I.
501- André A. / Kartoffel-Stampfer
502- Atranox / End-Gaming.eu
503- BEN89
504- Baggavy J.
505- Benjamin B.
506- Benjamin L.
507- BoKo / WebShell
508- Bralosch
509- ChoosenEye
510- Chris / Orange Bots
511- Christoph
512- Christopher / Lenzen Networks
513- Corba
514- DaRkBoZ
515- Daniel L.
516- DarRoe
517- DarkGhost
518- David K.
519- Denden / TSforYOU
520- Dr.No
521- DunklerKeks / Dark Empire Clan
522- EidEchse
523- FRAGGYNZ
524- Fabrice
525- Felix R.
526- Flavio
527- Flofus
528- FoXFTW
529- Frank B.
530- Fusionpot
531- GWR
532- Gamle / MainGaming.dk
533- Giftzwerg
534- Guus W.
535- Heiko
536- Hermann W.
537- Hinken
538- HoschY1987
539- Invictus International / TS Server HQ
540- IronMC
541- Jay / Clanwarz
542- Jeremy P.
543- Johannes1509
544- KingHunt / Gamers Platoon
545- Kirbyfan1223
546- Lore
547- MajorThorn
548- Mariuszeq
549- Marko M.
550- Mateusz Z.
551- Megamaluco
552- Micha5
553- Mikołaj
554- MrChicken
555- NaTesTa10
556- NanooTec
557- Nate4ever
558- Nobody_cbm / Software Galaxy
559- Pascal / Fierlord-Hosting
560- Patschi
561- Philip H. / squaX
562- Pierre N. / Next-Host
563- Prototype
564- Raiden4918 / Subculture-Gaming
565- Robert M.
566- Robin B. / TS3-4You
567- Rowtag
568- Sandro M. / TS Voice
569- Saucenteufel
570- Sebastian S.
571- SkullDrago
572- Slater
573- Speddyroot
574- St3v3
575- Stefan R.
576- Surf3rDud3
577- TS-Coach
578- Taishou / NLFS Bündnis
579- TeaTow
580- Thomas / Science System
581- ThomasHH / thl-online
582- TotoIsBack
583- Tukaa
584- WaterFlow
585- Yanek
586- barricas
587- cigaming
588- dukio
589- eggster
590- elpoepel
591- kadama / Oxivoice
592- livedisco
593- mastermax
594- mathewitp / Old Dragons
595- mthomas
596- sojakfa
597- thecrew
598- tigerle
599- whvler
600- xeomueller / xgs.in
601- xoun
602List in alphabetical order.