Confirmed that this issue still exists in 1.15.1 and has not been resolved, despite the many duplicate issues claiming otherwise. What a shame.
Confirmed that this issue still exists in 1.15.1 and has not been resolved, despite the many duplicate issues claiming otherwise. What a shame.