v1.90.2

Details

  • Filename
    NoLagg-1.90.2.jar
  • Uploaded by
  • Uploaded
    Aug 18, 2013
  • Size
    273.18 KB
  • Downloads
    39,983
  • MD5
    073e7c2c63f1fab55c6118c7a71c4a10

Supported Bukkit Versions

  • 1.6.4
  • CB 1.6.2-R0.1
  • CB 1.5.2-R1.0

Changelog

Requires BKCommonLib v1.54 or v1.54-REVISITED Go to the BKCommonLib Dev-bukkit page

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.

Changelog

  • Added backwards support for 1.5.2 using BKCommonLib 1.54-REVISITED
  • Fixed examiner error (getEvent not found) due to Bukkit API change

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!)