LagMeter

Version 1.15.1

• API: Package structure has changed to com.webkonsept.minecraft.lagmeter. If your plugin relies on this one as a dependency, make sure you warn users not to update LagMeter until you update your references to this project.
• Fixed a bug where lag and memory watchers would fail to parse the command to run when the threshold is exceeded.
• Fixed default configuration values to reasonable values (down from 101% memory and 21 TPS, whoops - those were testing values!)
• Fixed silly error messages when an invalid timed command was set up.

Version 1.15.0

• API: LagMeter#getTPS() has been deprecated. The method will not be removed, but developers should cast to double when using any methods involving TPS (I forgot to deprecate some others, such as the ones on the lag/mem watchers). In 1.16, the TPS will be converted to a double value, so as to get a more accurate (and often faster) representation than a float.
• The /ping command now pings players instead of assuming google.com (unless performed from the console, where google.com will be used instead)
• Polling for TPS has been staggered until 1 minute and 15 seconds after the plugin starts. This change is to prevent bad data collection.
• Fixed an issue where the configuration would sometimes not load correctly.
• Fixed an issue where, when reloaded by the server or another plugin, the plugin would often fail to load its configuration correctly.
• Slight optimizations (removed a few unnecessary checks, etc).
• Converted back to Maven (not really a change that effects the plugin, but it is a change to the repository nevertheless).

Version 1.15.1 Bugs

• Claims to be 1.16.0.
• LagMaps are worded incorrectly.