API: Created a listener system for both Lag (TPS) and Memory watchers. Developers: to use this, see the API page. Listeners exist for asynchronous and synchronous execution.
API: Created getters for most of LagMeter's API, and made a few more methods public. I will be encapsulating LagMeter's classes even more in the future, so that the entire plugin will eventually comply with java standards.
API: Many of LagMeter's methods (most of them, actually) are now public and are available for developers to harness the powers of. This includes the new methods with 1.14.0.
Lag/mem listener command times can now have delays in the format that uptime commands do.
Log outputs will now have digit grouping and two decimal places (i.e. 3,635,252.55 and for everywhere that uses a full-stop as a digit grouping character, 3.645.211.755,15) when refering to TPS and memory.
Fixed (on accident) a NullPointerException which would occur when the plugin was disabled with logging disabled.
Added 'uptime commands' - commands to be run after a certain amount of time the server has run for. Can be set to recur. To use, add to your config (a command, followed by <>, followed by the time (w: weeks; d: days; h: hours; m: minutes; s: seconds):
UptimeCommands:commandList:-/stop<>7d12h
Fixed the ping command: it will no longer create massive tonnes of lag, but instead, the response will be a bit delayed instead of delaying the entire server thread if a high value is entered for the hops. In other words, you might use the command /ping 500 and it'll respond in about 20 minutes or so, but the server won't lag.
