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

Спойлер: список изменений с версии 5.5.5

Version 6.0.2 (27.02.2016)
+ InactiveChannelCheck now can ignore spacer channels like [cspacer].
o Fixed some error messages at the Bad Nickname Check and Bad Channel Name Check.

Version 6.0 - Updated package (24.02.2016)
+ New chat command at the AutoKickTimer plugin: time argument to know how long you are already online and when you will be kicked.
- Bugfix at the AutoKickTimer plugin: Fixed bug that it checked the kick timer every seconds. Only every 60 seconds was planned.
- Bugfix at the AutoKickTimer plugin: Plugin was compiled with target Java 8. Changed to target Java 5.
o Updated source code in the file documents/plugin_sources/AutoKickTimer_src.zip
o No changes to the JTS3ServerMod itself, still version 6.0 (15.01.2016).

Version 6.0 (15.01.2016)
+ Welcome Message has a new chat command. The old test command was renamed to vars and the new test command send you the current saved welcome message,
ignoring the show on connection number setting. (thx to SuiciniV)
+ Server Group Notify is now able to check the client connection count to decide if something has to be notifed. Works like at the Welcome Message. (thx to KGBGaming)
- Bugfix: Welcome Message show on connection number feature didn't worked correctly in some cases.
- Bugfix: Server Group Protection add and remove commands now write back an error message, if you try to add or remove someone to/from an unprotected server group.
- Bugfix: Version check works again, now the communication with the server is encrypted.
o Server Group Protection add and remove commands now also works for normal bot admins,
but can only add or remove someone from the normal server groups (and not the query or template groups).
o Almost all functions are now allowed while slow mode is activated. You only get a warning in the bot log now.
In general make sure that you don't use to much functions, if the bot is not whitelisted.
o Updated the documentation

Version 6.0 Beta 1 (28.12.2015)
+ Added plugin interface, which allows you to create own plugins using Java programming language.
More information about this in the file plugins\Readme_plugins.txt and plugins\Readme_plugins_deutsch.txt
+ Added an example plugin, which kicks all clients after a specified online time in minutes. Good for demo TS3 servers.
- Bugfix: Fixed a small possible bug since version 5.5.7, which might prevent writing detailed error messages
into the bot log while saving or loading the configuration after using the chat commands !botcfgcheck and !botcfgsave.
o Since this version the current API build is: 1

Version 5.5.7 (28.12.2015)
+ If an error occur while loading or saving the configuration, a stack trace with error message will be written to the bot log.
- Bugfix: Chat command add of the Server Group Protection had problems with the comments of the protected clients. (thx to InS)
In some situations the configuration of the Server Group Protection was saved wrong (missing entries or wrong comments).
It was also not possible to write comments with spaces using the add chat command (sometimes one single word is not enough).
Both problems are fixed now.
- Bugfix: If the bot is checking the configuration or updating the config file, no useless error messages should be visible now.
- Bugfix: !botcfgsave was not working correctly after the !botreload or !botreloadall command was used.

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).