cfcf69f0b9
With single player on its server thread, the window is the server's client and dropped several packets the in-frame game never needed: - ClientboundBlockEntityDataPacket and the block entities of chunk packets: the block entity of that type loads the tag (signs, spawners), as handleBlockEntityData and LevelChunk.replaceWithPacketData do. - ClientboundChangeDifficultyPacket: the level data's difficulty and lock. - ClientboundSetDefaultSpawnPositionPacket: the respawn data spawn compasses point at. - ClientboundSetChunkCacheCenterPacket: ClientChunkCache's view centre; columns outside the storage (the server's radius + 3) are ignored or dropped, as ClientChunkCache.Storage does. - ClientboundAnimatePacket: wake up, and the critical and magic critical hit emitters. - ClientboundTickingStatePacket / ClientboundTickingStepPacket (new in the protocol crate): the level's TickRateManager. A frozen level holds its time and non-player entities, and the server's rate only ever slows the client timer down (Minecraft.getTickTargetMillis). - ClientboundServerDataPacket: the server list entry keeps a valid icon (ServerList.saveSingleServer); single player has no entry. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>