Advertisement
Not a member of Pastebin yet?
Sign Up,
it unlocks many cool features!
- # Config file of the JTS3ServerMod
- 2.# http://www.stefan1200.de
- 3.# This file must be saved with the ANSI encoding ISO-8859-1!
- 4.
- 5.# Teamspeak 3 server address
- 6.ts3_server_address = goldenlegends.net
- 7.# Teamspeak 3 server query port, default is 10011
- 8.ts3_server_query_port = 10011
- 9.# Teamspeak 3 server query admin account name
- 10.ts3_server_query_login = serveradmin
- 11.# Teamspeak 3 server query admin password
- 12.ts3_server_query_password = ZmOlGarV
- 13.# Teamspeak 3 virtual server ID or -1 to use ts3_virtualserver_port
- 14.ts3_virtualserver_id = 1
- 15.# Teamspeak 3 virtual server port, only needed if ts3_virtualserver_id is set to -1
- 16.ts3_virtualserver_port = 9987
- 17.
- 18.# Channel id, the bot will join into it after connecting. If not wanted, use a negative number like -1.
- 19.# Don't set the default channel here, because the bot is already in the default channel after connecting.
- 20.bot_channel_id = -1
- 21.# Activate the slow mode of the bot, 0 = disable, 1 = enable.
- 22.# If slow mode is activated, the bot connects slower to the server
- 23.# and disables some bot features to reduce the amount of needed commands.
- 24.# This feature may allow you to use the bot without whitelist the bot IP address.
- 25.# Slow mode disables the client database cache and do not allow the bot check interval to be lower than 3 seconds.
- 26.bot_slowmode = 0
- 27.# Check every X seconds, default is 1. Values between 1 and 30 are allowed.
- 28.# If slow mode is activated, 3 is the lowest possible value.
- 29.bot_check_interval = 1
- 30.# A different encoding of the messages config files.
- 31.# Default is UTF-8 which should be good for all EU and US languages.
- 32.# Change this only if you know what you are doing!
- 33.# For English or German language you can also use the encoding ISO-8859-1
- 34.# A list of all valid ones: http://docs.oracle.com/javase/1.5.0/docs/guide/intl/encoding.doc.html
- 35.bot_messages_encoding = UTF-8
- 36.# This enables the client database list cache. This cache is needed for commands like !searchip. 1 = Enable, 0 = Disable
- 37.bot_clientdblist_cache = 1
- 38.# This enables the global message variables. See readme file for a list of variables. 1 = Enable, 0 = Disable
- 39.# If enabled, you can use all server variables in all messages. If not needed, disable this to save performance.
- 40.bot_global_message_vars = 1
- 41.# Server Query name, this will be displayed as name of the connection.
- 42.bot_server_query_name = GLC Server's
- 43.# Second Server Query name, this will be displayed as name of the connection.
- 44.# This name will be used, if the first name is already in use.
- 45.bot_server_query_name_2 = GLC BOT's
- 46.# Change the date pattern, which will be used to format a date in chat functions and welcome message.
- 47.# To get help how to make such a pattern, look here: http://docs.oracle.com/javase/1.5.0/docs/api/java/text/SimpleDateFormat.html
- 48.bot_date_pattern = yyyy-MM-dd HH:mm:ss
- 49.# Change the timezone of the bot, which will be used for the date of the chat functions and welcome message.
- 50.# If nothing is set here, the default timezone of the operating system will be used.
- 51.# To get a list of valid timezones, look at the TZ column on the following page:
- 52.# https://en.wikipedia.org/wiki/List_of_tz_database_time_zones#List
- 53.bot_timezone =
- 54.# Should the bot try to connect forever if the Teamspeak server or the bot is offline? 0 = disable, 1 = enable
- 55.bot_connect_forever = 0
- 56.# Minimum log level, how much details you want to be written to the bot log files? Default is 1.
- 57.# Higher log levels will be also written, as an example: You set log level to 2, level 2, 3 and critical errors will be written to bot log file.
- 58.# 0 = Debug
- 59.# 1 = Information (recommended and default)
- 60.# 2 = Warning (recommended for smaller log files)
- 61.# 3 = Error (experts only)
- 62.bot_log_level = 1
- 63.# A comma separated list (without spaces) of unique user ids, which should be able to use bot admin commands.
- 64.# The unique user ids looks like this: mBbHRXwDAG7R19Rv3PorhMwbZW4=
- 65.bot_admin_list =
- 66.# A comma separated list (without spaces) of server group ids, which should be able to use the following bot admin commands:
- 67.# !clientsearch, !searchip, !listinactiveclients, !listinactivechannels, !channellist, !setchannelname, !setchannelgroup, !removeservergroups, !removechannelgroups, !msgchannelgroup and !msgservergroup.
- 68.# All other bot admin commands are not allowed!
- 69.bot_lightadmingroup_list =
- 70.
- 71.# Set a comma separated list (without spaces) of needed bot functions here.
- 72.# Each function needs the function class (or plugin filename) and the function name, both separated with a colon.
- 73.# All possible function classes are listed below, that class is case sensitive!
- 74.# You can use external functions, they have to be in the plugins directory and you have to use the filename
- 75.# including the jar file extension as function class, as an example: AutoKickTimer.jar:akt
- 76.# That function name you choose is important and has to be unique. It will be used as prefix for the configuration key names and chat commands.
- 77.# Don't use spaces in the function names, only use letters, numbers, minus and underscore!
- 78.# Most functions allow multiple usage, that allows you to set as many welcome messages or idle check rules, as you want.
- 79.# Don't forget that you have to put all settings of the functions in this file.
- 80.# Hint: Start the bot with the argument -updateconfig after adding bot functions, that writes the configuration for all functions into this file!
- 81.# Whole command: java -jar JTS3ServerMod.jar -updateconfig
- 82.# Notice: This -updateconfig will also delete all lines of removed or renamed functions in this config file!
- 83.# For more information about the functions read documents/ConfigHelp.html or documents/ConfigHelp_deutsch.html!
- 84.#
- 85.# Example: IdleCheck:idle,IdleCheck:idle_guest,MuteMover:mute,WelcomeMessage:welcome,WelcomeMessage:welcome_guest
- 86.# This example gives you the following:
- 87.# - Two IdleCheck with the name idle and idle_guest
- 88.# - One MuteMover with the name mute
- 89.# - Two WelcomeMessage with the name welcome and welcome_guest
- 90.#
- 91.# Function list (multiple use possible):
- 92.# Advertising - Send messages to channel or server chat every X minutes
- 93.# AutoMove - Move connecting clients of a specified server group to a specified channel
- 94.# AwayMover - Move the client as soon as away status is set for longer than X seconds
- 95.# BadChannelNameCheck - Checking for bad channel names, can delete the channel and punish the client
- 96.# BadNicknameCheck - Checking for bad nicknames and can punish the client
- 97.# ChannelNotify - Notify specified server groups about clients joining a specified channel
- 98.# IdleCheck - Move or kick an idle client, can also send an idle warning message
- 99.# InactiveChannelCheck - Delete channels if empty for more than X hours
- 100.# LastSeen - Chat command to check the last online time of a client (client database list cache must be enabled!)
- 101.# MuteMover - Move the client as soon as the specified mute status is set for longer than X seconds
- 102.# RecordCheck - Move or kick a recording client (of course only the record function of the Teamspeak client is detected)
- 103.# ServerGroupNotify - Notify specified server groups about clients of specified server groups connecting to the TS3 server
- 104.# ServerGroupProtection - Make sure that only specified clients are members of the specified server groups
- 105.# WelcomeMessage - Sends a message to new connected clients
- 106.bot_functions = Advertising:advertising,AutoMove:automove,AwayMover:away,BadChannelNameCheck:badchannelname,BadNicknameCheck:badnickname,ChannelNotify:channelnotify,IdleCheck:idle,InactiveChannelCheck:icc,LastSeen:lastseen,MuteMover:mute,RecordCheck:record,ServerGroupNotify:servergroupnotify,ServerGroupProtection:servergroupprotection,WelcomeMessage:welcome,WelcomeMessage:welcome_guest
- 107.# Set a comma separated list (without spaces) of needed but disabled bot functions here.
- 108.# Same format as bot_functions!
- 109.# All functions you set here are not activated at bot start, but you can switch on functions using chat commands.
- 110.bot_functions_disabled =
- 111.
- 112.
- 113.# Is the target of the advertising messages a channel or a server? Possible values (just write one of the both words!): channel or server
- 114.advertising_mode = server
- 115.# If a channel is the target, set channel id to write advertising message into it
- 116.advertising_channel_id =
- 117.# Advertise every X minutes
- 118.advertising_repeat_time = 30
- 119.# Path to file which contains the advertising messages.
- 120.advertising_file = %apphome%config/server1/advertising.cfg
- 121.
- 122.# A comma separated list (without spaces) of platform names (it's the same value as %CLIENT_PLATFORM% at the welcome message).
- 123.# Only selected platforms will be moved or leave this empty to move all platforms.
- 124.# Possible platforms: Windows, Mac, Linux, Android, iOS
- 125.automove_platform_list = Windows, Mac, Linux, Android, iOS
- 126.# Select the message mode, how the clients should get the message.
- 127.# poke, chat or none are valid values!
- 128.automove_message_mode = chat
- 129.# Path to file which contains the auto move configuration and message.
- 130.automove_file = %apphome%config/server1/automove.cfg
- 131.
- 132.# Move client back if not away anymore? Set yes or no here!
- 133.away_moveback = yes
- 134.# Channel id to move away clients into it
- 135.away_channel_id = 3781
- 136.# Idle time in seconds after the client with away status will be moved to the channel.
- 137.# Has between 0 and 10000 seconds!
- 138.away_delay = 450
- 139.# A comma separated list (without spaces) of channel ids.
- 140.# Depends on the given mode, this channels can be ignored or only this channels will be checked!
- 141.# If no channels should be ignored, set no channels here and select the channel list mode ignore!
- 142.away_channel_list = 4009
- 143.# Select one of the two modes for the channel list.
- 144.# ignore = The selected channels will be ignored.
- 145.# only = Only the selected channels will be checked.
- 146.away_channel_list_mode = ignore
- 147.# A comma separated list (without spaces) of server group ids.
- 148.# Depends on the given mode, this server groups can be ignored or only this server groups will be checked!
- 149.# If no server groups should be ignored, set no server groups here and select the group list mode ignore!
- 150.away_group_list = 2,3001,2910,2914,3153,3152,3151
- 151.# Select one of the two modes for the server group list.
- 152.# ignore = The selected server groups will be ignored.
- 153.# only = Only the selected server groups will be checked.
- 154.away_group_list_mode = ignore
- 155.# Select the message mode, how the client should get the message.
- 156.# poke, chat or none are valid values!
- 157.away_message_mode = none
- 158.# Path to file which contains the away mover message
- 159.away_file = %apphome%config/server1/awaymessages.cfg
- 160.
- 161.# Move client back if not away anymore? Set yes or no here!
- 162.away1_moveback = yes
- 163.# Channel id to move away clients into it
- 164.away1_channel_id = 4009
- 165.# Idle time in seconds after the client with away status will be moved to the channel.
- 166.# Has between 0 and 10000 seconds!
- 167.away1_delay = 1
- 168.# A comma separated list (without spaces) of channel ids.
- 169.# Depends on the given mode, this channels can be ignored or only this channels will be checked!
- 170.# If no channels should be ignored, set no channels here and select the channel list mode ignore!
- 171.away1_channel_list =
- 172.# Select one of the two modes for the channel list.
- 173.# ignore = The selected channels will be ignored.
- 174.# only = Only the selected channels will be checked.
- 175.away1_channel_list_mode = ignore
- 176.# A comma separated list (without spaces) of server group ids.
- 177.# Depends on the given mode, this server groups can be ignored or only this server groups will be checked!
- 178.# If no server groups should be ignored, set no server groups here and select the group list mode ignore!
- 179.away1_group_list = 2
- 180.# Select one of the two modes for the server group list.
- 181.# ignore = The selected server groups will be ignored.
- 182.# only = Only the selected server groups will be checked.
- 183.away1_group_list_mode = only
- 184.# Select the message mode, how the client should get the message.
- 185.# poke, chat or none are valid values!
- 186.away1_message_mode = none
- 187.# Path to file which contains the away mover message
- 188.away1_file = %apphome%config/server1/awaymessages1.cfg
- 189.
- 190.# Instantly kick client that creates a channel with a bad name? Set yes or no here!
- 191.badchannelname_kick = no
- 192.# Instantly delete a channel with a bad name? Set always, onlynew or no here!
- 193.# onlynew = Try to rename channel back first. Only if that fail (maybe channel is quite new and the old name is unknown) the channel will be deleted!
- 194.# no = Try to rename channel back, but the channel will not be deleted!
- 195.badchannelname_delete = onlynew
- 196.# A comma separated list (without spaces) of channel ids.
- 197.# This channels will be ignored!
- 198.badchannelname_channel_list =
- 199.# Add complain entry to the user? Set yes or no here!
- 200.badchannelname_add_complain = no
- 201.# A comma separated list (without spaces) of server group ids.
- 202.# Depends on the given mode, this server groups can be ignored or only this server groups will be checked!
- 203.# If no server groups should be ignored, set no server groups here and select the group list mode ignore!
- 204.badchannelname_group_list =
- 205.# Select one of the two modes for the server group list.
- 206.# ignore = The selected server groups will be ignored and can create channels with bad channel names.
- 207.# only = Only the selected server groups will be checked.
- 208.badchannelname_group_list_mode = ignore
- 209.# Select the message mode, how the client should get the message.
- 210.# poke, chat or none are valid values!
- 211.# If client kick is activated, the message will be always used as kick message!
- 212.badchannelname_message_mode = poke
- 213.# Path to file which contains the Bad Channel Name Check rules and the message.
- 214.badchannelname_file = %apphome%config/server1/badchannelname.cfg
- 215.
- 216.# Kick client with a bad nickname? Set yes or no here!
- 217.badnickname_kick = yes
- 218.# Add complain entry to the user? Set yes or no here!
- 219.badnickname_add_complain = no
- 220.# A comma separated list (without spaces) of server group ids.
- 221.# Depends on the given mode, this server groups can be ignored or only this server groups will be checked!
- 222.# If no server groups should be ignored, set no server groups here and select the group list mode ignore!
- 223.badnickname_group_list = 2
- 224.# Select one of the two modes for the server group list.
- 225.# ignore = The selected server groups will be ignored and can have bad nicknames.
- 226.# only = Only the selected server groups will be checked.
- 227.badnickname_group_list_mode = ignore
- 228.# Select the message mode, how the client should get the message.
- 229.# poke or chat are valid values!
- 230.# If client kick is activated, the message will be always used as kick message!
- 231.badnickname_message_mode = none
- 232.# Path to file which contains the bad nickname message and check rules.
- 233.badnickname_file = %apphome%config/server1/badnickname.cfg
- 234.
- 235.# Channel id that should be watched for new clients. You can only set one channel id here!
- 236.channelnotify_channel_id =
- 237.# A comma separated list (without spaces) of server group ids.
- 238.# Depends on the given mode, this server groups can be ignored or only this server groups will be watched!
- 239.# If no server groups should be ignored, set no server groups here and select the group list mode ignore!
- 240.channelnotify_group_list =
- 241.# Select one of the two modes for the server group list.
- 242.# ignore = The selected server groups will be ignored.
- 243.# only = Send a notify message only if the selected server groups join the channel.
- 244.channelnotify_group_list_mode = ignore
- 245.# A comma separated list (without spaces) of server group ids, which should be notified about new clients in the specified channel.
- 246.channelnotify_grouptargets =
- 247.# A comma separated list (without spaces) of channel ids.
- 248.# Depends on the given mode, target clients in this channels can be ignored or only clients in this channels receive the notify message!
- 249.# If no channels should be ignored, set no channels here and select the channel list mode ignore!
- 250.channelnotify_channel_list =
- 251.# Select one of the two modes for the channel list.
- 252.# ignore = Clients in the selected channels will be ignored.
- 253.# only = Only clients in the selected channels receive the notify message.
- 254.channelnotify_channel_list_mode = ignore
- 255.# Select the message mode, how the notified clients should get the message.
- 256.# poke or chat are valid values!
- 257.channelnotify_message_mode = poke
- 258.# Select the message mode, how the clients (who joined the channel) should get the message.
- 259.# poke, chat or none are valid values!
- 260.channelnotify_messagenotified_mode = none
- 261.# Path to file which contains the channel notify message
- 262.channelnotify_file = %apphome%config/server1/channelnotifymessages.cfg
- 263.
- 264.# Select the action if a client is idle for more than the specified maximum time, possible values: kick and move
- 265.idle_action = move
- 266.# If clients got moved, move client back if not idle anymore? Set yes or no here!
- 267.idle_moveback = yes
- 268.# If clients should be moved, set channel id to move idle clients into it.
- 269.idle_channel_id = 3781
- 270.# A comma separated list (without spaces) of channel ids.
- 271.# Depends on the given mode, this channels can be ignored or only this channels will be checked!
- 272.# If no channels should be ignored, set no channels here and select the channel list mode ignore!
- 273.idle_channel_list = 4009
- 274.# Select one of the two modes for the channel list.
- 275.# ignore = The selected channels will be ignored.
- 276.# only = Only the selected channels will be checked.
- 277.idle_channel_list_mode = ignore
- 278.# A comma separated list (without spaces) of server group ids.
- 279.# Depends on the given mode, this server groups can be ignored or only this server groups will be checked!
- 280.# If no server groups should be ignored, set no server groups here and select the group list mode ignore!
- 281.idle_group_list = 2,3001,2910,2914,3153,3152,3151
- 282.# Select one of the two modes for the server group list.
- 283.# ignore = The selected server groups will be ignored.
- 284.# only = Only the selected server groups will be checked.
- 285.idle_group_list_mode = ignore
- 286.# Set the max idle time in minutes.
- 287.# If clients should be kicked, the client will be kicked after being idle for this time.
- 288.# If clients should be moved, the client will be moved to specified channel after being idle for this time!
- 289.idle_max_time = 30
- 290.# If clients should be moved, set the max idle time in minutes to kick someone.
- 291.# Has to be greater than idle_max_time or -1 to disable this feature!
- 292.idle_second_max_time = -1
- 293.# Set the idle warn time in minutes or set -1 to disable this feature.
- 294.# The idle warn time has to be smaller than the max idle time
- 295.idle_warn_time = -1
- 296.# A minimum client count to activate the idle check (Query clients are not counted).
- 297.# If less clients are in the channel or on the server, idle check does nothing.
- 298.idle_min_clients = 3
- 299.# Select if the minimum client count is needed in the channel or on the server.
- 300.# channel or server are valid values!
- 301.idle_min_clients_mode = channel
- 302.# If clients should be moved, select the message mode, how the client should get the message.
- 303.# poke, chat or none are valid values!
- 304.idle_message_mode = chat
- 305.# Select the message mode, how the client should get the message.
- 306.# poke or chat are valid values!
- 307.idle_warn_message_mode = chat
- 308.# Path to file which contains the idle messages
- 309.idle_file = %apphome%config/server1/idlemessages.cfg
- 310.
- 311.# After how many hours an empty channel should be deleted? Possible values between 1 and 2200 hours.
- 312.icc_emptydeletetime = 168
- 313.# Never delete permanent channels? Set yes or no here!
- 314.icc_ignore_permanent = no
- 315.# Never delete semi permanent channels? Set yes or no here!
- 316.icc_ignore_semipermanent = no
- 317.# Never delete spacer channels (like [cspacer])? Set yes or no here!
- 318.icc_ignore_spacer = no
- 319.# A comma separated list (without spaces) of channel ids you like to ignore. This channels don't get deleted!
- 320.icc_ignore_channels =
- 321.# A comma separated list (without spaces) of parent channel ids (use 0 for the top level).
- 322.# Depends on the given mode, all sub-channels of this channels can be ignored or only sub-channels of this channels will be checked!
- 323.# The check parent channel only mode allows you to check the activity only on the selected parent channels (which will be reset also on activity in sub-channels) and delete the parent channel including the sub channels, if it is detected inactive.
- 324.# If no parent channels should be ignored, set no channels here and select the channel list mode ignore!
- 325.icc_parentchannel_list =
- 326.# Select one of the four modes for the parent channel list.
- 327.# ignore = All sub-channels of the selected channels will be ignored.
- 328.# only = Only sub-channels of the selected channels will be checked.
- 329.# parentignore = Only the parent channels will be checked (and will delete all sub channels), which are not on the list.
- 330.# parentonly = Only the parent channels will be checked (and will delete all sub channels), which are on the list.
- 331.icc_parentchannel_list_mode = ignore
- 332.
- 333.# Who should be able to use the last seen command? Possible values: all, botadmin, servergroup
- 334.lastseen_user = botadmin
- 335.# A comma separated list (without spaces) of server group ids.
- 336.# Depends on the given mode, this server groups can be ignored or only this server groups will be allowed to use the !lastseen command!
- 337.# This is only needed, if user servergroup is selected!
- 338.lastseen_group_list =
- 339.# Select one of the two modes for the server group list.
- 340.# ignore = The selected server groups will be ignored.
- 341.# only = Only the selected server groups are allowed to use the !lastseen command!
- 342.lastseen_group_list_mode = ignore
- 343.
- 344.# Move client back if not muted anymore? Set yes or no here!
- 345.mute_moveback = yes
- 346.# Enable move if headphone is muted, yes or no
- 347.mute_headphone = yes
- 348.# Enable move if microphone is muted, yes or no
- 349.mute_microphone = no
- 350.# Enable move if headphone hardware is disabled, yes or no
- 351.mute_headphone_hardware = no
- 352.# Enable move if microphone hardware is disabled, yes or no
- 353.# This also happen if someone is speaking in another TS3 client server tab.
- 354.mute_microphone_hardware = no
- 355.# Move the client if the client has all selected conditions or at least one? Set all or one here!
- 356.mute_condition_mode = one
- 357.# Channel id to move muted clients into it
- 358.mute_channel_id = 3781
- 359.# Idle time in seconds after the client with a specified mute status will be moved to the channel.
- 360.# Has between 0 and 10000 seconds!
- 361.mute_delay = 300
- 362.# A comma separated list (without spaces) of channel ids.
- 363.# Depends on the given mode, this channels can be ignored or only this channels will be checked!
- 364.# If no channels should be ignored, set no channels here and select the channel list mode ignore!
- 365.mute_channel_list = 4009
- 366.# Select one of the two modes for the channel list.
- 367.# ignore = The selected channels will be ignored.
- 368.# only = Only the selected channels will be checked.
- 369.mute_channel_list_mode = ignore
- 370.# A comma separated list (without spaces) of server group ids.
- 371.# Depends on the given mode, this server groups can be ignored or only this server groups will be checked!
- 372.# If no server groups should be ignored, set no server groups here and select the group list mode ignore!
- 373.mute_group_list = 2,3001,2910,2914,3153,3152,3151
- 374.# Select one of the two modes for the server group list.
- 375.# ignore = The selected server groups will be ignored.
- 376.# only = Only the selected server groups will be checked.
- 377.mute_group_list_mode = ignore
- 378.# Select the message mode, how the client should get the message.
- 379.# poke, chat or none are valid values!
- 380.mute_message_mode = none
- 381.# Path to file which contains the mute mover message
- 382.mute_file = %apphome%config/server1/mutemessages.cfg
- 383.
- 384.# Select the action if a client starts recording, possible values: kick and move
- 385.record_action = kick
- 386.# If clients should be moved, set channel id to move recording clients into it
- 387.record_channel_id =
- 388.# A comma separated list (without spaces) of channel ids.
- 389.# Depends on the given mode, this channels can be ignored or only this channels will be checked!
- 390.# If no channels should be ignored, set no channels here and select the channel list mode ignore!
- 391.record_channel_list =
- 392.# Select one of the two modes for the channel list.
- 393.# ignore = The selected channels will be ignored.
- 394.# only = Only the selected channels will be checked.
- 395.record_channel_list_mode = ignore
- 396.# A comma separated list (without spaces) of server group ids.
- 397.# Depends on the given mode, this server groups can be ignored or only this server groups will be checked!
- 398.record_group_list =
- 399.# Select one of the two modes for the server group list.
- 400.# ignore = The selected server groups will be ignored and are allowed to record.
- 401.# only = Only the selected server groups will be checked and punished, if they start recording.
- 402.# If no server groups should be ignored, set no server groups here and select the group list mode ignore!
- 403.record_group_list_mode = ignore
- 404.# A comma separated list (without spaces) of channel group ids.
- 405.# Depends on the given mode, this channel groups can be ignored or only this channel groups will be checked!
- 406.# If no channel groups should be ignored, set no channel groups here and select the group list mode ignore!
- 407.record_channelgroup_list =
- 408.# Select one of the two modes for the channel group list.
- 409.# ignore = The selected channel groups will be ignored and are allowed to record.
- 410.# only = Only the selected channel groups will be checked and punished, if they start recording.
- 411.record_channelgroup_list_mode = ignore
- 412.# Add complain entry to the user? Set yes or no here!
- 413.record_add_complain = no
- 414.# If clients should be moved, select the message mode, how the client should get the message.
- 415.# poke, chat or none are valid values!
- 416.record_message_mode = poke
- 417.# Path to file which contains the record message
- 418.record_file = %apphome%config/server1/recordmessages.cfg
- 419.
- 420.# A comma separated list (without spaces) of server group ids, which should be watched on joining.
- 421.servergroupnotify_groups =
- 422.# A comma separated list (without spaces) of server group ids, which should be notified about joining clients.
- 423.servergroupnotify_grouptargets =
- 424.# A comma separated list (without spaces) of the total connection count (it's the same value as %CLIENT_TOTALCONNECTIONS% at the welcome message),
- 425.# when this message should be send to the clients. Set this to -1 to show it every time.
- 426.# Ranges like 1-100, -20 (means 20 or less) or 100- (means 100 or more) are also possible.
- 427.servergroupnotify_showonconnectionnumber = -1
- 428.# A comma separated list (without spaces) of channel ids.
- 429.# Depends on the given mode, target clients in this channels can be ignored or only clients in this channels receive the notify message!
- 430.# If no channels should be ignored, set no channels here and select the channel list mode ignore!
- 431.servergroupnotify_channel_list =
- 432.# Select one of the two modes for the channel list.
- 433.# ignore = Clients in the selected channels will be ignored.
- 434.# only = Only clients in the selected channels receive the notify message.
- 435.servergroupnotify_channel_list_mode = ignore
- 436.# Select the message mode, how the notified clients should get the message.
- 437.# poke, chat or none are valid values!
- 438.servergroupnotify_message_mode = poke
- 439.# Select the message mode, how the clients (who joined the server) should get the message.
- 440.# poke, chat or none are valid values!
- 441.servergroupnotify_messagenotified_mode = none
- 442.# Path to file which contains the server group notify message
- 443.servergroupnotify_file = %apphome%config/server1/servergroupnotifymessages.cfg
- 444.
- 445.# A comma separated list (without spaces) of server group ids, which should be protected.
- 446.servergroupprotection_groups =
- 447.# Enable this to kick every client which using a protected server group and are not on the list of the bot, set yes or no here!
- 448.servergroupprotection_kick = yes
- 449.# Add complaint entry to the user, set yes or no here!
- 450.# This would only add a complaint, if the bot has to remove a server group.
- 451.servergroupprotection_add_complain = no
- 452.# If a client is listed in the servergroupprotection_file and miss a server group, they get added to the server group.
- 453.# This only works for normal server groups (clients do not get added to groups like Admin Server Query)! Set yes or no here!
- 454.servergroupprotection_add_missing_groups = yes
- 455.# A comma separated list (without spaces) of server group ids, which are also allowed to use the add and remove chat commands.
- 456.# Bot admins can always use this commands!
- 457.servergroupprotection_chatcmd_group_list =
- 458.# Select the message mode, how the client should get the message (useless if kick is enabled).
- 459.# poke, chat or none are valid values!
- 460.servergroupprotection_message_mode = poke
- 461.# Path to file which contains the Server Group Protection client list and kick message.
- 462.servergroupprotection_file = %apphome%config/server1/servergroupprotection.cfg
- 463.
- 464.# A comma separated list (without spaces) of server group ids.
- 465.# Depends on the given mode, this server groups can be ignored or only this server groups get this welcome message!
- 466.# If no server groups should be ignored, set no server groups here and select the group list mode ignore!
- 467.welcome_group_list =
- 468.# Select one of the two modes for the server group list.
- 469.# ignore = The selected server groups will be ignored and don't get this welcome message.
- 470.# only = Only the selected server groups get this welcome message.
- 471.welcome_group_list_mode = ignore
- 472.# A comma separated list (without spaces) of the total connection count (it's the same value as %CLIENT_TOTALCONNECTIONS% at the welcome message),
- 473.# when this message should be send to the client. Set this to -1 to show it every time.
- 474.# Ranges like 1-100, -20 (means 20 or less) or 100- (means 100 or more) are also possible.
- 475.welcome_showonconnectionnumber = -1
- 476.# A comma separated list (without spaces) of platform names (it's the same value as %CLIENT_PLATFORM% at the welcome message).
- 477.# Only selected platforms get the welcome message or leave this empty to send the welcome message to all platforms.
- 478.# Possible platforms: Windows, Mac, Linux, Android, iOS
- 479.welcome_platform_list =
- 480.# Select the message mode, how the client should get the message.
- 481.# poke or chat are valid values!
- 482.welcome_message_mode = none
- 483.# Path to file which contains the welcome message.
- 484.welcome_file = %apphome%config/server1/welcomemessages.cfg
- 485.
- 486.# A comma separated list (without spaces) of server group ids.
- 487.# Depends on the given mode, this server groups can be ignored or only this server groups get this welcome message!
- 488.# If no server groups should be ignored, set no server groups here and select the group list mode ignore!
- 489.welcome_guest_group_list =
- 490.# Select one of the two modes for the server group list.
- 491.# ignore = The selected server groups will be ignored and don't get this welcome message.
- 492.# only = Only the selected server groups get this welcome message.
- 493.welcome_guest_group_list_mode = ignore
- 494.# A comma separated list (without spaces) of the total connection count (it's the same value as %CLIENT_TOTALCONNECTIONS% at the welcome message),
- 495.# when this message should be send to the client. Set this to -1 to show it every time.
- 496.welcome_guest_showonconnectionnumber = -1
- 497.# A comma separated list (without spaces) of platform names (it's the same value as %CLIENT_PLATFORM% at the welcome message).
- 498.# Only selected platforms get the welcome message or leave this empty to send the welcome message to all platforms.
- 499.# Possible platforms: Windows, Mac, Linux, Android, iOS
- 500.welcome_guest_platform_list =
- 501.# Select the message mode, how the client should get the message.
- 502.# poke or chat are valid values!
- 503.welcome_guest_message_mode = none
- 504.# Path to file which contains the welcome message.
- 505.welcome_guest_file = %apphome%config/server1/welcomemessages.cfg
Advertisement
Add Comment
Please, Sign In to add comment
Advertisement