Ticket #45666

"PlayerFlag" requirement

오픈 날짜: 2022-09-19 18:30 마지막 업데이트: 2023-10-10 01:19

Reporter:
소유자:
Status:
Closed
Component:
MileStone:
Priority:
5 - Medium
Severity:
5 - Medium
Resolution:
Fixed
File:
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.

Ticket History (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 (None) to cazfi
  • Resolution Update from None 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
  • Status Update from Open to Closed
  • Resolution Update from Accepted to Fixed

Attachment File List

Edit

Please login to add comment to this ticket » Login