"piglin_safe": false,
"bed_works": true,
"respawn_anchor_works": true,
"has_raids": false,
"logical_height": 256,
"infiniburn": "minecraft:infiniburn_overworld"
I appended these extra settings because of this issue, but I am still getting errors in the log:
[Render thread/ERROR]: No key infiniburn in MapLike[{"ultrawarm":false,"natural":true,"shrunk":false,"ambient_light":-0.2,"has_skylight":true,"has_ceiling":false}];
Nevermind, it just fixed itself after I killed a spider with a crossbow. Weird.
Happened to me too. I cannot mine or attack with melee weapons now for some reason, but I was just digging up some sand
Same with me, but only with most villagers, Apprentice rank or higher especially.
It goes off its x position, and sometimes changes its facing direction, suggesting a curve
The quality is bad, but the only command blocks are for the x-position-to-score, the kill-all-non-players, the one that gives the vex the motion, and one to summon the vex stack.
No external commands that could interfere, and I tried it on a new world with similar results. I have a video showing that it still happens on a new world.
It has no positions of any type stored in its entity data, so I have no idea why it goes off course. Almost half a block after 20 or so blocks, sometimes varies.
Ah. I thought that the resource pack did not change any villagers, but it turns out it did. Honestly, I cannot remember what they all look like regulary.
Tested without "Optifine" (forgot I had it on), and the results are the same.
It lets you through the shulker from whatever side is its 'forward' side, as my failed elevator attempt shows. You fall through it when not constantly jumping.
(my connection is not the best, and it keeps failing to upload the second video)
Just moving the egg from the hotbar to an inventory slot and back. I failed to reproduce this once, but it worked another time.
I had this happen on 19a just now
I did not enter the command, only typing before the suggestions loaded:
scoreboard objectives add a.b_c (crash)
The character in question shows up as a ☃ (snowman) emoji in the output log's crash report, and I could not reproduce the error a second time.