I've fixed this today. I still don't know how this bug started, but I've figured out a way to fix it. Expect the v 1.5.5 update tonight
