LagMeter 1.13.0

Details

  • Filename
    LagMeter.jar
  • Uploaded by
  • Uploaded
    Apr 4, 2013
  • Size
    25.15 KB
  • Downloads
    19,725
  • MD5
    8da29ce5cb78acc6433c2897125bca90

Supported Bukkit Versions

  • CB 1.5.1-R0.1

Changelog

Thank you for downloading, and please take the time to vote on the front page poll about whether or not the addition of PluginMetrics should happen. Thanks!

Version 1.13.0

  • Built with Bukkit for Minecraft 1.5.1 (R0.1).
  • Added /ping and /lping commands, where the server will ping google.com and thereafter return the resulting ping time in milliseconds to the player or console which used it. You may specify, if you have the necessary permission node, the amount of hops (packets) to send to google.com to test your ping, to get a better average result of ping time. Typing /ping 10 will check if the player has the necessary permission node, and if so, will ping google.com with 10 packets, averaging the times together, and returning that. This has a maximum of 10, as it becomes server-intensive soon after 3 or 4 hops. Pinging the player instead is possible, create a ticket if you'd like this to happen (it was deemed too expensive as far as memory goes for now).
  • Fixed a bug where LagMeter might display its tag twice.
  • Removed an unnecessary message telling the player they had no commands besides the help command, where that was already obvious.
  • Paginated support. You can now use /lm help, /lm help 1, or /lm help 2.
  • Fixed a bug where LagMeter's permission checks could have ignored lagmeter.*
  • Added permission node lagmeter.commands.ping, in correspondence to the /ping and /lping commands.
  • Added permission node lagmeter.commands.ping.unlimited, in correspondence to the packet hop specification of the /ping command.
  • Fixed a bug where commands sometimes didn't fire from lag/memory watchers.
  • When entities and/or chunks are output, if the amount shown would be 0, it is not displayed (should help MCPC users who have Mystcraft installed from getting spammed with tons of 0s).
  • Added more documentation to default configuration.
  • Fixed a bug where an exception would be thrown by the plugin if the configuration was invalid, where the it was intended to just show a message saying that there was an invalidity in the configuration.
  • Fixed a rare NoClassDefFoundException where the plugin's main class was instantiated before it was passed a Bukkit instance by the JVM, causing the plugin to try to find Bukkit classes where they were not yet visible to the plugin.
  • Added colours to console messages, at the cost of the [WARNING] and [SEVERE] tags.