Confirmed for 19w41a.
I think it'd be easier to have everything in the same ticket, for the sake of consistency and helping devs
I updated the report with remaining issues.
There is still residue of this bug in 19w37a.
This is a shipwreck. Check under your feet.
Can approve this happens since these entities exist.
Also affects all types of boats.
Can confirm it also affects non-solid blocks that emits light. For example, torches do cause lag spikes.
Can confirm this only affects solid blocks. For example, tall grass and glass blocks do not cause lag spikes.
Can confirm /setblock also causes lag spikes. Any kind of block updates causes lag spikes actually, might be related to the new light engine.
Also can confirm this 18w43c and can confirm this is client side, only FPS and not TPS.
Sure!
As said in MC-125774 comments :
"You no longer keep the swimming / crawling animation, and instead stand up, however your eyes are still where your feet are."
Then it should be marked as fixed, as I never mentionned the eyes height and should need another ticket.
And IMO, this possible ticket will be resolved as WAI.
This also affects the port of the control settings from 1.12.2 to 1.13-pre10
The thing is that it doesn't produces any error. When you have an AZERTY keyboard, it will switch keys to the QWERTY keyboard.
[media]For example, here: the menu says that forwards is W. The options.txt
says it is Z and it is what it should be
Still affects 1.13-pre10 for me. I don't complicated keys, just some letters and numbers. Linked my options.txt
It seems like the method used in the features that are incorrectly placed provide an incorrect argument: the flags.
With Fabric's mappings I was able to indentify that there was a "setBlockState" method within the "Feature" class that should be used for all features, but is not. They call for the more generic "setBlockState" method, in the "ModifiableWorld" class with the flags argument set to 3, which means "notify the neighbor blocks, listeners and the client when the block is placed". You can also notify only the listeners and the client by using the value 2. However, some features call for the generic "setBlockState" method with 4 as the argument, which tells the client to suppress the render pass on clients.
Feature classes that do not use the "notify listener" include:
ForestRockFeature
FossilFeature
HugeFungusFeature
BlockPileFeature