Bukkit

This changelog concern versions from 0.5 to 1.03

MaintenanceManager 1.03

• Fixed a bug that made the duration thread do not run if the schedule value equaled to 0.
• Fixed a bug that occured when you typed /maint on 0
• Fixed an error that occured when you scheduled you maintenance with underterminated duration.
• Fixed a bug that made the schedule launch even if the duration value was wrong.
• Remove API unsued classes.

MaintenanceManager 1.02

• No more help.yml in the plugin data folder.
• The maintenance icon is now read from a file into the main folder of the server. (maintenance-icon.png)
• If no maintenance-icon.png can be found in the main folder of the server, the default one would be created and used.
• Added a security when a maintenance is scheduled: You can't anymore schedule or simply activate the maintenance mode until a schedule is up.
• Fixed a bug with two threads (schedule one and duration one)
• Added very long durations support.

MaintenanceManager 1.01

• Replaced an ugly error message by a nice looking help message. (Not customizable)

MaintenanceManager 1.0

Official release yay!

• Improved code
• Mistakes fixed
• Some bugs fixed
• Maintenance duration and schedule fixed.
• Backups are now threaded. That means that the server would lag less during backing up.
• Default config.yml includes now colors.

MaintenanceManager 0.8

• Backup command doesn't any longer saves previous backups.
• SigarSmoke isn't required anymore to make /cpu and /ram commands working! However, dlls are always required.

MaintenanceManager 0.72

• Fixed backup again! You can now use the command several time without taking 100% of your disk space and without make the server crash!

MaintenanceManager 0.71

• Fixed backups. Everything is now saved and servers weigthing more than 2Go are supported.
• Added world saving disabling during backup to prevent chunk slides.

MaintenanceManager 0.7

• Fixed a bug with motd when the maintenance had a duration.
• Fixed a bug with permissions.
• Added a command: /maintenance backup. (Not working properly for the moment, but you can still save some files).

MaintenanceManager 0.6

Please remove your MaintenanceManager folder before updating!

• New feature! Check out the server hardware at any time with /cpu and /ram commands!
• The administrator can define in the config.yml how much time the server would wait beore answering the /cpu and /ram command.
• Improved behavior for scheduling a maintenance with a duration. The last modification about this! Now it works fine.
• Added aliases to /maintenance command. You can now use /mmode or /maint. Thank you to @thequestingbeast for his suggestion!

• Note: Those two commands take a little time to perform because it requires to run external native code. Works only with Windows, Linux and MacOS.*
• Another note: You need to do something to make those commands work. Please read the instructions below.!*

Important: Please read carefully...

• SigarSmoke.jar and all sigar libraries are required to make /cpu and /ram possible. If you want a proof of what it is doing, check out the sources [here] (https://github.com/JeremGamer/Maintenance-Manager--CB-Plugin/tree/master/io/github/jeremgamer/sigarsmoke)!*

Run the server for the first time with MaintenanceManager and then try /cpu command. If it returns null ("CPU used at null%", highly probable), go to the config.yml and go to the section named "waitTime". The default value is 650 (milliseconds). Increase this value until the /cpu and /ram commands work properly. Caution, the value must be an integer! You can modify it without having to restart or reload the server using /maintenance reload. Then, delete smokeAnswer.yml each time your try fails.

MaintenanceManager 0.52

Caution, this version might be unstable!

Please remove your MaintenanceManager folder before updating!

• New feature! Check out the server hardware at any time with /cpu and /ram commands!
• The administrator can define in the config.yml how much time the server would wait beore answering the /cpu and /ram command.
• Improved behavior for scheduling a maintenance with a duration. But the last modification on it will be in the next version. There's again something wrong...

Note: Those two commands take a little time to perform because it requires to run external native code. Works only with Windows, Linux and MacOS. Another note: You'll see a lot of new files in the MaintenanceManager folder, please dont' touch!

Important: Please read carefully the instructions below...

SigarSmoke.jar is required to make /cpu and /ram possible. If you want a proof of what it is doing, check out the sources [here] (https://github.com/JeremGamer/Maintenance-Manager--CB-Plugin/tree/master/io/github/jeremgamer/sigarsmoke)!

Run the server for the first time with MaintenanceManager and then try /cpu command. If it returns null ("CPU used at null%", highly probable), go to the config.yml and go to the section named "waitTime". The default value is 650 (milliseconds). Increase this value until the /cpu and /ram commands work properly. Caution, the value must be an integer!