Team readiness

The question team readiness answers: can this player field this team today, and if not, what is missing?

For one player

/players/<id>/team-readiness checks every defined team against that player's roster and reports, per team, whether each required unit is owned and at the required star, gear and relic level.

For a whole guild

/guilds/<id>/team-readiness runs the same check across all fifty members at once. This is the officer view: before committing to a Territory Battle platoon or a Territory War defence, see how many people can actually put the team on the board.

Drilling into a single team shows the per-member breakdown — who is ready, who is one unit short, and who is not close.

Defining teams

Teams → List manages the definitions. A team is a name and a set of units with the requirements each must meet. Teams are shared across the instance, so a team an officer defines is immediately available to everyone.

Requirements are what make readiness meaningful: "owns the five units" and "owns the five units at relic 7" are very different questions, and only the second one predicts whether a defence will hold.