The behavior I found may explain why MC‑305128 happens, but it is more specific than what that report describes. If this is considered a different issue, please let me know and I will create a separate bug report for it.
bug is too vague, im making another one more detailed
still exist in 1.21.6 pre4
The behavior I found may explain why MC‑305128 happens, but it is more specific than what that report describes. If this is considered a different issue, please let me know and I will create a separate bug report for it.