yup, this was stated in the devlog as an error we know of! it'll be fixed in the next update ^^
Thank you!
