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