LagMeter 1.11.0

Download

Details

  • Filename
    LagMeter.jar
  • Uploaded by
    View TheLunarFrog's Profile
    TheLunarFrog
  • Uploaded
    Dec 9, 2012
  • Size
    24.84 KB
  • Downloads
    2,510
  • MD5
    2bd51b4d2ef4a66b567aeb5efd7058c4

Supported Bukkit Versions

  • CB 1.4.5-R0.2

Changelog

Version 1.11.0

  • Built with CB1.4.5-R0.2
  • Added a new command: /lmobs - Shows how many entities are currently alive in each world, then shows a total.
  • Added a new command: /lchunks - Shows how many entities are currently loaded in each world, then shows a total.
  • Added a new command: /lmp - Works the same as /lm with no arguments, but shows players too.
  • Added a base command: /lagmeter - Shows the current version and available sub-commands (/lagmeter help and /lagmeter reload").
  • Changed a command: /lm - If no arguments are added, it will work the same as before, but if help or reload are added, it will perform such a function.
  • Added the ability to make all of the log information appear on one line. Users should add this configuration node to their settings.yml, under the log: section and change it depending on their preference: 
    #Should the plugin put each statistic (TPS, memory, players) on a separate line?
    #Default: true
    newLinePerStatistic: true
  • Added the ability to make an extra space appear between each block of log data. Users should add this configuration node to their settings.yml, under the log: section and change it depending on their preference: 
    #Should the plugin have an empty line between each log tick to make the log file neater?
    #Default: true
    newBlockPerLog: true
  • Added the ability to add loaded chunks per world or only total, or not at all. The same goes for entities alive. Users should add these lines to their configuration under the log: section and then edit them based on their preference. 
    #Should LagMeter log how many entities are present on the server?
    #Default: true
    logEntities: true
    #Should LagMeter only display total entities, and not those for each world?
    #Default: true
    logTotalEntitiesOnly: true
    #Should LagMeter log how many chunks are currently loaded on the server?
    #Default: true
    logChunks: true
    #Should LagMeter only display total chunks, and not those for each world?
    #Default: true
    logTotalChunksOnly: true
  • Added the ability to show chunks and/or entities on plugin (re)load. Displays per-world and total. Users should add the following configuration nodes to the base of their config, then edit accordingly: 
#Display chunks loaded on plugin (re)load?
#Default: true
LoadedChunksOnLoad: true
#Should LagMeter display all of the entities that exist at the time of plugin (re)load?
#Default: true
displayEntitiesOnLoad: true
  • Fixed a bug where the log interval would never be loaded.
  • Fixed a bug where default values for configuration would not load the correct values if the file did not exist, or the node was missing.
  • Fixed a bug where if a bug is found in the plugin, Bukkit won't tell you to nag Demmy, but rather, me (TheLunarFrog).
  • A bit of optimization of code pathing.
  • Largely optimized memory usage.
  • Added a check to make sure there's not a divide by 0 error.
  • Changed the descriptions for the lag notification permissions (they were copied and pasted before)
  • Users must use vault if they want users to have /lag - reverted commit, meaning all permissions are default op-only, so for anyone to have /lag, they must have the lagmeter.command.lag permission.
  • Added ability to see entities per world and total, same with loaded chunks, when using /lag. Users should add this section to their configuration: 
Commands:
    Lag:
        #Should the commands which show the TPS meter also display entities in each world?
        #Default: false 
        displayEntities: false
        #Should the commands which show the TPS meter also display loaded chunks in each world?
        displayChunks: false
  • Added a percentage value to the memory when it is logged, so now it will show something like "Memory free: 1000/1337 (74%)."
  • Re-structured the default configuration. To make sure users aren't missing anything, it now looks like this: 
#################
##     General      ##
#################
#Whether or not to use the average for TPS. If set to false, the server will always return the value at the last poll.
#Default: true
useAverage: true
#How many polls to keep in LagMeter's memory.
#Default: 10
averageLength: 10
#How often LagMeter should poll the server.
#Default: 40
interval: 40
#Display chunks loaded on plugin (re)load?
#Default: true 
LoadedChunksOnLoad: true
#Should LagMeter display all of the entities that exist at the time of plugin (re)load?
#Default: true
displayEntitiesOnLoad: true
#################
##   Commands  ##
#################
Commands:
    Lag:
        #Should the commands which show the TPS meter also display entities in each world?
        #Default: false 
        displayEntities: false
        #Should the commands which show the TPS meter also display loaded chunks in each world?
        displayChunks: false
#################
##     Logging      ##
#################
log:
    #How often the plugin should log information to its log file.
    #Default: 150
    interval: 150
    #Should LagMeter log information to a file?
    #Default: true
    enable: true
    #Should LagMeter use a folder called 'logs' and use 'Day-Month-Year-Lag.log' format for each day's logs?
    #Default: false
    useLogsFolder: false
    #Should LagMeter log how many players are online as well?
    #Default: true
    logPlayersOnline: true
    #Should LagMeter log how many entities are present on the server?
    #Default: true
    logEntities: true
    #Should LagMeter only display total entities, and not those for each world?
    #Default: true
    logTotalEntitiesOnly: true
    #Should LagMeter log how many chunks are currently loaded on the server?
    #Default: true
    logChunks: true
    #Should LagMeter only display total chunks, and not those for each world?
    #Default: true
    logTotalChunksOnly: true
    #Should the plugin have an empty line between each log tick to make the log file neater?
    #Default: true
    newBlockPerLog: true
    #Should the plugin put each statistic (TPS, memory, players) on a separate line?
    #Default: true
    newLinePerStatistic: true
#################
#    Notifications    #
#################
Notifications:
    Lag:
        #Enables low TPS notifications.
        #Default: true
        Enabled: true
        #If the server is at or below this value for memory free, it will notify OPs and anyone with the permission node lagmeter.notify.lag
        #Default: 17
        Threshold: 17
        #How often LagMeter should check on the TPS, in minutes.
        #Default: 5
        CheckInterval: 5
        #Specify a command to use when the plugin notices that the TPS is low. Must be usable from console.
        #Default: /lag
        ConsoleCommand: /lag
    Memory:
        #Enables/disables low memory free notifications.
        #Default: true
        Enabled: true
        #If the server is at or below this value for memory free, it will notify OPs and anyone with the permission node lagmeter.notify.mem
        #Default: 25
        Threshold: 25
        #How often LagMeter should check on the free memory, in minutes.
        #Default: 10
        CheckInterval: 10
        #Specify a command to use when the plugin notices that the free memory is low. Must be usable from console.
        #Default: /mem
        ConsoleCommand: /mem

Developers:

  • Made nothing in LagMeter static - now, the LagMeter instance must be used if LagMeter is to be hooked into. There is a static accessor variable, however: LagMeter.p.
  • Added API: double[] getMemory() - Returns: 0 - used memory; 1 - max memory; 2 - memory free; 3 - percentage of memory free (un-truncated).