Thanks for the report .3.b the bug has already been fixed but it'll be updated in the next update (the 25th)
I'm glad I could help! :)
