Разные JTS3ServerMod - многофункциональный TS3 сервер бот 6.4.0

-= Changelog =-
Version 5.4.2 (18.01.2015)
- Bugfix: -updateconfig argument was not working since version 5.4. (thx to InseTTe93pl)
- Bugfix: Not every error message in log file had the right function name beside it.

Version 5.4.1 (01.01.2015)
- Bugfix at chat commands !botfunctionactivate and !botfunctiondisable, now they should work correctly.
- Bugfix: Function LastSeen was not working, if disabled at bot start.
o Happy new year :)

Version 5.4 (31.12.2014)
+ Chat commands !msgchannelgroup and !msgservergroup allows now more than one channel and server group id at once.
Just write a comma separated list of channel/server group ids without spaces. (thx to Morthawt)
+ New chat commands !botfunctionactivate and !botfunctiondisable to activate/disable bot functions on the fly. (thx to Jim O.)
+ Channel Notify function now have a new message keyword for clickable channel names in chat messages (only the message for supporters).
- Bugfix: Chat command !bothelp sometimes exceeds the maximum character count of chat messages. (thx to Dominik A. and Robert S.)
o Removed the word "final" from version string, because some people think that no new JTS3ServerMod versions will be released.
In future only the words beta or RC (release candidate) will be added, if it's a test version.
o New rules for bot names: Don't use spaces, only use letters, numbers, minus and underscore!

Version 5.3 Final - SILENT UPDATE (02.11.2014)
- Smaller fixes to the InstallWindowsService.cmd script.
o Added much information to the documentation.
o No changes to the bot itself, so no update notification.

Version 5.3 Final (27.10.2014)
o Some additions to the documentation.

Version 5.3 RC 3 (20.10.2014)
+ Chat commands !setchannelgroup, !removechannelgroups and !removeservergroups now also accept the client unique id.
Of course the client database id can be still used.
+ Chat command !clientsearch also accept the client unique id now. (thx to Morthawt)
But wildcards are not allowed for unique ids, only for client names!
- Bugfix: Chat command !setchannelgroup displayed wrong message if successful, fixed now!
- Bugfix: Chat command !removeservergroups attempted to remove the default server group, if a client had no server groups set. Fixed!
- Bugfix: Chat command !removechannelgroups didn't display a message if the client had no channel groups set. Fixed!
o Chat commands !msgchannelgroup and !msgservergroup ignore query clients now!
Write to me if you ever used this commands to send messages also to query clients!

Version 5.3 RC 2 (18.10.2014)
+ New chat command !botrename to rename the client name of the bot to another name temporary.
Without argument it renames the bot back to the default name from bot config.
+ Old InstanceManager log file will be also renamed to .old on bot start (an already existing .old file will be deleted).
The bot is starting with a clean InstanceManager log file. This should keep also this log file small.

Version 5.3 RC 1 (17.10.2014)
+ Bot log creation was changed completely!
Now there are log levels (DEBUG, INFO, WARNING, ERROR and CRITICAL), STATUS and EXCEPTION entries.
If you don't need the INFO messages, you can set a higher log level to keep your log files small and clean.
One column shows you now which function was adding that line.
Bot functions don't spam the log anymore if a permission is missing.
The error message because of TS3 error messages will be only written one time into the bot log.
+ Old log file will be renamed to .old on bot start (an already existing .old file will be deleted).
The bot is starting with a clean log file. This should keep the log files also small.
+ New message keywords for the functions Server Group Notify and Channel Notify.
%CLIENT_NAME_CLICKABLE% and %CLIENT_NAMES_CLICKABLE% creates clickable client name links for the TS3 client.
Check documents/ConfigHelp.html for more information.
+ New chat command !removeservergroups to remove all server groups of a client using the client database id.
+ Added update notification for new JTS3ServerMod versions.
Bot full admins get a chat message after connecting the TS3 server, if a new JTS3ServerMod version is available.
Disabled by default, enable it in the JTS3ServerMod_InstanceManager.cfg file.
- Bugfix: !execwait now shortens long messages to maximum TS3 chat message length.
- Bugfix: Function Server Group Notify was displaying a query client as admin.
o Chat commands !exec and !execwait now displays a better error message if a command was unable to execute.
o Chat commands !botreload and !botcfgcheck returns a better error message now if the bot configuration is invalid.
o More settings from JTS3ServerMod_InstanceManager.cfg file will be reloaded on !botinstancelistreload chat command.
The value bot_update_check needs a bot reload after changing to work.
The bot full admin list and exec command state are reloaded instantly after that command.
o The chat command !removechannelgroups uses now the internal cache for the server settings.
If you change the default channel group of your server you should wait some minutes before using this command.
o Smaller fixes to some INFO log messages. More functions now writes INFO log messages.

