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.
@LHammonds For Permission nodes I strongly recommend just reading the PermissionsDefaults.yml, as you noticed the ones on the page are a bit outdated.
The 'nolagg.monitor.use' and 'nolagg.common.gc' should work just fine, if this is not the case, then it's a permissions plugin bug (likely). What permissions plugin are you using? Do you have Vault installed as well?
@ToastedGoat It does, only updating BKCommonLib is required.
What are the actual permission nodes for NoLagg 1.90.2?
I'm using CraftBukkit 1.6.4-R0.1, Java 1.7.0_40 (64-bit), Ubuntu Server 12.04.3 LTS (64-bit), PermissionsEx 1.20.3. I also have OP disabled so nobody is OP on my server and thus, any plugin requiring OP-only will never work.
The command page says to use "nolagg.examine" but the "permissionsDefaults.yml" in the plugin folder suggests the node is "nolagg.examine.run" which works if I used that node.
The command page says to use "nolagg.monitor" to run the /nolagg stats command. However, that too is incorrect. The "permissionsDefaults.yml" suggests the node is "nolagg.monitor.showmemory" and/or "nolagg.monitor.use" but they do not work...only if I OP myself can I get that command to work.
I also tried the "/nolagg gc" command but did not have sufficient permissions. The commands page does not even show it. The "permissionsDefaults.yml" suggests the node is "nolagg.common.gc" but that does not work.
LHammonds
Hello,
Does this work on 1.6.4? I have installed it but it says it failed to load. Just wondering if maybe I'm doing something wrong or if you are planning on updating it? Thanks!
ToastedGoat
@PrimoHighDefinition Actually, it should fix the FPS drops caused by TNT explosions too. Unless you computer is really bad of course, and even a single explosion lags it. You can configure all this to reduce the lag in the config.yml.
@martin0leung
It will remove serverlaggs and not your fps drops^^
Does it work for 1.6.4 cause I got 0 fps when using tnt
It can automatically clean up Define a Caps numerical auto clean to designation entity types?
sorry.my english.
I was doing a: /nolagg examine when: http://pastebin.com/jASUXsRP
It continues till the server is restarted.
EDIT: I could see this too on log: http://pastebin.com/y0ubg2zj
@ha11oga11o
Look aat the line 14. I did /nolagg clear and got that. Is it possible that something is broken on mine server so its actually keeps items on the floor?
http://pastebin.com/4feWbRfn
really, if someone have any idea please post it.
Thanks.
@jeracom
Hello all,
is this caused by this plugin or not*?? Server iz frozen at this:
http://pastebin.com/Yq6c3UQL
Thanks!
@waremanu
Nolagg 1.9.2 running with the 1.6.4. You must have the latest BKcommonlib.
Click on the picture and you have the "Dev version".
If you want Nolagg Dev, there is the 1.9.3
@bergerkiller
The server is running Spigot, and the lighting bug exists when using CB as well.
To answer your three questions:
1. It fixes most of the lighting glitches, but not these black spots. These spots seem to be pretty random and can happen all over the map.
2. Yes it always fails at this spot.
3. Nope.
@waremanu
The hell it does it.
Please update for 1.6.4! The 1.6.2 don't work for 1.6.4.
@ShakyTom Hmn strange. I do notice you are using MCPC+, so perhaps it has to do with that(?). A few questions:
This is after a lighting fix with nolagg.
What is wrong with the dark bit?
http://gontroller.com/caps/3f28d4e5f8.png
NoLagg 1.90.2 still works on MC 1.6.4, all you need to update is BKCommonLib. The stacking of items with different lore/displayname is fixed in BKCommonLib as well.
@erik1988 Already works, only BKCommonLib has to be updated.
@TheDanteChaos On BKCommonLib page: "Support for Tekkit is not entirely certain, no issues thus far"
Clearly there are issues, as it's not working. I could look into adding support, but unfortunately Tekkit is incredibly behind on updating, and I really need a 1.6.4 version of Tekkit to do that...which is the reason I could never add support.
Hi, Im testing out your plugin on a local copy of my live tekkit server. With chunks enabled it wont load any chunk anymore. absolutly nothing untill i turn that off and it works like a charm. Using 1.5.2 version of BKCommonLib and latest version of this plugin.
Any idea's?
Iooking forward to the 1.6.4 version. It does not load so far..