Advertisement
Not a member of Pastebin yet?
Sign Up,
it unlocks many cool features!
- # JTS3ServerMod Instance Manager config file
- #
- # Each bot instance need:
- # X.instance_enable
- # X.instance_name
- # X.instance_config_path
- #
- # Optional:
- # X.instance_logfile_path
- # X.instance_csvloginlog_path
- # X.instance_debug = 1
- #
- # For X use a number starting from 1. Make sure that you have not more than 10 missing numbers between the instances.
- # At least one enabled instance is needed or the bot process will stop after starting.
- #
- # This file must be saved with the encoding ISO-8859-1!
- # A comma seperated list (without spaces) of unique user ids,
- # which should be able to use bot full admin commands on all bot instances.
- # Bot full admin can also see the TS3 server password and is able to use the !exec command.
- # The unique user ids looks like this: mBbHRXwDAG7R19Rv3PorhMwbZW4=
- bot_fulladmin_list = OleFvKPpfJKMOxeYi6C/5lnTUCQ=
- # Allow !exec and !execwait commands for bot full admins? 1 = Yes, 0 = No
- # This allow you to execute system commands.
- # Only use !execwait for commands which quits within some seconds,
- # because the bot waits for the end of this command to send you the text output of the program.
- # Use !exec for commands with a longer runtime instead,
- # this command don't send you any text output, because the bot don't wait for it.
- bot_command_exec = 0
- # Every time a bot full admin connects to the TS3 server it will be checked if an update for the JTS3ServerMod is available.
- # If an update is available, a chat message will be sent to the bot full admin.
- # 0 = disable, 1 = final versions, 2 = final and test versions
- bot_update_check = 0
- # The own personal licence key.
- # Read the instructions, to know how to get one, at the download page of the JTS3ServerMod Hosting Edition.
- bot_licence_key = JTS3SMHE-2BMHE-1e5c63420f1d6be17e0adbf41c37ee390e412a05f8a330fd57063bc269c3a528
- # Add a small delay in milliseconds to the bot starting process.
- # Only change this value if you have problems starting all bots at once, like hanging bot threads.
- delay_bot_start = 100
- # Enable the multi IP mode. 1 = Enable, 0 = Disable
- # If slow mode is activated, this feature split bot connections to the Teamspeak 3 servers.
- # Events (Chat and some functions) and the Client Database Cache gets an own connection which should solve the IP ban problem.
- multiipmode_enable = 0
- # Local IP Address of the main connection, make sure that this is not the same as for chat and cache!
- multiipmode_ip_main = 123.123.123.123
- # Local IP Address of the chat connection, make sure that this is not the same as for main and cache!
- multiipmode_ip_chat = 124.124.124.124
- # Local IP Address of the cache connection, make sure that this is not the same as for chat and main!
- multiipmode_ip_cache = 125.125.125.125
- # First local port
- multiipmode_portrange_min = 50000
- # Last local port
- # Make sure, that you have at least 3 ports for every bot, which use the slow mode!
- multiipmode_portrange_max = 51999
- # Enable the Query Interface of the JTS3ServerMod. 1 = Enable, 0 = Disable
- # You are able to start, stop or reload a virtual bot instance using this Query Interface.
- telnet_enable = 1
- # Choose a port for the Query Interface, default port is 5873.
- telnet_port = 5873
- # Choose a password for the Query Interface.
- # If this password is shorter than 6 characters, the Query Interface will be disabled!
- telnet_password = Ug/gxq0y?]q[2g9e5![k
- # Choose a network interface for the Query Interface. Only set a single ip address of a local network interface here.
- # Set nothing here to bound the Query Interface to all network interfaces (default).
- # Example: Set to 127.0.0.1 (IPv4) or ::1 (IPv6) to allow connections only from localhost.
- telnet_bindTo = 127.0.0.
- # A comma seperated list (without spaces) of IP addresses, which are allowed to connect to the Query Interface.
- # Leave empty, if every IP address is allowed to connect.
- telnet_whitelist = 127.0.0.1
- # Log query connection attempts to logfile? 1 = Enable, 0 = Disable
- telnet_connection_log = 1
- # Enable this to prevent that the JTS3ServerMod process quits if no bot instances are running. 1 = Enable, 0 = Disable
- # You can still quit the process with !botquit in TS3 client chat or with botquit on the Query Interface.
- telnet_run_forever = 1
- # Use a MySQL database to save bot instances and configurations. 1 = Enable, 0 = Disable
- # There should be a structure sql file in the documents directory.
- # Import this into your MySQL database to create the tables (the included web interface do this already for you).
- # But you must fill this tables by yourself, the bot just reads the information out there.
- mysql_enable = 1
- mysql_host = 127.0.0.1
- mysql_port = 3306
- mysql_user = JTS3
- mysql_password = Xaucz0z76vv813o4dusv
- mysql_database = JTS3
- # Optional MySQL settings, more information on https://dev.mysql.com/doc/connector-j/en/connector-j-reference-configuration-properties.html
- # Possible values: -1 = default, 0 = disable, 1 = enable
- mysql_verifyServerCertificate = -1
- mysql_useSSL = -1
- mysql_requireSSL = -1
- mysql_useCompression = -1
- # Normal log entries older than X days will be deleted from MySQL jts3servermod_log table. 0 = disable auto delete!
- mysql_log_delete = 0
- # Connection log entries older than X days will be deleted from MySQL jts3servermod_log table. 0 = disable auto delete!
- mysql_connection_log_delete = 0
Advertisement
Add Comment
Please, Sign In to add comment
Advertisement