Teams and Members

Users participate in an event through a team. One member is the captain, and the team’s invite code allows other users to join until the team-size limit is reached. Team membership is scoped to the event; it does not change the user’s account or their membership in another event.

Hiding Participants

An administrator can hide an entire team or one member of a team. Hiding is intended for non-competitive participation: the hidden participant keeps access to the event and may view challenges, start instances, and submit flags, but does not affect the competition.

A hidden team has no competitive solves. It is omitted from the scoreboard, its submissions do not increase challenge solve counts, and its submissions do not affect dynamic challenge values. This applies to every member of the team, regardless of each member’s own visibility setting.

A hidden member remains on the team, but submissions made by that member are non-competitive. Submissions from the team’s visible members continue to count normally. Hiding a member is an event-level setting; it does not hide or disable the user’s site-wide account.

Successful submissions from hidden participants are retained as submission history. A hidden participant also continues to see a challenge they personally solved as solved, even though that submission is not included in the public solve count.

Retrospective Changes

Hiding a team or member takes effect retrospectively. Existing submissions from that participant are removed from the event’s competitive solve set. Unhiding restores eligible historical submissions. Dynamic challenge values and the scoreboard are recalculated from the resulting competitive solves.

Only one submission per team and challenge is competitive. If several members have successful submissions, the earliest eligible submission represents the team’s solve. This allows a visible member to solve a challenge previously completed only by a hidden member without awarding the team twice.

Removing a member transfers their solves to the team’s current captain. The team keeps those solves and its score. To remove the captain, first assign another member as captain. If a member who received transferred solves is later removed, those solves move to the current captain again. If the captain or the entire team is hidden, the transferred solves remain non-competitive until they are unhidden.

Deleting a team excludes all of its submissions from the competition. Its past submissions remain available to administrators, but they no longer contribute to challenge values, solve counts, or standings.