AndyJohns

Even if this bug isn't fixed soon enough, Mojang should be able to move the border to up to 32,768,000 blocks as opposed to the 30,000,000 limit. If this bug does finally get fixed for once, my hope is that the world border should get to 262,144,000 blocks at least, or up to 1,074,741,824 blocks depending on whether or not they've patched whatever bug that causes massive amounts of internal server lag when farther out than around 200 million.

Can confirm in 1.20.41 for Sculk Veins.

@Dhranios I think maybe have separate options.txt files for every client instance.

Isn't the shield meant to block attacks? If so, why is this unresolved? It makes sense for the shield to block knockback. I assume this is going to have a resolution of "Works as Intended"

Can't Mojang just calculate the block you are supposed to collide with using Integers rather than floating point? I mean, it's fine by me for them to use Floating point for vertical block collision since at Y=320 floating point precision is still at 0.000030517578125 units per increment. Mojang, if you are reading this, you have just been given a idea as to how you can fix this bug. And I beg of you, please fix it, it objectively impairs playability of the game. I would expect Mojang to put this at high priority.