Yes, even this bug (MC-249831) still exists in 1.19-pre3.
It's similar, but I'm not sure if it's the same error (duplicate) and same cause.
But it would like to remind developers so they do not forget it and to fix. Thank you.
pepkansek
Yes, even this bug (MC-249831) still exists in 1.19-pre3.
It's similar, but I'm not sure if it's the same error (duplicate) and same cause.
But it would like to remind developers so they do not forget it and to fix. Thank you.