Bukkit

Compatibility

NoLagg uses BKCommonLib for all implementation-specific calls. Even then, there is no guarantee that it will work on all future versions. There is no risk of world corruption or damages, as long as you make sure you ALWAYS update BKCommonLib to the correct version first. At least then you will see correct errors if compatibility with NoLagg breaks, and you know when to update.

In general, NoLagg will keep functioning on all future Bukkit builds. It depends on what BKC is able to support whether this stays this way.

Tested on BKCommonLib 1.57.

Changelog

• Fixed 1.7.2 support (mainly BKC-related)
• Fixed method deprecation (block.getTypeId -> block.getType)

For a full Changelog, click here.

Notice: If you get a 'main thread taking too long' warning message and stack trace, and it shows NoLagg as a probable cause, report it to me. I want to ban out all lengthy tasks and spread the load over multiple ticks where possible.

For any other possible thread locking problems, read the stack trace that is reported. Common causes:

• Someone using WorldEdit to edit a huge part of a world
• Someone causing a lot of chunk loads
• Plugin reading from a flatfile or database on the main thread (common bug!)

For those using MCPC+ and MC 1.5.2: Disable the 'buffered loading' in the chunks component, as there is a bug in BKCommonLib that causes this to malfunction. Fixing it requires initiating a new REVISITED version for 1.5.2, which takes a bit long to do.