I am already in the midst of deploying v1.4.12, so it won't make it into the next direct update, but rest assured I have resolved it for v1.4.13 which addresses this issue, along with other potential fixes that may arise. :)
A Steam Post will be made when that happens!
Once again thanks so much for letting me know about this issue~