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.
Working Build for 1.7.9?
Good news,
The latest NoLagg dev build works on 1.7.10!
Every single feature works fine, but i wont release it on BukkitDev until i tested BKCommonLib with all other plugins
@tjbruce
In ym opinion Clearlagg does nothign but make your players think its clearing lag. 1.7.10 update on the way
1.7.9 update please
Please working for 1.7.9
@THEREDBARON24
@THEREDBARON24
@Mr_Simba
Having The Same Problem. Using 'Clearlagg' as an alternative while 'Nolagg' Updates.
Is this still being updated? It completely doesn't work on 1.7.9 servers, chunks don't seem to get sent to the client and they never load the world, eventually timing out.
http://pastebin.com/HKvavQ7H Well this is a mess. Chunks do not load for the client. Server version is 1.7.9 which I am guessing is the issue.
@tailang
Looks like you haven't installed bkcommonlib. Perhaps it has been installed and you still need other libs for bk to work?
1.7.2spigot bug report wonderful plugin of course but ....... what am i suppose to do with this?
[01:59:04] [Server thread/ERROR]: Could not load 'plugins\NoLagg-1.90.4.jar' in folder 'plugins' org.bukkit.plugin.UnknownDependencyException: BKCommonLib at org.bukkit.plugin.SimplePluginManager.loadPlugins(SimplePluginManager.java:201) [spigot-1.7.2-R0.3-SNAPSHOT.jar:git-Spigot-1.7.2-R0.3-122-gb58e277] at org.bukkit.craftbukkit.v1_7_R1.CraftServer.loadPlugins(CraftServer.java:355) [spigot-1.7.2-R0.3-SNAPSHOT.jar:git-Spigot-1.7.2-R0.3-122-gb58e277] at net.minecraft.server.v1_7_R1.DedicatedServer.init(DedicatedServer.java:135) [spigot-1.7.2-R0.3-SNAPSHOT.jar:git-Spigot-1.7.2-R0.3-122-gb58e277] at net.minecraft.server.v1_7_R1.MinecraftServer.run(MinecraftServer.java:437) [spigot-1.7.2-R0.3-SNAPSHOT.jar:git-Spigot-1.7.2-R0.3-122-gb58e277] at net.minecraft.server.v1_7_R1.ThreadServerApplication.run(SourceFile:617) [spigot-1.7.2-R0.3-SNAPSHOT.jar:git-Spigot-1.7.2-R0.3-122-gb58e277]
really need the light fix /lag fix (shoudld be renamed to light fix) .. but anyway really need it for 1.7.9/10
Video Tutorial on the Plugin
http://youtu.be/EQgNlpDTrSs
Credits Video: (AbsintoJ/NoLagg)
Can You please Update NoLagg to 1.7.9? I get an PlayerChunkMap Error when I start my server. It is preventing my worlds from generating properly. So can you please update to 1.7.9? I would Be Very Grateful! Thanks!
EDIT: Also Get a WorldLoadEvent error. Using Bukkit 1.7.9 RO.2
@lenis0012
The best option in my opinion is to recode Nolagg completely as it may run better than the current one and will have more features than the lightweight. As there is always a possibility that the lightweight one could break too.
I vote for option 3 - Recode. I know it's gonna be a lot of work, but this plugin is gold, so I'd rather wait for a full update, than get a quick and dirty fix (the lightweight) or having a version that doesn't break on updates, but probably doesn't work as well.
Without fear !
'Make a lighweight versionof NoLagg that does not break every update.'
Keep good work man :D
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?
HI Could I translate your NoLagg to chinese?
Most of plugins breaking every update, it isn't a big problem, so I'm voting for recoding nolagg.
@lenis0012
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.