NoLagg
Version: 1.90.4 | CB 1.7.2
Quote from lenis0012:NoLagg has not been updated since 1.7.10, for more info, check BKCommonLib
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
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.
Since v1.41, when I place a single tnt and ignited it, on explosion my client crashes and the server does as well. Not sure what was changed but I had to go back to v1.40
Error on /reload http://pastebin.com/rtDFefUu
"Add option to disable physics when the tick delay becomes too high "
does this mean disabling sand and gravel falling and redstone mechanics? if not an option to disable/pause redstone mechanics if the delay becomes to high would be nice too :)
@vicente947
As soon Spout has correctly working packet listeners...I still can't catch chunk packets with the compressed data...and I have to catch those if I want to send packets in-sync correctly.
When are you going to update NoLaggChunks?
V1.40 is out, until it's displayed in the 'recent files' section to the right, you can download it from GitHub.
@bergerkiller
THANKS!!!!!!!!!!!!!!!!!!!
@goldseed
In v1.39 I added compatibility for Showcase
@th3controller
I had 3 updates in 1 day, so obviously didn't have time to update this page with it. I'll update it for a bit.
This bukkitdev page is not updated. When in time is this page? The version I see in the Bukkit Forum is 1.39 and in here it says 1.36. Also the change-log is not being updated and also the page is not being updated constantly to provide latest information. This plugin is great but it should be handled more efficiently.
@drakcore
Yes that has been fix.
@Hoot215
The Plugin NoLaggChunks is broken right now so just remove it untill it gets fix. That plugin is on hold due to the bugs that occurs. So dont use NoLaggChunks yet.
This plugin seems to work great, with a few minor bugs. Like this one:
http://imageshack.us/photo/my-images/256/20111029124425.png/
Other than that though, awesome plugin! Also, the bug above happened when I used /spawn, and I could not seem to reproduce the issue. I guess it's just random? Oh also, I was using NoLaggChunks as well (With Spout of course). And there was no error in the console.
Has the text on signs been fixed?
Hi...
NoLagg...causes infinite item pop-up when it is used with showcase or showcasestandalone.
I confirmed this experimentally with removing and adding plugins
Nolagg gathers same items located closely and makes bundle. (eg. arrow near arrow... == arrow x2)
so. . when I make two showcases with same stackable item nearby, it makes.. bundles..and items pops up infinitely
I don't want to lose both of them...
Is there any solutions?
http://dev.bukkit.org/server-mods/scs/
config.yml
formItemStacks: false
this can be quick solution.. through...
@bergerkiller
Dude where do I put the mob restrict thing? Inside the config file?
<<reply 407010="">>
i think its pretty basic knowledge stuff.. its not like its rocket science equations or something.
could you add a "plug&play" config file that would be good for most servers ;] ? and an information about it on this page, because its sounds complicated and i think it scares a lot of people ;]
i like the plugin very much, but... the sign text is a big issue as said by the other people. Maybe you could fix this sometime soon. thanks.
This is super plugin, but after every server restart, sign texts are gone. Text is there i think, because using sign edit it shows it, but players can see it, until using something to edit that sign. Tried without any other plugins.