Deleted 1 year ago
Hi! A couple people reported this bug for the previous build. Do you happen to be using build 3.0 or 3.1, as I (hopefully) fixed this bug in the most recent build. If you’re using build 3.1 and experiencing this issue, please feel free to email more details to me at studioscrescence@gmail.com so I can get a bit more insight as to what is causing the error to occur!