Rules corrupt

[FlorianBome]

I’m sorry to hear of this trouble!

I can confirm that this is a bug that appeared in version 1.9 build 1018 and was fixed in 1.9 build 1022.
See here:

Corrupt Options on loading rules initializing variables starting with x

excellent, thanks a lot for finding out more about this. I could narrow it down to this: xa=0 xb=0 On reload, it’ll become xa=11. I think I know what’s happening: you can also specify numbers using hex notation, like xa=0x7F. Upon reading such a file, the Rules are following one another, so it will read like this: xa=0xb=0 And 0xb is hexadecimal for 11. It’s fun being a detective So for now, an easy workaround is to not assign 0, but, for example, another 0 variable. But a…

Be aware that this bug still exists in BomeBox firmware version 1.5.