Ok, it turns out it's a bug. It's been fixed by the dev, and it will start working when we update our version in the next day or two