diff --git a/JTS3Config/.gitignore b/JTS3Config/.gitignore
new file mode 100644
index 0000000..333c1e9
--- /dev/null
+++ b/JTS3Config/.gitignore
@@ -0,0 +1 @@
+logs/
diff --git a/JTS3Config/JTS3ServerMod_server.cfg b/JTS3Config/JTS3ServerMod_server.cfg
new file mode 100644
index 0000000..6f5b3e8
--- /dev/null
+++ b/JTS3Config/JTS3ServerMod_server.cfg
@@ -0,0 +1,346 @@
+# Config file of the JTS3ServerMod
+# http://www.stefan1200.de
+# This file must be saved with the encoding ISO-8859-1!
+# File created at 2015-04-30 14:05:59
+
+# Teamspeak 3 server address
+ts3_server_address = magic.adam-ant.co.uk
+# Teamspeak 3 server query port, default is 10011
+ts3_server_query_port = 10011
+# Teamspeak 3 server query admin account name
+ts3_server_query_login = selfserve
+# Teamspeak 3 server query admin password
+ts3_server_query_password = KaZRc+Yb
+# Teamspeak 3 virtual server ID or -1 to use ts3_virtualserver_port
+ts3_virtualserver_id = 1
+# Teamspeak 3 virtual server port, only needed if ts3_virtualserver_id is set to -1
+ts3_virtualserver_port = 9987
+
+# Channel id, the bot will join into it after connecting. If not wanted, use a negative number like -1.
+# Don't set the default channel here, because the bot is already in the default channel after connecting.
+bot_channel_id = -1
+# Activate the slow mode of the bot, 0 = disable, 1 = enable.
+# If slow mode is activated, the bot connects slower to the server
+# and disables some bot features to reduce the amount of needed commands.
+# This feature may allow you to use the bot without whitelist the bot IP address.
+# Slow mode disables the bad channel name check, channel notify, client auto move, client database cache,
+# server group notify, welcome message and do not allow the bot check interval to be lower than 3 seconds.
+bot_slowmode = 0
+# Check every X seconds, default is 1. Values between 1 and 30 are allowed.
+# If slow mode is activated, 3 is the lowest possible value.
+bot_check_interval = 1
+# A different encoding of the messages config files.
+# Default is UTF-8 which should be good for all EU and US languages.
+# Change this only if you know what you are doing!
+# For English or German language you can also use the encoding ISO-8859-1
+# A list of all valid ones: http://java.sun.com/j2se/1.5.0/docs/guide/intl/encoding.doc.html
+bot_messages_encoding = UTF-8
+# This enables the client database list cache. This cache is needed for commands like !lastseen. 1 = Enable, 0 = Disable
+bot_clientdblist_cache = 1
+# This enables the global message variables. See readme file for a list of variables. 1 = Enable, 0 = Disable
+# If enabled, you can use all server variables in all messages. If not needed, disable this to save performance.
+bot_global_message_vars = 0
+# Server Query name, this will be displayed as name of the connection.
+bot_server_query_name = AprilFoolsBot
+# Second Server Query name, this will be displayed as name of the connection.
+# This name will be used, if the first name is already in use.
+bot_server_query_name_2 = ClockworkBot2
+# Change the date pattern, which will be used to format a date in chat functions and welcome message.
+# To get help how to make such a pattern, look here: http://java.sun.com/j2se/1.5.0/docs/api/java/text/SimpleDateFormat.html
+bot_date_pattern = yyyy-MM-dd HH:mm:ss
+# Should the bot try to connect forever if the Teamspeak server or the bot is offline? 0 = disable, 1 = enable
+bot_connect_forever = 1
+# 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
+# Minimum log level, how much details you want to be written to the bot log files? Default is 1.
+# 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.
+# 0 = Debug
+# 1 = Information (recommended and default)
+# 2 = Warning (recommended for smaller log files)
+# 3 = Error (experts only)
+bot_log_level = 1
+# A comma separated list (without spaces) of unique user ids, which should be able to use bot admin commands.
+# The unique user ids looks like this: mBbHRXwDAG7R19Rv3PorhMwbZW4=
+bot_admin_list =
+
+# Set a comma separated list (without spaces) of needed bot functions here.
+# Each function needs the function class and the function name, both separated with a colon.
+# All possible function classes are listed below, that class is case sensitive!
+# 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.
+# Don't use spaces in the function names, only use letters, numbers, minus and underscore!
+# Most functions allow multiple usage, that allows you to set as many welcome messages or idle check rules, as you want.
+# Don't forget that you have to put all settings of the functions in this file.
+# Hint: Start the bot with the argument -updateconfig after adding bot functions, that writes the configuration for all functions into this file!
+# Whole command: java -jar JTS3ServerMod.jar -updateconfig
+# Notice: This -updateconfig will also delete all lines of removed or renamed functions in this config file!
+# For more information about the functions read documents/ConfigHelp.html or documents/ConfigHelp_deutsch.html!
+# Example: IdleCheck:idle,IdleCheck:idle_guest,MuteMover:mute,WelcomeMessage:welcome,WelcomeMessage:welcome_guest
+# This example gives you the following:
+# - Two IdleCheck with the name idle and idle_guest
+# - One MuteMover with the name mute
+# - Two WelcomeMessage with the name welcome and welcome_guest
+#
+# Function list (use only once!):
+# AutoMove - Move connecting clients of a specified server group to a specified channel
+# LastSeen - Chat command to check the last online time of a client (client database list cache must be enabled!)
+#
+# Function list (multiple use possible):
+# Advertising - Send messages to channel or server chat every X minutes
+# AwayMover - Move the client as soon as away status is set for longer than X seconds
+# BadChannelNameCheck - Checking for bad channel names, can delete the channel and punish the client
+# BadNicknameCheck - Checking for bad nicknames and can punish the client
+# ChannelNotify - Notify specified server groups about clients joining a specified channel
+# IdleCheck - Move or kick an idle client, can also send an idle warning message
+# InactiveChannelCheck - Delete channels if empty for more than X hours
+# MuteMover - Move the client as soon as the specified mute status is set for longer than X seconds
+# RecordCheck - Move or kick a recording client (of course only the record function of the Teamspeak client is detected)
+# ServerGroupNotify - Notify specified server groups about clients of specified server groups connecting to the TS3 server
+# ServerGroupProtection - Make sure that only specified clients are members of the specified server groups
+# WelcomeMessage - Sends a message to new connected clients
+bot_functions = AutoMove:automover,LastSeen:lastseen,AwayMover:away,BadChannelNameCheck:badchannelname,BadNicknameCheck:badname,IdleCheck:idle,MuteMover:mutemove,RecordCheck:recordmove,WelcomeMessage:welcome,Advertising:advert
+# Set a comma separated list (without spaces) of needed but disabled bot functions here.
+# Same format as bot_functions!
+# All functions you set here are not activated at bot start, but you can switch on functions using chat commands.
+bot_functions_disabled =
+
+
+# Select the message mode, how the clients should get the message.
+# poke, chat or none are valid values!
+automover_message_mode = chat
+# Path to file which contains the auto move configuration and message.
+automover_file = /data/automove.cfg
+
+# Who should be able to use the last seen command? Possible values: all, botadmin, servergroup
+# This command only works if the bot_clientdblist_cache is enabled!
+lastseen_user = botadmin
+# A comma separated list (without spaces) of server group ids.
+# Depends on the given mode, this server groups can be ignored or only this server groups will be allowed to use the !lastseen command!
+# This is only needed, if user servergroup is selected!
+lastseen_group_list =
+# Select one of the two modes for the server group list.
+# ignore = The selected server groups will be ignored.
+# only = Only the selected server groups are allowed to use the !lastseen command!
+lastseen_group_list_mode = ignore
+
+# Move client back if not away anymore? Set yes or no here!
+away_moveback = yes
+# Channel id to move away clients into it
+away_channel_id = 20
+# Idle time in seconds after the client with away status will be moved to the channel.
+# Has between 0 and 10000 seconds!
+away_delay = 30
+# A comma separated list (without spaces) of channel ids.
+# Depends on the given mode, this channels can be ignored or only this channels will be checked!
+# If no channels should be ignored, set no channels here and select the channel list mode ignore!
+away_channel_list =
+# Select one of the two modes for the channel list.
+# ignore = The selected channels will be ignored.
+# only = Only the selected channels will be checked.
+away_channel_list_mode = ignore
+# A comma separated list (without spaces) of server group ids.
+# Depends on the given mode, this server groups can be ignored or only this server groups will be checked!
+# If no server groups should be ignored, set no server groups here and select the group list mode ignore!
+away_group_list = 9
+# Select one of the two modes for the server group list.
+# ignore = The selected server groups will be ignored.
+# only = Only the selected server groups will be checked.
+away_group_list_mode = ignore
+# Select the message mode, how the client should get the message.
+# poke, chat or none are valid values!
+away_message_mode = chat
+# Path to file which contains the away mover message
+away_file = /data/awaymessages.cfg
+
+# Instantly kick client that creates a channel with a bad name? Set yes or no here!
+badchannelname_kick = no
+# Instantly delete a channel with a bad name? Set always, onlynew or no here!
+# 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!
+# no = Try to rename channel back, but the channel will not be deleted!
+badchannelname_delete = onlynew
+# A comma separated list (without spaces) of channel ids.
+# This channels will be ignored!
+badchannelname_channel_list =
+# Add complain entry to the user? Set yes or no here!
+badchannelname_add_complain = no
+# A comma separated list (without spaces) of server group ids.
+# Depends on the given mode, this server groups can be ignored or only this server groups will be checked!
+# If no server groups should be ignored, set no server groups here and select the group list mode ignore!
+badchannelname_group_list =
+# Select one of the two modes for the server group list.
+# ignore = The selected server groups will be ignored and can create channels with bad channel names.
+# only = Only the selected server groups will be checked.
+badchannelname_group_list_mode = ignore
+# Select the message mode, how the client should get the message.
+# poke, chat or none are valid values!
+# If client kick is activated, the message will be always used as kick message!
+badchannelname_message_mode = poke
+# Path to file which contains the Bad Channel Name Check rules and the message.
+badchannelname_file = /data/badchannelname.cfg
+
+# Kick client with a bad nickname? Set yes or no here!
+badname_kick = yes
+# Add complain entry to the user? Set yes or no here!
+badname_add_complain = no
+# A comma separated list (without spaces) of server group ids.
+# Depends on the given mode, this server groups can be ignored or only this server groups will be checked!
+# If no server groups should be ignored, set no server groups here and select the group list mode ignore!
+badname_group_list =
+# Select one of the two modes for the server group list.
+# ignore = The selected server groups will be ignored and can have bad nicknames.
+# only = Only the selected server groups will be checked.
+badname_group_list_mode = ignore
+# Select the message mode, how the client should get the message.
+# poke or chat are valid values!
+# If client kick is activated, the message will be always used as kick message!
+badname_message_mode = poke
+# Path to file which contains the bad nickname message and check rules.
+badname_file = /data/badnickname.cfg
+
+# Select the action if a client is idle for more than the specified maximum time, possible values: kick and move
+idle_action = move
+# If clients got moved, move client back if not idle anymore? Set yes or no here!
+idle_moveback = yes
+# If clients should be moved, set channel id to move idle clients into it.
+idle_channel_id = 20
+# A comma separated list (without spaces) of channel ids.
+# Depends on the given mode, this channels can be ignored or only this channels will be checked!
+# If no channels should be ignored, set no channels here and select the channel list mode ignore!
+idle_channel_list =
+# Select one of the two modes for the channel list.
+# ignore = The selected channels will be ignored.
+# only = Only the selected channels will be checked.
+idle_channel_list_mode = ignore
+# A comma separated list (without spaces) of server group ids.
+# Depends on the given mode, this server groups can be ignored or only this server groups will be checked!
+# If no server groups should be ignored, set no server groups here and select the group list mode ignore!
+idle_group_list = 9,12
+# Select one of the two modes for the server group list.
+# ignore = The selected server groups will be ignored.
+# only = Only the selected server groups will be checked.
+idle_group_list_mode = ignore
+# Set the max idle time in minutes.
+# If clients should be kicked, the client will be kicked after being idle for this time.
+# If clients should be moved, the client will be moved to specified channel after being idle for this time!
+idle_max_time = 20
+# If clients should be moved, set the max idle time in minutes to kick someone.
+# Has to be greater than idle_max_time or -1 to disable this feature!
+idle_second_max_time = -1
+# Set the idle warn time in minutes or set -1 to disable this feature.
+# The idle warn time has to be smaller than the max idle time
+idle_warn_time = -1
+# A minimum client count to activate idle check (telnet and TS3 clients counted together).
+# If less clients online, idle check does nothing.
+idle_min_clients = 2
+# If clients should be moved, select the message mode, how the client should get the message.
+# poke, chat or none are valid values!
+idle_message_mode = chat
+# Select the message mode, how the client should get the message.
+# poke or chat are valid values!
+idle_warn_message_mode = chat
+# Path to file which contains the idle messages
+idle_file = /data/idlemessages.cfg
+
+# Move client back if not muted anymore? Set yes or no here!
+mutemove_moveback = yes
+# Enable move if headphone is muted, yes or no
+mutemove_headphone = yes
+# Enable move if microphone is muted, yes or no
+mutemove_microphone = no
+# Enable move if headphone hardware is disabled, yes or no
+mutemove_headphone_hardware = yes
+# Enable move if microphone hardware is disabled, yes or no
+# This also happen if someone is speaking in another TS3 client server tab.
+mutemove_microphone_hardware = no
+# Move the client if the client has all selected conditions or at least one? Set all or one here!
+mutemove_condition_mode = one
+# Channel id to move muted clients into it
+mutemove_channel_id = 20
+# Idle time in seconds after the client with a specified mute status will be moved to the channel.
+# Has between 0 and 10000 seconds!
+mutemove_delay = 120
+# A comma separated list (without spaces) of channel ids.
+# Depends on the given mode, this channels can be ignored or only this channels will be checked!
+# If no channels should be ignored, set no channels here and select the channel list mode ignore!
+mutemove_channel_list =
+# Select one of the two modes for the channel list.
+# ignore = The selected channels will be ignored.
+# only = Only the selected channels will be checked.
+mutemove_channel_list_mode = ignore
+# A comma separated list (without spaces) of server group ids.
+# Depends on the given mode, this server groups can be ignored or only this server groups will be checked!
+# If no server groups should be ignored, set no server groups here and select the group list mode ignore!
+mutemove_group_list = 9,12
+# Select one of the two modes for the server group list.
+# ignore = The selected server groups will be ignored.
+# only = Only the selected server groups will be checked.
+mutemove_group_list_mode = ignore
+# Select the message mode, how the client should get the message.
+# poke, chat or none are valid values!
+mutemove_message_mode = chat
+# Path to file which contains the mute mover message
+mutemove_file = /data/mutemessages.cfg
+
+# Select the action if a client starts recording, possible values: kick and move
+recordmove_action = move
+# If clients should be moved, set channel id to move recording clients into it
+recordmove_channel_id = 20
+# A comma separated list (without spaces) of channel ids.
+# Depends on the given mode, this channels can be ignored or only this channels will be checked!
+# If no channels should be ignored, set no channels here and select the channel list mode ignore!
+recordmove_channel_list =
+# Select one of the two modes for the channel list.
+# ignore = The selected channels will be ignored.
+# only = Only the selected channels will be checked.
+recordmove_channel_list_mode = ignore
+# A comma separated list (without spaces) of server group ids.
+# Depends on the given mode, this server groups can be ignored or only this server groups will be checked!
+recordmove_group_list = 9,12
+# Select one of the two modes for the server group list.
+# ignore = The selected server groups will be ignored and are allowed to record.
+# only = Only the selected server groups will be checked and punished, if they start recording.
+# If no server groups should be ignored, set no server groups here and select the group list mode ignore!
+recordmove_group_list_mode = ignore
+# A comma separated list (without spaces) of channel group ids.
+# Depends on the given mode, this channel groups can be ignored or only this channel groups will be checked!
+# If no channel groups should be ignored, set no channel groups here and select the group list mode ignore!
+recordmove_channelgroup_list =
+# Select one of the two modes for the channel group list.
+# ignore = The selected channel groups will be ignored and are allowed to record.
+# only = Only the selected channel groups will be checked and punished, if they start recording.
+recordmove_channelgroup_list_mode = ignore
+# Add complain entry to the user? Set yes or no here!
+recordmove_add_complain = yes
+# If clients should be moved, select the message mode, how the client should get the message.
+# poke, chat or none are valid values!
+recordmove_message_mode = poke
+# Path to file which contains the record message
+recordmove_file = /data/recordmessages.cfg
+
+# A comma separated list (without spaces) of server group ids.
+# Depends on the given mode, this server groups can be ignored or only this server groups get this welcome message!
+# If no server groups should be ignored, set no server groups here and select the group list mode ignore!
+welcome_group_list = 9
+# Select one of the two modes for the server group list.
+# ignore = The selected server groups will be ignored and don't get this welcome message.
+# only = Only the selected server groups get this welcome message.
+welcome_group_list_mode = ignore
+# A comma separated list (without spaces) of the total connection count (it's the same value as %CLIENT_TOTALCONNECTIONS% at the welcome message),
+# when this message should be send to the client. Set this to -1 to show it every time.
+welcome_showonconnectionnumber = -1
+# Select the message mode, how the client should get the message.
+# poke or chat are valid values!
+welcome_message_mode = poke
+# Path to file which contains the welcome message.
+welcome_file = /data/welcomemessages.cfg
+
+
+# Is the target of the advertising messages a channel or a server? Possible values (just write one of the both words!): channel or server
+advert_mode = server
+# If a channel is the target, set channel id to write advertising message into it
+advert_channel_id = 
+# Advertise every X minutes
+advert_repeat_time = 30
+# Path to file which contains the advertising messages
+advert_file = /data/advertising.cfg
diff --git a/JTS3Config/README.md b/JTS3Config/README.md
new file mode 100644
index 0000000..ec95b52
--- /dev/null
+++ b/JTS3Config/README.md
@@ -0,0 +1,3 @@
+# teamspeak-configs
+
+JTS3Bot configs for Clcokwork Gaming Server
diff --git a/JTS3Config/advertising.cfg b/JTS3Config/advertising.cfg
new file mode 100644
index 0000000..2215b3e
--- /dev/null
+++ b/JTS3Config/advertising.cfg
@@ -0,0 +1,5 @@
+# JTS3ServerMod Config File
+# Each line which not start with # is a new advertising message.
+# The bot write this messages in the order from top to bottom and start from top again.
+# Typical BBCode like in Teamspeak 3 Client possible. You can use \n for a new line.
+Hey! Have you tried Clockwork PLUS! yet?\n[URL]http://www.cwgaming.co.uk/plus[/URL]
diff --git a/JTS3Config/automove.cfg b/JTS3Config/automove.cfg
new file mode 100644
index 0000000..cd8649f
--- /dev/null
+++ b/JTS3Config/automove.cfg
@@ -0,0 +1,10 @@
+# JTS3ServerMod Config File
+# The first line is the chat message for the auto move function.
+# You can use the following keywords, which will be replaced:
+# %CHANNEL_NAME% - Target Channel Name
+# Typical BBCode like in Teamspeak 3 Client possible. You can use \n for a new line.
+You was moved to your default channel!
+
+# This is the list of server groups, which will be moved to a specified channel.
+# One line per server group starting with the server group id, followed by a comma, and ends with the channel id.
+
diff --git a/JTS3Config/awaymessages.cfg b/JTS3Config/awaymessages.cfg
new file mode 100644
index 0000000..e2bbc87
--- /dev/null
+++ b/JTS3Config/awaymessages.cfg
@@ -0,0 +1,6 @@
+# JTS3ServerMod Config File
+# Away Mover message, the client get this message as chat message.
+# You can use the following keywords, which will be replaced:
+# %AWAY_CHANNEL_NAME% - This will be replaced with the name of the specified channel
+# Typical BBCode like in Teamspeak 3 Client possible. You can use \n for a new line.
+You were moved because you were away. Un-away to move back.
diff --git a/JTS3Config/badchannelname.cfg b/JTS3Config/badchannelname.cfg
new file mode 100644
index 0000000..0c217f9
--- /dev/null
+++ b/JTS3Config/badchannelname.cfg
@@ -0,0 +1,28 @@
+# JTS3ServerMod Config File
+# Set message for using a bad channel name.
+# You can use the following keywords, which will be replaced:
+# %CHANNEL_NAME% - Bad Channel Name
+# You can use \n for a new line and typical BBCode like in Teamspeak 3 Client.
+The channel name %CHANNEL_NAME% is not allowed!
+
+# Set bad channel name rules here. One rule per line. Use regular expressions for the rules.
+# This rules will be used case-insensitive.
+# The following link give you some informations about regular expressions in java:
+# http://docs.oracle.com/javase/1.5.0/docs/api/java/util/regex/Pattern.html
+# Important: If you are not sure, test your regular expressions on the following page:
+# http://www.rubular.com or http://regexp-evaluator.de/evaluator/
+# Or the bot may delete all channels, if you do something wrong!
+#
+# nigger and some variations
+.*n[i!1](g|gg)er.*
+# hitler and some variations
+.*h[i!1]tler.*
+# nazi and some variations
+.*n[a@]z[i!1].*
+
+#Dick
+.*d[i|1]ck.*
+#Cunt
+.*cunt.*
+#Pussy
+.*pu[ss|zz]y.*
diff --git a/JTS3Config/badnickname.cfg b/JTS3Config/badnickname.cfg
new file mode 100644
index 0000000..44cd4a9
--- /dev/null
+++ b/JTS3Config/badnickname.cfg
@@ -0,0 +1,23 @@
+# JTS3ServerMod Config File
+# Set message for using a bad nickname.
+# You can use the following keywords, which will be replaced:
+# %CLIENT_NAME% - Client Name
+# You can use \n for a new line and typical BBCode like in Teamspeak 3 Client.
+This nickname is not allowed on this server!
+
+# Set bad nickname rules here. One rule per line. Use regular expressions for the rules.
+# This rules will be used case-insensitive.
+# The following link give you some informations about regular expressions in java:
+# http://java.sun.com/j2se/1.5.0/docs/api/java/util/regex/Pattern.html
+# Important: If you are not sure, test your regular expressions on the following page:
+# http://www.rubular.com or http://regexp-evaluator.de/evaluator/
+# Or the bot may kick all people, if you do something wrong!
+#
+# nigger and some variations
+.*n[i!1](g|gg)er.*
+# hitler and some variations
+.*h[i!1!ee]tler.*
+.*adolf.*
+.*hdolf.*
+# nazi and some variations
+.*n[a@]z[i!1].*
diff --git a/JTS3Config/channelnotifymessages.cfg b/JTS3Config/channelnotifymessages.cfg
new file mode 100644
index 0000000..d746258
--- /dev/null
+++ b/JTS3Config/channelnotifymessages.cfg
@@ -0,0 +1,28 @@
+# JTS3ServerMod Config File
+# Channel Notify message, specified clients get this message as chat or poke message.
+# You can use the following keywords, which will be replaced:
+# %CLIENT_NAME% - Client Name
+# %CLIENT_NAME_CLICKABLE% - Clickable client name (many characters, not useful for poke messages!)
+# %CLIENT_DBID% - Client Database ID
+# %CLIENT_UNIQUEID% - Client Unique ID
+# %CHANNEL_NAME% - Watched Channel Name
+# %CHANNEL_NAME_CLICKABLE% - Clickable watched Channel Name (many characters, not useful for poke messages!)
+# Typical BBCode like in Teamspeak 3 Client possible. You can use \n for a new line.
+Client [b]%CLIENT_NAME%[/b] (DB ID: %CLIENT_DBID%) joined channel %CHANNEL_NAME%!
+
+# Channel Notify message for the watched client.
+# If enabled, clients joining the watched channel get this message as chat or poke message.
+# You can use the following keywords, which will be replaced:
+# %CLIENT_COUNT% - Number of target group clients who get informed about this client
+# %CLIENT_NAMES% - List of names of target group clients who get informed about this client
+# %CLIENT_NAMES_CLICKABLE% - List of clickable client names of target group clients who get informed about this client (many characters, not useful for poke messages!)
+# %CHANNEL_NAME% - Watched Channel Name
+# Typical BBCode like in Teamspeak 3 Client possible. You can use \n for a new line.
+Please wait in channel %CHANNEL_NAME%, %CLIENT_COUNT% people are online to help you.
+
+# Channel Notify message for the watched client, if no target group client is online.
+# If enabled, clients joining the watched channel get this message as chat or poke message.
+# You can use the following keywords, which will be replaced:
+# %CHANNEL_NAME% - Watched Channel Name
+# Typical BBCode like in Teamspeak 3 Client possible. You can use \n for a new line.
+Currently no admins are online, please write us an email or wait in channel %CHANNEL_NAME%.
\ No newline at end of file
diff --git a/JTS3Config/idlemessages.cfg b/JTS3Config/idlemessages.cfg
new file mode 100644
index 0000000..cdaff79
--- /dev/null
+++ b/JTS3Config/idlemessages.cfg
@@ -0,0 +1,22 @@
+# JTS3ServerMod Config File
+# Idle message, the client get this message as kick reason (on kick) or chat message (on move).
+# You can use the following keywords, which will be replaced:
+# %IDLE_MAX_TIME% - Replaced with max idle time
+# %IDLE_CHANNEL_NAME% - After moving client this will be replaced with the channel name
+# Typical BBCode like in Teamspeak 3 Client possible. You can use \n for a new line.
+You are now idle for more than %IDLE_MAX_TIME% minutes, you got moved to the channel "%IDLE_CHANNEL_NAME%"!
+
+# If move is enabled, set the kick reason for being idle longer than second max idle time.
+# You can use the following keywords, which will be replaced:
+# %IDLE_MAX_TIME% - Replaced with max idle time
+# %IDLE_SECOND_MAX_TIME% - This will be replaced with the second idle max time
+# Typical BBCode like in Teamspeak 3 Client possible. You can use \n for a new line.
+You got kicked because being idle for longer than %IDLE_SECOND_MAX_TIME% minutes.
+
+# Idle warning message, the client get this message as chat message.
+# You can use the following keywords, which will be replaced:
+# %IDLE_WARN_TIME% - Replaced with idle warn time
+# %IDLE_MAX_TIME% - Replaced with max idle time
+# %IDLE_CHANNEL_NAME% - After moving client this will be replaced with the channel name
+# Typical BBCode like in Teamspeak 3 Client possible. You can use \n for a new line.
+You are already since %IDLE_WARN_TIME% minutes idle. If you are %IDLE_MAX_TIME% minutes idle, you will be moved to channel "%IDLE_CHANNEL_NAME%"!
diff --git a/JTS3Config/mutemessages.cfg b/JTS3Config/mutemessages.cfg
new file mode 100644
index 0000000..45f973f
--- /dev/null
+++ b/JTS3Config/mutemessages.cfg
@@ -0,0 +1,6 @@
+# JTS3ServerMod Config File
+# Mute Mover message, the client get this message as chat message.
+# You can use the following keywords, which will be replaced:
+# %MUTE_CHANNEL_NAME% - This will be replaced with the name of the specified channel
+# Typical BBCode like in Teamspeak 3 Client possible. You can use \n for a new line.
+You were moved to channel "%MUTE_CHANNEL_NAME%" because your client status is muted. You will be moved back if your client status is not muted anymore.
diff --git a/JTS3Config/recordmessages.cfg b/JTS3Config/recordmessages.cfg
new file mode 100644
index 0000000..43bb24c
--- /dev/null
+++ b/JTS3Config/recordmessages.cfg
@@ -0,0 +1,6 @@
+# JTS3ServerMod Config File
+# Set a record message. On both modes the client should see the message.
+# You can use the following keywords, which will be replaced:
+# %RECORD_CHANNEL_NAME% - After moving client this will be replaced with the channel name
+# Typical BBCode like in Teamspeak 3 Client possible. You can use \n for a new line.
+Do not record here!
diff --git a/JTS3Config/servergroupnotifymessages.cfg b/JTS3Config/servergroupnotifymessages.cfg
new file mode 100644
index 0000000..5c8e29d
--- /dev/null
+++ b/JTS3Config/servergroupnotifymessages.cfg
@@ -0,0 +1,25 @@
+# JTS3ServerMod Config File
+# Server Group Notify message, specified clients get this message as chat or poke message.
+# You can use the following keywords, which will be replaced:
+# %SERVER_GROUP_ID% - Server Group ID
+# %SERVER_GROUP_NAME% - Server Group Name
+# %CLIENT_NAME% - Client Name
+# %CLIENT_NAME_CLICKABLE% - Clickable client name (many characters, not useful for poke messages!)
+# %CLIENT_DBID% - Client Database ID
+# %CLIENT_UNIQUEID% - Client Unique ID
+# Typical BBCode like in Teamspeak 3 Client possible. You can use \n for a new line.
+Client [b]%CLIENT_NAME%[/b] of the server group [b]%SERVER_GROUP_NAME%[/b] joined server!
+
+# Server Group Notify message for the watched client.
+# If enabled, clients with a watched server group connecting the server get this message as chat or poke message.
+# You can use the following keywords, which will be replaced:
+# %CLIENT_COUNT% - Number of target group clients who get informed about this client
+# %CLIENT_NAMES% - List of names of target group clients who get informed about this client
+# %CLIENT_NAMES_CLICKABLE% - List of clickable client names of target group clients who get informed about this client (many characters, not useful for poke messages!)
+# Typical BBCode like in Teamspeak 3 Client possible. You can use \n for a new line.
+Please wait, %CLIENT_COUNT% people are online to help you: %CLIENT_NAMES%
+
+# Server Group Notify message for the watched client, if no target group client is online.
+# If enabled, clients with a watched server group connecting the server get this message as chat or poke message.
+# Typical BBCode like in Teamspeak 3 Client possible. You can use \n for a new line.
+Currently no admins are online, please write us an email.
\ No newline at end of file
diff --git a/JTS3Config/servergroupprotection.cfg b/JTS3Config/servergroupprotection.cfg
new file mode 100644
index 0000000..154456b
--- /dev/null
+++ b/JTS3Config/servergroupprotection.cfg
@@ -0,0 +1,15 @@
+# JTS3ServerMod Config File
+# The first line is the kick or chat message for the server group protection.
+# You can use the following keywords, which will be replaced:
+# %SERVER_GROUP_ID% - Replaced with the server group id.
+# %SERVER_GROUP_NAME% - Replaced with the server group name.
+# Typical BBCode like in Teamspeak 3 Client possible.
+The server group [b]%SERVER_GROUP_NAME%[/b] is protected!
+
+# This is the list of allowed clients in the protected server groups.
+# One line per client starting with the server group id, followed by a comma,
+# and ends with the unique id of the client.
+# If a client is member of two protected groups, make two lines with the
+# same unique id, but different server group id.
+# An example (please remove this example after you understand it):
+6,mBbHRXwDAG7R19Rv3PorhMwbZW4=
\ No newline at end of file
diff --git a/JTS3Config/welcomemessages.cfg b/JTS3Config/welcomemessages.cfg
new file mode 100644
index 0000000..79a246b
--- /dev/null
+++ b/JTS3Config/welcomemessages.cfg
@@ -0,0 +1,18 @@
+# JTS3ServerMod Config File
+# Set welcome message. You can use \n for a new line and typical BBCode like in Teamspeak 3 Client.
+# You can use the following keywords, which will be replaced:
+# %CLIENT_ID% - Current client ID on the server
+# %CLIENT_DATABASE_ID% - Client database ID
+# %CLIENT_UNIQUE_ID% - Unique client ID
+# %CLIENT_COUNTRY% - Short name of the client country, detected by the TS3 server
+# %CLIENT_NICKNAME% - Nickname of the client
+# %CLIENT_VERSION% - Client version
+# %CLIENT_PLATFORM% - Client platform (Windows, Linux, ...)
+# %CLIENT_IP% - Client IP address, bot needs permission b_client_remoteaddress_view for this!
+# %CLIENT_CREATED% - Date and time of the first connection of the client
+# %CLIENT_TOTALCONNECTIONS% - Total connection count of the client
+# %CLIENT_MONTH_BYTES_UPLOADED% - Uploaded data in current month (filetransfer and avatar)
+# %CLIENT_MONTH_BYTES_DOWNLOADED% - Downloaded data in current month (filetransfer and avatar)
+# %CLIENT_TOTAL_BYTES_UPLOADED% - Uploaded data all times (filetransfer and avatar)
+# %CLIENT_TOTAL_BYTES_DOWNLOADED% - Downloaded data all times (filetransfer and avatar)
+Hello %CLIENT_NICKNAME%, a user of %CLIENT_PLATFORM, from %CLIENT_IP%!\nCheck out Clockwork PLUS!.\n[URL]www.cwgaming.co.uk/plus[/URL]\nWe know everything about you... :>