This bug was fixed in 0.10.2A and 0.9.4B
Thanks for the response. I'll read the patch notes next time. Sry :(
