#45666: "PlayerFlag" requirement
Open Date: 2022-09-19 12:30
Last Update: 2023-10-01 08:25
URL for this Ticket:
https://osdn.net//projects/freeciv/ticket/45666
RSS feed for this Ticket:
https://osdn.net/ticket/ticket_rss.php?group_id=12505&tid=45666
---------------------------------------------------------------------
Last Changes/Comment on this Ticket:
2023-10-01 08:25 Updated by: cazfi
* Owner Update from (None) to cazfi
* Resolution Update from None to Accepted
---------------------------------------------------------------------
Ticket Status:
Reporter: ihnatus
Owner: cazfi
Type: Feature Requests
Status: Open [Owner assigned]
Priority: 5 - Medium
MileStone: S3_2 d3f
Component: General
Severity: 5 - Medium
Resolution: Accepted
---------------------------------------------------------------------
Ticket details:
From ticket #41813
cazfi
Somewhat overlapping (but not replacement) idea would be "PlayerFlag" requirement type. The benefit of PlayerFlag over PlayerState would be that requirement system would automatically gain access to each new flag added (no further implementation needed once we have the generic flag checking in place). Each PlayerState type would need to be implemented separately.
Currently, it can provide AI control status. I don't think any player state/speciality should be tracked in a flag but this one can and maybe some future ones too.
--
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/45666
RSS feed for this Ticket:
https://osdn.net/ticket/ticket_rss.php?group_id=12505&tid=45666