Hon Leung

I have this happening in my 1.16 (now 1.16.1) server world. The only questionable thing we did was making a cramped skeleton spawner farm and a cramped cow farm and AFKing. Just thought to update this so the affected version includes up to 1.16.1. It goes something like this:

[03:55:54] [Server thread/WARN]: Fetching packet for 
removed entity bbg['Air'/85471, l='ServerLevel[world]', x=135.70, 
y=18.00, z=368.30]
[04:03:39] [Server thread/WARN]: Fetching packet 
for removed entity bbg['Air'/85984, l='ServerLevel[world]', x=135.70, 
y=18.00, z=368.70]
[04:03:43] [Server thread/WARN]: Fetching packet 
for removed entity bbg['Air'/85986, l='ServerLevel[world]', x=135.30, 
y=18.00, z=368.70]
[04:05:11] [Server thread/WARN]: Fetching packet 
for removed entity bbg['Air'/86105, l='ServerLevel[world]', x=135.70, 
y=18.00, z=368.30]
[04:34:06] [Server thread/WARN]: Fetching packet 
for removed entity bbg['Air'/89285, l='ServerLevel[world]', x=135.70, 
y=18.00, z=368.70]
[04:35:12] [Server thread/WARN]: Fetching packet 
for removed entity bbg['Air'/89347, l='ServerLevel[world]', x=135.30, 
y=18.00, z=368.70]
[04:50:07] [Server thread/WARN]: Fetching packet 
for removed entity bbg['Air'/90707, l='ServerLevel[world]', x=135.70, 
y=18.00, z=368.30]

The logging frequency is inconsistent, ranging from 5 seconds to 15 minutes each in between randomly. I also checked the coordinates and it is exactly at my waiting area for the skeleton farm. Let me know if you need the world, kind of think it is related to cramping mobs.

With MC-151825 marked as duplicate, the affected versions should include 1.14.1

https://www.dropbox.com/sh/seb7ahfm6dcboir/AAAItZ4MSIClq5QWzJUGVYyga?dl=0

Should be available for at least 5 days, hopefully I remember not to delete it
*Sorry I was working on my academic paper, forgot 1.14 is supposed to be out soon

Actually so that is once, cos the second "falling back" I trashed the world with chunks reset, so only downgraded once.
The socalled second time is in [N], but I basically just reused the world last opened in 19w14b, in 19w14b again

I described all of my version changes in MC-148147
Yes, twice but not recently, its copied here
I attempted upgrades through these versions:
*(Parentheses mean backup made without optimizing before the upgrade)
*[Square brackets mean action taken but no backup made after the upgrade]
(A) 19w08a to 19w08b
(B) 19w08b to 19w09a
(C) 19w09a to 19w09a
(D) 19w09a to 19w11a
(E) 19w11a to 19w09a (Fallback due to barrel ticking MC-145031)
(F) 19w09a to 19w09a
(G) 19w09a to 19w12b
(H) 19w12b to 19w13a
(I) 19w13a to 19w13b
(J) 19w13b to 19w13b
(K) 19w13b to 19w14a
(L) 19w14a to 19w14b
(M) 19w14b to 19w14b
[N] 19w14b(from after (M)) to 1.14pre1 (Optimization succeeds, reset some chunks due to MC-147800, update world trashed)
(O) 19w14b(from after (L)) to 1.14pre2 (Optimization fails at 52% in singleplayer)
[P] 19w14b(from after (M)) to 1.14pre3 (Optimization fails at 34% in multiplayer, 52% in singleplayer)
[Q] 19w14b(from after (M)) to 1.14pre3 (Optimization fails at 7% in multiplayer)
[R] 19w14a(from after (K)) to 1.14pre3 (Optimization fails at 68% in multiplayer)
[S] 19w14b(from after (M)) to 1.14pre3

Im happy to hear that the lighting bug seems to be finally fixed, but by optimizing world/force updating I encounter MC-148147 and it just fails on me (at 52% or 34%). I know my world might be corrupted somehow but I believe there was nothing I have done that was not intended to be done - I never killed the server apart from it crashing etc. I know this is not related to the lighting bug anymore but without optimizing the world/force updating the lighting situation would still be the same.

@Johnibur It should still not fail the optimization, also the datapacks worked before and are simple enough that should not cause any problems.
Also I am quite sure the world is somehow corrupted by upgrading to 1.14 pre2 and pre3, but works fine before these two versions.

Are you sure you are not in range of any dolphins and you dont have depth strider?

Is there a way for developers to simply add a debugging f3 combination/command that updates/ensures all light sources (say around a player) is doing their job server-side? I know this is not a permanent solution but I think it might be good enough for now, as replacing light sources (including lava) is a tedious manual thing to do, and it shouldn't be a difficult thing to implement (I guess?)

Can you mark my MC-147877 as duplicate if MC-147768 / MC-147783 / MC-147830 are marked?

Exactly, for now I have to temporarily fall back to 19w14b (including the server) as I made a backup when I updated.

The problem has escalated. I had a problem of MC-147877 (Namely 1.14 Pre1 resetting some of my chunks), so I took the original backup and decide to make my server fall back to 19w14b, which is when the backup was last used. Now throughout my world, not a single kind of light source is working. The game is basically unplayable now in normal survival as mobs spawn everywhere. (i was in spectator)

My mouse cursor never left that specific face of the block, and again I was able to place the torch or access the GUI if I do it slowly without trying to get the timing right. It's only if I try to click at that exact moment it does nothing. Where the torch would have been placed has always been an air block when I try to click on the furnace.

I realize it was probably a latency problem, but still it should synchronize and decide which function would be triggered instead of doing nothing.

@BladeCP69925233 Read my comment after you
and also it now plays the sound when you are near a dark cave

Actually confirmed in 1.14 pre1, I downloaded my multiplayer world back to my computer, put it to singleplayer and run the "Optimize World" function in 1.14 pre1. Uploaded it back to my host, and joined the game. A lot of the originally mislighted areas were fixed but this is new: (refer to lighting again.png)

In 1.14-pre1, I am not sure if it still recreates itself, but previously mislighted chunks (light level 0 regardless of having light sources or not) stay mislighted (if its a word). Replacing the light source one-by-one is not an option as the bug affected thousands of metre squared in my world. To mark it fixed, can there be a way for the game to refresh the lighting server-side while loading in, or provide a command or F3-something.

Oh yes.. Sorry about the mistake. I usually don't do anything non-vanilla to the server but there were too many creepers everywhere even when its lit due to MC-142134 :/ so I turned off mob-griefing until its fixed but I forgot about it. Sorry about it and please resolve the issue.

Edit: this broke my sheep farm which relies on detecting grass block changes, but I didnt think of that

 I just retested in on my multiplayer server, sheeps indeed dont consume the grass. @xParadoxical_

I believe it is an adaptive gliding mode instead of swimming. You can achieve that by also spam jumping into a 1-high gap.

Confirmed in 19w13b