Thanks for the report @Just that guy_07. This bug got fixed in PC version 1.4.2, so when Mobile gets updated to 1.4.2 (whenever that is, there’s no estimate) it’ll be fixed in mobile.
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.