>>41438
yeah it definitely was, reloading fixed it, just a weird bug I hadn't seen before