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

Спойлер: changelog c версии 5.4.2

Version 5.5.5 (25.10.2015)
+ New way to create a Windows Service of the JTS3ServerMod. Now it is possible to stop the bot by stopping the service.
This new way is also compatible with Windows 10 (and should be also compatible with Windows 8, 8.1, Server 2012 and 2012 R2).
Check out the tools directory! Thanks to the team behind the tool procrun from Apache Commons!
- Bugfix: ChannelNotify throw a NullPointerException, if the AutoMove function was moving a client into the channel of ChannelNotify. Fixed now! (thx to Mischa F.)
o Path values can contain now the variable %apphome% which will be replaced with the environment variable app.home.
app.home will be set while starting the JTS3ServerMod as a Windows service created by my script.
But you can also set this app.home variable while adding the argument -Dapp.home=PATH_TO_JTS3SERVERMOD while starting the JTS3ServerMod.
If no app.home environment variable exists, it will be replaced with an empty string.
o Recreated JTS3ServerMod Windows executables with the current version of Launch4j (because of bugfixes).

Version 5.5.4 (11.07.2015)
+ The chat commands !clientsearch and !searchip are now able to show much more search results, if no joker character (*) was used (perfect match). (thx to Morthawt)
This makes it possible to get a list of names, if up to 19 clients have the same IP address or client name.
- Bugfix: The chat commands !clientsearch, !searchip, !getchannelid, !listinactivechannels and !listinactiveclients had problems with multibyte unicode characters
in client or channel names. Now the message length will be measured right and, if needed, use the limit for chat messages on TS3 servers now. (thx to Morthawt)
- Bugfix: Functions was not writing a warning message into the log, if a chat message with multibyte unicode characters was to long.
This had no effects for kick or poke messages.

Version 5.5.3 (10.07.2015)
+ Changed chat command !listinactiveclients again: Using without arguments it displays the most inactive clients. (thx to Morthawt)
With an argument it displays the least inactive clients which are at least X days inactive.

Version 5.5.2 (10.07.2015)
+ Changed chat command !listinactiveclients to show always the most inactive clients, even if to much was found. (thx to Morthawt)
Number of clients is limited by the maximum length of a chat message.

Version 5.5.1 (09.07.2015)
+ Idle Check min client count on server reimplemented using the new option min_clients_mode. (thx to Adrian G.)
Now you can choose if the min client count have to be on server or just in that channel.
- Bugfix: Bad Channel Name Check tried to poke or message a query client, if a query client created a channel with a bad name. (thx to ParaFAL)
o Idle Check min client count does not count query clients anymore! Only TS3 clients will be counted now.

Version 5.5 (06.07.2015)
! IdleCheck value min_clients does not count all clients on the server anymore. Now you set the min_clients in the channel.
! LastSeen and the !clientsearch chat command now works also if the Client Database Cache is disabled.
+ Special characters §+§ to split a long message into multiple messages. Usable for almost all functions, including Welcome Message.
Not working for the function Advertising and for kick messages.
This allows you to send more than 100 characters as poke message to one client by splitting it into multiple messages.
Example Welcome Message as poke message:
Hello Guy, this is a long greeting!§+§You are on the server and other statistics!§+§More information about the community.
This example will send three poke messages with each up to 100 characters possible.
+ Welcome Message configuration showonconnectionnumber allows now ranges like 1-100, -20 (means 20 or less) or 100- (means 100 or more).
+ New global message variable %SERVER_CLIENT_DB_COUNT% to get the full client count of the TS3 database.
+ InactiveChannelCheck now allows to check parent channels only. This allows to delete a whole tree of channels if all sub-channels are unused.
+ ServerGroupProtection now writes all current server group members into the configuration file, if no client was set.
As soon as one client is set for the server group, no more clients will be added to the configuration automatically.
+ ServerGroupProtection chat command add now allows the optional argument for a comment. So you can add a name to the unique id.
- Bugfix: Called activate method of functions while loading configuration initially after starting the bot (without TS3 server connection).
o Smaller updates to the documentation.

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.