NoLagg

Empty

NoLagg logo

Version: 1.90.4 | CB 1.7.2

Quote from lenis0012:

in case you are using Orebfuscator, make sure you have ProtocolLib Installed

Description

NoLagg is made out of multiple completely separate components which you can enable and disable freely. Together they offer:

  • Send chunks more gracefully with lowered network stress and reduced processing spikes Read more...
  • Remove entities, resend chunks in case of chunk holes and clean up server memory Read more...
  • Examine server tick rate performance with deep view into per-tick processes of the server Read more...
  • Stop a large amount of items from spawning and spawn at a later time to avoid frozen clients Read more...
  • Stack items with a configurable per-world radius Read more...
  • Fix lighting errors that cause clients to recalculate lighting (and thus lag) Read more...
  • Keep track of server performance such as entities, tick rate, memory and more Read more...
  • Fix various bugs the server has (Patches component)
  • Schedule autosaves and force data to be written to disk to prevent data loss on server crash (Saving component)
  • Limit the amount of entities allowed to spawn per world or globally Read more...
  • Watch events closely to warn when plugins execute main-thread methods from another thread Read more...
  • Show a detailed message explaining the cause for a server freeze (lock) [read more]
  • New TNT execution algortithm that is not only more efficient, but also avoids server freezes Read more...

Important

When first installing NoLagg, open up config.yml and disable components you do not need. This is very important, as some components may conflict with other plugins you use, or may not function on the type of demand you have. If you get a warning message [Severe] followed up with a stack trace in the log, this has to do with the main thread not having responded within 10 seconds. The warning is NOT an error and is no bug, and not a bug related to NoLagg. To disable this feature, disable 'threadlocknotifier' in the config.yml. This feature is mainly intended to notify you what plugin is causing the server to freeze, may it ever happen. It is used to debug plugins in general, as they may get stuck for whatever reason. If NoLagg DOES show up in there, it is a bug you should report.

FAQ

Before reporting any problems, errors, issues, lag or even commenting about it, please read the information on this page very carefully. It makes my and your life a lot easier if you do.

Separating into jar files

NoLagg consists of multiple components you can individually enable and disable. Reasons for not publishing it as a separate jar file for every component can be read here. Please don't ask to separate the components, I will just link you to here.

Spigot server

Not all components are needed when you use the Spigot server. The ItemStacker, ItemBuffer, Spawn Limiter, Thread Checker and Thread Lock Notifier components are not needed, since Spigot has it's own implementations to deal with that. If you still wish to use one of these components, you can, but it's best to disable the Spigot alternative then.

The other components (such as TNT, Chunks, Lighting, Common, etc.) are not implemented in Spigot (yet?) and offer additional functionality.

PTweaks

Since people keep asking about this, I went ahead and compared the two plugins. I am not going to discuss which is better in functionality, I'm just going to state which features overlap and which do not. Both plugins offer a TNT-lag solving solution, feel free to choose which solution you like better. (the solutions are different) Both plugins also offer a way to change when and how chunks are saved, NoLagg adds to this that you can configure when the server writes data to disk. PTweaks offers a way of showing used memory, NoLagg Monitor too with a bit more information. Again, preference. Chunk Persistence is something PTweaks offers and NoLagg does not. Reason I excluded it from NoLagg is that the implementation used up more processing power than that it solved (I did have this for a while). If you want to give it a try, PTweaks is your answer. Monster Limiter is incorporated in NoLagg as well but then for all entities, and more options. ChunkEdits is a tricky one: NoLagg chunks does something similar, with the difference being that it also changes at what rate chunks are sent, which is the main feature NoLagg chunks offers. In addition, the ability to increase the amount of threads running to process chunk packets and the re-using of packet raw data offers some benefits PTweaks does not offer.

Then there are a lot of other features NoLagg has and PTweaks does not, such as examining server tick rate, item stacker, item buffer, fixing lighting, cleaning up server memory, resending chunks, removing entities on command and others (see description).

In short: Both plugins offer some overlapping features, and you need to pay close attention to the configuration of PTweaks and NoLagg and disable things that conflict. Having two TNT explosion altering plugins is going to have strange results, for example. Compare the functionality, decide, and enable in NoLagg what you do not want in PTweaks, and vice versa.

NoLagg showing up in error stack traces

The examine component inserts various hooks into the server to gather measurements. Specifically, you will find that the following lines show up now and then. These hook classes do absolutely nothing when not examining and can not be the cause for any issues, unless the stack trace ends there (first line after the exception shows this stack trace)

  • org.timedbukkit.craftbukkit.*
  • com.bergerkiller.bukkit.common.internal.ChunkProviderServerHook

Video

Here is a video by BlueDevonMovies (lenis0012):

Metrics

