When placing torches light doesn't spread correctly
Related issues
is duplicated by
Attachments
Comments

This issue may be relates to MC-3329

@unknown, MC-3329 is about generated torches, and this ticket is about placed torch

Probably related to MC-89262. Confirmed.

I can confirm this too in 16w07a. It is annoying. The light will not update until you force a reload with F3+A

Also, mining blocks leave dark spots, and sunlight fails to update for some reason when I opened a cave up to a clear view of the sky. F3 works sometimes, but not always. Definitely affects all lighting, not just torches. Torches are just the most easily noticed.

Is it possible that this bug is only because its a snapshot? Maybe the code is running in a sub-optimized state and this will go away for pre-release. I can only hope I guess. I sure don't see it in 1.8. Its very bad. I am surprised others are not reporting it.

I added two more screen shots for this. A before with torch and then after the torch is removed. It is very easy to reproduce with the 16w snapshots. I wish this was voted on more.

Affects 1.9-pre1. I really hopped that this one wouldn't make it into the final release.

Confirmed 1.9-pre4

Hmm this seems to happen more so when there's tick lag in the world or something like it. I switched from a command block heavy world to a fresh super flat world and the issue seems to not really be happening.

java version: 1.8.0_25 (integreted minecraft java launcher)
windows system: windows 10 x64
minecraft launcher: 1.6.59
minecraft version: 1.9

Also affects OS X 10.11.3, please update the environment.

Workaround: press F3+A to reload all chunks when this issue appears.

Still an issue in 16w15b

Affects 16w20a and OS X 10.11.4.

Still an issue in 1.10

I really wish that Mojang, or maybe Marcono1234 could take a look at this one next as this is a really annoying one.

Still an issue in 16w32a & 16w32b

Still in 16w33a

Still in 36a

16w39b too.

Confirmed in 16w40a

Still an issue in 16w41a

Confirmed in 16w42a

Confirmed in 16w43a

Confirmed in 1.11-pre1

Confirmed in 1.11

This happens because Minecraft will wait until no other chunk render updates are in some queue to schedule render updates for lighting, even if they are close to player. The one the block change occurs in is always updates because that's where the block got changed so it has to be updated.

Confirmed in 16w50a

Lights of chunks get updated in OptiFine.
This issue is resolved if you use OptiFine.

Confirmed in 1.12

This bug seriously messes with the look of a base I'm starting building. There's a glowstone below every glass block in the paths in this image. It's hard to visually tell if I've mob proofed an area properly. I've tried manually updating the bad chunks with the block/destroy forced update method, and sometimes it works for a little while, but eventually it reverts. This happens under optifine as well.
This needs fixing very badly.
[media]
That’d be MC-80966 (empty cubic chunks don’t send over light information), this is about light not spreading correctly to chunk borders if just placed, and reloading chunks will fix this.

I also found this hole in MC-131912👍

Still in 1.13.1 release

Still in 1.13.2-pre1

Still in 1.13.2-pre2

Correction of @Temian Schnell : he made a mistake with the bug report. This bug is not in 1.14! So you can delete the affected version 1.14.