Version 5.2.4 Final (29.06.2014)
- Bugfix: NullPointerException at chat message creation fixed, if no message should be created. (thx to Solaris17)

Version 5.2.3 Final (17.06.2014)
- Bugfix: Fixed endless loop while connecting to the TS3 server because of missing query ban detection.

Version 5.2.2 Final (10.06.2014)
+ Chat commands !listinactivechannels and !getchannelid now accept a channel ID as argument.

Version 5.2.1 Final (10.06.2014)
- Bugfix: Fixed chat output of !listinactivechannels: Sometimes the message was too long and no answer was send. (thx to Morthawt)
- Bugfix: Another fix for !listinactivechannels: Missing message if no channel was found or the answer had empty lines.
- Bugfix: Chat command !botfunctionlist writes a better message if no function was loaded.
- Bugfix: Chat command !getchannelid: Missing message if no channel was found or missing because too long.
o The function Inactive Channel Check skips now channels with an invalid empty time from TS3 server. (thx to Morthawt)

Version 5.2 Final (09.06.2014)
+ New function: Inactive Channel Check - Delete channels if empty for more than X hours.
+ New chat command: !listinactivechannels - You get a list of empty channels (and the time since they are empty).
+ New aliases for some chat commands. Look at documents\ChatCommandHelp.html
- Chat command !botcfghelp now cut of very long help messages to maximum chat message length.
Sometimes the answer was missing because of a to long chat message, as an example: !botcfghelp bot_functions
o Internal Caches (Server Info, Channel List, Server Group List) will be updated now every minute (was 10 minutes).
This was important, because now many bot chat commands and functions need this caches.
o Updated documentation
o Reworked most help messages about bot chat commands (look at !bothelp chat command).

Version 5.1.1 Final (21.05.2014)
o Updated help text for config files and documentation. Not all changes in version 5.1 was well documented.

Version 5.1 Final (20.05.2014)
+ New global message variables can be enabled in the bot config file, look at bot_global_message_vars.
This allows you to use all server info variables from welcome message at all messages.
+ Channel Notify and Server Group Notify can send a message to the watched client, special message possible if no target group clients are online.
o Changed: Debug value will be reloaded on virtual bot instance reconnect. Need to use the !botinstancelistreload command first!
o Added an example config file to help you understanding the new stuff: JTS3ServerMod_server1_example.cfg
o Updated documentation

Version 5.0.6 Final (06.04.2014)
- Bugfix: Remove wrong TS3 events error output while using !botcfgsave command. (thx to PTZer0)
- Bugfix: ChannelNotify tried to send a message also to query clients, now only to real TS3 clients.
o Changed !botcfgset output, if you try to change a write protected value. (thx to PTZer0)

Version 5.0.5 Final (18.03.2014)
- Bugfix: Server Group Protection add and remove chat commands now works if function is disabled. (thx to SkullDrago)
- Bugfix: LastSeen now ignore spaces at the user setting. (thx to zrikz)

Version 5.0.4 Final (09.03.2014)
- Bugfix: LastSeen mode all was not working. (thx to Demianz)

Version 5.0.3 Final (03.03.2014)
+ Mute Mover has a new switch to select if all or just one condition is needed to get moved.

Version 5.0.2 Final (02.03.2014)
+ Welcome Message is now able to send a message only to clients with a specified total connection count.
If you set this to 1,2 the welcome message will only send to the first two connections to the server, but not later.
Important: This is based on the TS3 server value CLIENT_TOTALCONNECTIONS,
if the bot is not online while the first two connections, then the client never gets the message!
- Bugfix: Some Mute Mover combinations was not possible. (thx to Christian M.)

Version 5.0.1 Final (28.02.2014)
- Bugfix: Fixed some config reading issues with RecordCheck and IdleCheck. (thx to LordAnubis)

Version 5.0 Final (25.02.2014)
+ Added new bot admin chat command !searchip
+ Added last ip address to the output of the !clientsearch chat command
- Bugfix: Advertising and Welcome Message function was not reading the configuration correctly.

Version 5.0 RC 8 (22.02.2014)
o Updated documentation, completed German translation.
o Smaller code changes to the bot, no noticeable changes (I hope :)).

Version 5.0 RC 7 (19.02.2014)
- Bugfix: Both chat commands of the Server Group Protection function was not working correctly. (thx to Robert S.)
- Bugfix: Mute Mover delay was not read correctly from config file. (thx to Robert S.)
o Mute Mover change: If you now enable headphone and microphone mute within one function prefix,
both have now happen at the same time...