I've noticed that shutdown performed poorly in some edge-cases which lead to me finding some small memory leaks.

Due to a small error while calling the DebugLogger, said was not working properly which resulted in it not being called

Due to a down time of http://checkip.amazonaws.com/ the Metricshandler couldn't fetch its hosts ip which lead to errors in the console. I decided to build my own ipcheck service and update the Metricshandler

This update mainly consists of a major bugfix for bungeecord which disabled the autoupdater and the updatechecker

This is just a small patch for the UpdateChecker. It should now not spam anymore

I tried patching a small error that sometimes occurred

added AutoUpdater
improved DebugLogger

This update contains a fix for shutdown-bungee which should reenable the use of the timedshutdown

This update is only necessary for people who use the Plugin for BungeeCord

I just fixed some bugs I myself encountered

- improved debugging
- added cooldown to version command when executed from console
- bugfixes

This update contains:
- a scheduled shutdown every day
- many bugfixes

forgot to change the version in the last update for the UpdateChcker

fixed error in plugin.yml

fixed some issues

- added UpdateChecker back to PaperSpigot
- added Custom ServerShutDownEvent wich can be called in your Plugins
- added /shutdown rl command
- added /shutdown terminate
- changed /shutdown --now to /shutdown now
- added /shutdown version
- splitted config.yml and messages.yml

Due an Issue which I currently don't know how to fix i had to disable the UpdateChecker on any PaperSpigot version

I also added a new setting to the config.yml where you can disable the UpdateChecker if you want to.

- removed typo in config.yml
- added %s% variable to 'chat.broadcastmsg'

added help cmd and improved some small features

Some small changes to the ux

- Implemented stopping BungeeCord from cli

In this version I added the BungeeCord Version of Shutdown.
As before if you get Errors please report them to me, that I can fix them

fixed the /shutdown --now command

Now you really can stop the server from console

You can now use the Command form console

This version contains a fully customizable shutdown timer.

For example:

/shudown 19: Stops the Server in 19 seconds

/shutdown < 10 or /shutdown: stops the server in 10 seconds

Fixed some issues.

Just a little optimization in the config.yml

The Config.yml Colorcode Bug got fixed in this Update

WHILE STOP:
Your users are now getting a Kick message that is fully customizable!

COMMAND :
/shutdown --now ~ This Command stops ur Server immediately.

Changelog:

This Update includes a lot of new features.

Command:

Commandextention:
/shutdown 10-60 You can now choose between the standard 10 seconds or a Number up to 60 seconds. Example: /shutdown 30

Config.yml

Config.yml was added.