Light from fire that has gone out lingers at the border of chunks
I don't know the significance of the chunk, but I just ran into it. the light only appears to linger when the fire goes out on its own, when it's put out manually it doesn't seem to happen. The seed is 899465857
Linked Issues
is duplicated by8
Created Issue:
light from fire that has gone out lingers at the border of this chunk
I don't know the significance of the chunk, but I just ran into it. the light only appears to linger when the fire goes out on its own, when it's put out manually it doesn't seem to happen. The seed is 899465857
Environment
Windows 10, Java Version 8 Update 161
Windows 10, Java Version 8 Update 161
light from fire that has gone out lingers at the border ofthischunkLight from fire that has gone out lingers at the border of chunks
is duplicated by
relates to
is duplicated by
relates to
relates to
relates to
relates to
is duplicated by
is duplicated by
is duplicated by
is duplicated by
is duplicated by
is duplicated by
Duplicate of MC-166260. Please go and upvote this ticket instead.
Thank you for including your test world in its 1.15.2 state!
MC-192845 is indeed affected by the fix for this issue, however the lag in your test world still got worse compared to 1.15.2, so we will keep that one open.
The cause of the lag in the test world is light updates caused by all the blocks changing from blocking light to letting light though and back.
Prior to the 1.16 snapshots when more than 64 blocks in a chunk changed at once, the client would not recalculate the light and just trust data from the server which might or might not have matched the correct state (see MC-166260). Now the client will always calculate the light itself, which can be more expensive.
Duplicate of MC-166260
Thank you for your report!
We're tracking this issue in MC-166260, so this ticket is being resolved and linked as a duplicate.
If you would like to add a vote and any extra information to the main ticket it would be appreciated.
If you haven't already, you might like to make use of the search feature to see if the issue has already been mentioned.
Quick Links:
📓 Bug Tracker Guidelines – 💬 Community Support – 📧 Mojang Support
📓 Project Summary – ✍️ Feedback and Suggestions – 📖 Game Wiki
– I am a bot. This action was performed automatically! If you think it was incorrect, please notify us on Discord or Reddit
Possibly a duplicate of MC-166260. I'm unsure due to the lack of information provided in this report.
Thank you for your report!
We're tracking this issue in MC-166260, so this ticket is being resolved and linked as a duplicate.
If you would like to add a vote and any extra information to the main ticket it would be appreciated.
If you haven't already, you might like to make use of the search feature to see if the issue has already been mentioned.
Quick Links:
📓 Bug Tracker Guidelines – 💬 Community Support – 📧 Mojang Support
📓 Project Summary – ✍️ Feedback and Suggestions – 📖 Game Wiki
– I am a bot. This action was performed automatically! If you think it was incorrect, please notify us on Discord or Reddit
I removed my previous attached screenshots that were cases of MC-166260. I attached new ones that are actually caused by this issue.
This is actually a duplicate of MC-166260.
Duplicate of MC-166260.
Thank you for your report!
We're tracking this issue in MC-166260, so this ticket is being resolved and linked as a duplicate.
If you would like to add a vote and any extra information to the main ticket it would be appreciated.
If you haven't already, you might like to make use of the search feature to see if the issue has already been mentioned.
Quick Links:
📓 Bug Tracker Guidelines – 💬 Community Support – 📧 Mojang Support
📓 Project Summary – ✍️ Feedback and Suggestions – 📖 Game Wiki
– I am a bot. This action was performed automatically! The ticket was resolved by one of our moderators, and I left this message to give more information to you.
Resolving as a duplicate of MC-166260 then.
Thank you for your report!
We're tracking this issue in MC-166260, so this ticket is being resolved and linked as a duplicate.
If you would like to add a vote and any extra information to the main ticket it would be appreciated.
If you haven't already, you might like to make use of the search feature to see if the issue has already been mentioned.
Quick Links:
📓 Bug Tracker Guidelines – 💬 Community Support – 📧 Mojang Support
📓 Project Summary – ✍️ Feedback and Suggestions – 📖 Game Wiki
– I am a bot. This action was performed automatically! The ticket was resolved by one of our moderators, and I left this message to give more information to you.
At this point, MC-172980 is more of a catch-all ticket for all block lighting updates that do not propagate properly across chunk borders. The fact that the lighting propagates back to the original chunk is expected if the wrong chunk is updated first (something which I've experienced before while testing MC-166260 and MC-172980).










Still present in 1.15.
You can replicate through spamming fire while flying just above th ground in creative mode. You will deiscover some chunks let the fire go out, though the chunks around them think the fire isnt out, so the will keep showing the light of the fire. When you replace the blocks at the edge of the dark chunk the light will spread across the dark chunk. When you place blocks at the middle of the not present light sources, the light will dispappear
1.15. It happened to me when I collected blocks which had torches on.
This screenshot is from vanilla server. Issue disappeared when reloading chunks (loggin out and back)
Can no longer reproduce in 1.16-pre2. Might have been fixed along with
MC-172980. Someone please double check.cant reproduce for 1.16-pre2
I am unable to reproduce this issue in 20w51a.
I am still actually able to reproduce this in 20w51a. It happens quite rarely so reproducing this may take some time. I've attached a screenshot.
Can confirm in 21w03a.
Can confirm in 1.16.5 and 21w08b.
Affects 1.17 with 1.17.1 pre 1
Can confirm in 1.17.1 Release Candidate 1.
Can confirm in 21w40a.
Can confirm in 21w44a.
I am unable to reproduce this in 23w17a. Is anyone still able to reproduce this issue?
@[Mod] ampolive, me too.
I am resolving this as Fixed then.