I just updated my old 1.16.5 world to 1.18 and then I haven't stopped seeing these random dark spots in all my world, It happens in random chunks, and light sources.
I already tried optimizing my world into 1.18 and erasing cache option but doesn't work.
They continue to happen always even in the same places after I unload the chunks and reload them.
It always happens when exploring new terrain too.
please help is very annoying
Some of them disappear after placing a torch, but some others don't and I don't know what to do.
UPDATE: I updated the world to 1.18.2 release candidate 1 and this still happens I will let one screenshot of the bug
Linked issues
is duplicated by
relates to
Attachments
Comments

Can confirm in 1.18.1.
thank you, im not the only one (phew) I hope more people comment to see if we get a response

This issue keeps happening on my world (created in Beta, updated through to 1.17, currently 1.18.1). It didn't seem to happen as much in previous versions. "Optimise world" does temporarily resolve the issue but before long the issue appears somewhere else or even in the same places.

Can confirm. This just has happened to me in a brand new 22w03a world. So this is indeed not exclusive to upgraded worlds.
See
Hello, would it be possible to attach an affected world to the report?
Also a forced crash report (Holding F3+C for 10 seconds) from someone who is affected could be useful.
Of course, I found a chunk with this error again I attach some screenshots and the crash report
[media][media]
[media]
Thanks! 🙂
Could you also zip an affected world and attach it?

I believe I found a case of this occurring in 22w16b.

I can add a world zip if that's still required. Only world or config + logs as well?
I'm on 1.18.2 and I am not sure how long the problem existed. The world is quite old, upgraded incrementally since 1.15, but I've only noticed it in 1.18. I think it's related to chunk borders. My world has this problem pretty much everywhere I look
[media][media]Still in the 23w17a?
Cannot reproduce un 23w18a

Very closely related to MC-228608.
This exact thing has happened to me as well