yeh, i remember a JP rep commenting on this on the JP forums when 1.18 first came out.

so if you look on the bright side, they implemented this fix fairly quickly since it was a big issue for different regions of the community.