-
Type:
Bug
-
Resolution: Done
-
Priority:
Minor
-
None
-
Affects Version/s: None
-
Environment:
API 1.14-R0.1-SNAPSHOT - No Plugins - Vanilla Java 1.14 Client
-
git-Spigot-1eece4f-84400e6 (MC:1.14)
-
Yes
(First bug report attempt, please let me know if there's anything I can do to provide better information.)
Most chunks, but specifically ones with villages, lose all block light data when unloaded. This means that after a player logs off, or returns from the Nether, all light blocks, such as torches, lamps, and jack-o-lanterns have a block light value of 0 (as seen from the F3 data screen under "Block Light: 0")
Reproduction:
1) Place light sources, such as torches, in a general area, spanning multiple chunks.
2) Summon entities, specifically villagers, into this area. Anything more than 25 seems to begin to cause the issue.
3) Build and enter a Nether Portal, while no other players are in the area (forcing the chunks to quickly unload).
4) Upon return to those chunks, especially be returning through the portal, the Block Light value in many chunks will now be 0. (Set time to night to easily locate dark areas)
Notes: I have spent nearly a week investigating this. I cannot find a mention of this online, and cannot find a way to prevent this from occurring. I have updated the Spigot server via BuildTools whenever a new version is available (checked through /about in-game) hoping for it to be fixed.
We can reproduce this quite consistently on a public server, should someone who thinks they can help need to see this. Been using Spigot for years, and I'm at a complete loss.
Random-light-updates also does not seem to activate from any configs, and has yet to have any effect on this error.
Does not affect vanilla 1.14 server nor client, not reported to Mojang
[SPIGOT-4884] Chunks lose all light data when unloaded
md_5
added a comment - nothing was done to fix it, I relied on the comment of the person that said it didn't affect them, but duplicate or invalid probably would've been just as appropriate a resolution. Only resolved means it was actually fixed
md_5
added a comment - nothing was done to fix it, I relied on the comment of the person that said it didn't affect them, but duplicate or invalid probably would've been just as appropriate a resolution. Only resolved means it was actually fixed Just a heads up, this was a vanilla bug. Is there a way you could post on the Mojang bug tracker what the fix is so that the fix can be implemented in Vanilla 1.14.2?
https://bugs.mojang.com/browse/MC-142134
If this is truly fixed with Spigot, then that is huge. This bug has hundreds of comments and people on the watchlist and is one of the nastiest bugs to plague Minecraft at the moment!
Chris
added a comment - - edited Just a heads up, this was a vanilla bug. Is there a way you could post on the Mojang bug tracker what the fix is so that the fix can be implemented in Vanilla 1.14.2?
https://bugs.mojang.com/browse/MC-142134
If this is truly fixed with Spigot, then that is huge. This bug has hundreds of comments and people on the watchlist and is one of the nastiest bugs to plague Minecraft at the moment! Updated to today's build, having a few players and myself testing extensively, but as of Build git-Spigot-1eece4f-fe1199c this error is no longer occurring.
Thanks for taking the time to check this out! Your work is greatly appreciated by our long-time Spigot-run community.
Apologies for the confusion. Like I said, first bug report...
Due to the immense difficulty reproducing the bug, this has been hard to keep track of. For a while, it was every few minutes. For a while, it never occurred. The issue continues to occur, and continues to have no consistent reproduction beyond just unloading chunks until it happens.
Our current "fix" does very little, and is similar to Mojang's recommendation. Every so often we have spigot Force-Update all chunks while also erasing Cache data, which scans for and resets all blocks and block lighting.
After this ticket closed and it happened again, I had found the vanilla ticket before reopening this one. Sorry for getting hopes up.