任务单 #45666

"PlayerFlag" requirement

开放日期: 2022-09-19 18:30 最后更新: 2023-10-10 01:19

报告人:
属主:
状态:
关闭
组件:
里程碑:
优先:
5 - Medium
严重性:
5 - Medium
处理结果:
Fixed
文件:
1

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.

任务单历史 (3/5 Histories)

2022-09-19 18:30 Updated by: ihnatus
  • New Ticket ""PlayerFlag" requirement" created
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 Fixed

Attachment File List

编辑

Please login to add comment to this ticket » 登录名