Using /carpet setDefault to change the quasiConnectivity rule to something above 1 throws an InvalidRuleValueException upon server restart, despite the validator theoretically accepting any number from 0 to the world height. The value will then set itself back to 1, the default.
Hypothesis
This is most likely to do with maxRange not reassigning properly inside the validator. Perhaps while the server command source is not null, the world cannot be found?
Observed Behaviour
Using
/carpet setDefault
to change the quasiConnectivity rule to something above 1 throws anInvalidRuleValueException
upon server restart, despite the validator theoretically accepting any number from 0 to the world height. The value will then set itself back to 1, the default.Hypothesis
This is most likely to do with
maxRange
not reassigning properly inside the validator. Perhaps while the server command source is not null, the world cannot be found?To Reproduce:
/carpet setDefault quasiConnectivity 10
InvalidRuleValueException
being thrown for "10"/carpet quasiConnectivity
, and observe the rule having been set to 1 instead of 10