"PlayerFlag" requirement

• 回報者: ihnatus
• 負責人: cazfi
• 類型: 特色請求
• 狀態: 關閉
• 元件: General
• 里程碑: S3_2 d3f (closed)
• 優先權: 5 - 中
• 嚴重程度: 5 - 中
• 處理結果: 修正
• 檔案: 1

細節

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 History (3/5 Histories)

2022-09-19 18:30 Updated by: ihnatus

• New Ticket ""PlayerFlag" requirement" created

2023-10-01 14:10 Updated by: cazfi

• File 0049-Add-PlayerFlag-requirement-type.patch (File ID: 13412) is attached

2023-10-01 14:25 Updated by: cazfi

• 負責人 Update from (無) to cazfi
• 處理結果 Update from 無 to Accepted

2023-10-03 06:32 Updated by: None

評語

Reply To ihnatus

From ticket #41813 cazfi 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.

Oh, the possible applications are numerous. What about giving ruleset-defined flags to specific leaders for special virtues (like, France: Napoleon=+10% att, Louis XIV=+10% culture)? Another idea (spied in Ways of History), maybe we need for team members Captain (can invite/kick team members and/or manipulate their flags), ScienceDirector (only they can change pooled research) and TeamObserver (obvious) flags? Or hang temporal script-defined flags on players when it is more comfortable then setting a counter?

2023-10-10 01:19 Updated by: cazfi

• 狀態 Update from 開啟 to 關閉
• 處理結果 Update from Accepted to 修正