This plugin sends server count statistics to MCStats.org. You can (globally) opt out in the PluginMetrics/config.yml file.

Development Builds

DevBukkit Disclaimer
Click here to Download development builds of this Plugin

Go to the BKCommonLib Dev-bukkit page

Click here to add this banner to your page
How to place useful comments How to install plugins Solving errors and when to report them Reading and writing YAML

You must login to post a comment. Don't have an account? Register to get one!

  • Avatar of Layania Layania Jul 22, 2014 at 07:10 UTC - 0 likes

    Without fear !
    'Make a lighweight versionof NoLagg that does not break every update.'
    Keep good work man :D

  • Avatar of Mr_Simba Mr_Simba Jul 21, 2014 at 21:18 UTC - 0 likes

    Hi. My server currently has a problem where nametagged mobs or any mob with the PersistenceRequired tag will still despawn during wipes by our anti-lag plugin. Does NoLagg check for that, or will NoLagg also remove nametagged mobs if the mob limit is reached?

  • Avatar of EEFDGOD EEFDGOD Jul 21, 2014 at 08:59 UTC - 0 likes

    HI Could I translate your NoLagg to chinese?

  • Avatar of Gridbugkiller Gridbugkiller Jul 19, 2014 at 07:23 UTC - 0 likes

    Most of plugins breaking every update, it isn't a big problem, so I'm voting for recoding nolagg.

  • Avatar of xUndefeated786 xUndefeated786 Jul 18, 2014 at 21:41 UTC - 0 likes

    @lenis0012: Go

    Recode it. It's gonna be worth it. Every plugin breaks with an update. Theres not an API out there that can fix that effectively.

  • Avatar of azot4o azot4o Jul 18, 2014 at 20:23 UTC - 0 likes

    @lenis0012: Go

    That's a difficult choice. I say option 3, depending on what features option 2 light can have.

  • Avatar of AMoneyShotz AMoneyShotz Jul 18, 2014 at 17:11 UTC - 0 likes

    @lenis0012: Go

    Recoding it, and improving it entirely would be AMAZING! I love this plugin and would love to see it do more :D

  • Avatar of rodeyseijkens rodeyseijkens Jul 17, 2014 at 15:25 UTC - 0 likes

    @lenis0012: Go

    A lightweight version is nice but what are the features that will remain in that version?

    PS: Maybe its better for the lightweight version to exclude the things that are present in spigot, a lot of the servers run spigot too and that would save time and make it easier right :)

    Last edited Jul 17, 2014 by rodeyseijkens
  • Avatar of lenis0012 lenis0012 Jul 17, 2014 at 09:01 UTC - 0 likes

    Thanks for 1,000,000 downloads guys!
    I have been looking at your requests, and a lot of you are sad about the fact that NoLagg break every update.

    It is a choice we had to make.
    There is thousands of lines of code in Nolagg and BKCommonLib.
    They are some of the biggest plugins out there, and they are based of NMS (Minecraft internal code)
    This nms changes every update.
    Even tho nms changes every update, you can avoid having your plugins to break using reflection.
    We use reflection in a lot of places, but the amount of code we use is so large that we can't really avoid all of it.

    I have summer vacation and therefor time for 1 new big project.
    I want to let you guys choose:
    Work on the current NoLagg and fix all bugs i can spot
    OR
    Make a lighweight versionof NoLagg that does not break every update.
    OR
    Recode NoLagg entirely improving it but still breaking every update

    Last edited Jul 17, 2014 by lenis0012

    lenis0012.com (Comming soon)

  • Avatar of erik1988 erik1988 Jul 12, 2014 at 11:38 UTC - 0 likes

    I love nolagg, however I would wish it did not break everytime minecraft is updated. I guess that is easier said than done, but if it was possible it would be great!

    Is it so that only some components of nolagg does not work when updated? and if so is it possible to make it so nolagg just disable that feature instead of the whole component.

    I guess the reason for it to stop working also can be because of BKcommonLib, if so is it possible to make nolagg depend on protocollib instead, since it seems to work even after a update of minecraft.

    Im not a programmer so excuse me if I speak nonsense.

Facts

Date created
Sep 19, 2011
Categories
Last update
Jan 01, 2014
Development stage
Release
Language
  • enUS
License
GNU General Public License version 3 (GPLv3)
Curse link
NoLagg
Downloads
1,041,711
Recent files
  • R: v1.90.4 for CB 1.7.2-R0.2 Jan 01, 2014
  • R: v1.90.3 for 1.6.4 Oct 13, 2013
  • R: v1.90.2 for 1.6.4 Aug 18, 2013
  • R: v1.90.1 for CB 1.6.2-R0.1 Aug 06, 2013
  • R: v1.90.0 for CB 1.5.2-R1.0 Jul 10, 2013

Authors