Thank you for showing me this, I was able to find the problem, and it's now corrected in ver. 0.3.1Check the details on this in the devlog!
