#44181: Forbid singlepole setting requirements unless alltemperate is disabled
Open Date: 2022-03-25 15:54
Last Update: 2022-03-26 20:12
URL for this Ticket:
https://osdn.net//projects/freeciv/ticket/44181
RSS feed for this Ticket:
https://osdn.net/ticket/ticket_rss.php?group_id=12505&tid=44181
---------------------------------------------------------------------
Last Changes/Comment on this Ticket:
2022-03-26 20:12 Updated by: cazfi
Comment:
Reply To alienvalkyrie
Should we also do something for S3_0, e.g. mark those cases as deprecated
Yeah, deprecation warning would be the right thing to do, even if it seems that we still have work to do in educating ruleset authors to enable those warnings.
---------------------------------------------------------------------
Ticket Status:
Reporter: alienvalkyrie
Owner: alienvalkyrie
Type: Bugs
Status: Open [Owner assigned]
Priority: 5 - Medium
MileStone: S3_1 d3f
Component: Server
Severity: 5 - Medium
Resolution: None
---------------------------------------------------------------------
Ticket details:
It is currently possible to have singlepole requirements without also checking that alltemperate is disabled. This is nonsensical, since when alltemperate is in fact enabled, singlepole should not make any difference.
I can see a number of ways to deal with this:
Mark singlepole requirements deprecated unless (a) there is also a negated alltemperate requirement or (b) alltemperate is locked FALSE by the ruleset
As above, but make it a hard ruleset loading failure
Mark all singlepole requirements deprecated
As above, but make it a hard ruleset loading failure
To make #44038 easier / possible at all, this needs to be resolved in S3_1.
--
Ticket information of Freeciv project
Freeciv Project is hosted on OSDN
Project URL: https://osdn.net/projects/freeciv/
OSDN: https://osdn.net
URL for this Ticket:
https://osdn.net/projects/freeciv/ticket/44181
RSS feed for this Ticket:
https://osdn.net/ticket/ticket_rss.php?group_id=12505&tid=44181