Hey, this bug is back... Both in V0.1.5.2 and V0.2.0WIP.
I'll take a look. I must've reverted by accident at some point. It'll be fixed for the next patch.
