チケット #45666

"PlayerFlag" requirement

登録: 2022-09-19 18:30 最終更新: 2023-10-10 01:19

報告者:
担当者:
チケットの種類:
状況:
完了
コンポーネント:
マイルストーン:
優先度:
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.

チケットの履歴 (5 件中 3 件表示)

2022-09-19 18:30 更新者: ihnatus
  • 新しいチケット ""PlayerFlag" requirement" が作成されました
2023-10-01 14:25 更新者: cazfi
  • 担当者(未割り当て) から cazfi に更新されました
  • 解決法なし から 受領 に更新されました
2023-10-03 06:32 更新者: 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 更新者: cazfi
  • 状況オープン から 完了 に更新されました
  • 解決法受領 から 修正済み に更新されました

添付ファイルリスト

編集

このチケットにコメントを追加するには、ログインが必要です » ログインする