I noticed that the arguments created by the "Limit Mounts" option in rules have no prefix, so are being handled as an AND operation, rather than a replacement set of mounts.

I'm not sure of the use cases for how it currently is, but I needed and expected to get arguments prefixed with =, and thus a new set of mounts; therefore, I'm requesting support for an additional option that does this instead.

It's been a while since I looked at the limit stuff, but it sounds like a bug.

Yep, not working right. Next release Limit will behave as expected.

Expect to do a new release once flying is available and I fix whatever bugs it shows up. Should be within the next couple of days. Thanks for the bug report.