Still not solved in v1.16.20
It is weird that this is still not patched, because this already was a problem in v1.12
Still not solved in v1.16.20
It is weird that this is still not patched, because this already was a problem in v1.12