Thank you for the feedback, @OhThatDemoness6. I don't know if you're the same person who expressed the same issue on GitHub, but regardless, your issue is probably related, and I am glad to inform you that the issue is fixed in v1.0.18.