1. Place BKCommonLib.jar in the plugins folder
2. optional: You can add the example configuration folder; the plugin will create one itself if it is not present
3. If you have a previous version of 'BKCommonLib' on your server, replace it with a newer version if this is the case

Further installation of components:
- If you want to use the chunk sending mechanics, add NoLaggChunks.jar
- If you want to use TNT buffering and optimizations, add NoLaggTNT.jar
- for any other features, add NoLagg.jar
NoLaggChunks and NoLaggTNT are separate plugins and do NOT require the main NoLagg.jar to function. They do require BKCommonLib.

NoLagg.jar tends to have issues with the chunk unload delay and spawn limits, so disable those before you use it.
For spawn limiting I recommend finding an alternative, since NoLagg's version can cause a heavy tick rate drop on server
hosting 5K+ mobs. Due to the fact that it keeps meta data for each and every loaded chunk, it tends to eat performance rather than improve it.
This is especially the case on large-player-count servers. If you host around 100 players and have over 10K chunks loaded on average, 
I recommend only using NoLaggChunks and/or NoLaggTNT. The main NoLagg.jar functions best on lesser-performance servers.

- Older versions are compatible with newer BKCommonLib libraries; it has backwards compatibility.
- Do not put the BKCommonLib in the 'lib' folder; it will not function that way.
- BKCommonLib will show up as a separate running plugin, but won't do anything but monitor certain dependencies

The latest version of BKCommonLib can be downloaded from:
https://github.com/bergerkiller/BKCommonLib/downloads
The source is there as well.

You can examine the server tick rate using /lag examine
Use /lag examine 400 to examine for 400 ticks.
Use /lag examine to examine for 500 ticks.
The report will be exported to NoLagg/logs/
A program to view this file can be found in the same folder.

~Bergerkiller