S3_0 ruleup has no --clean option to allow updating without causing deprecation warnings
Similar ("...us never used by any unit.") messages received from other ruleset as well, also in S3_1 after 3.0 -> 3.1 ruleup. I've attached a log file from a S3_1 run with ruleup'd rulesets.
Reply To cazfi
Similar ("...us never used by any unit.") messages received from other ruleset as well, also in S3_1 after 3.0 -> 3.1 ruleup. I've attached a log file from a S3_1 run with ruleup'd rulesets.
No --clean when updating?
Reply To kvilhaugsvik
Reply To cazfi
Similar ("...us never used by any unit.") messages received from other ruleset as well, also in S3_1 after 3.0 -> 3.1 ruleup. I've attached a log file from a S3_1 run with ruleup'd rulesets.
No --clean when updating?
No. And I know I were against having it as the default. What I would consider the most correct (default) behavior would be to not remove any rules written by a human (no --clean), but not to cause unused rules when converting old hardcoded behaviors to a more generic ruleset format (--clean). That's probably too complex to implement? So current behavior is acceptable compromise. Except for the small detail that there is no --clean option in S3_0 to fix those warnings when wanted.
Reply To cazfi
Except for the small detail that there is no --clean option in S3_0 to fix those warnings when wanted.
That's what this ticket is about now.
Is this something that is possible to implement in S3_0 (in practice), or does it depend on other changes not in that branch?
Maybe it's time to drop this ticket - it's sort of late to start making that change to mature release branch.
Loading classic ruleset ruleup'd from S2_6 to S3_0 result in deprecation warning:
Action enabler for "Capture Units" is never used by any unit.
Same for "Bombard" and "Conquer City" actions.