Can confirm it’s still present on the latest snapshot
Uhhh not sure if I can change the affected versions anymore after the Jira migration? This bug is still present on 1.21.5 Pre-Release 3
Can confirm it’s still present on the latest snapshot