Contest problems

Problems are added to a contest from the space's problem library, on the contest's Problems tab. A contest problem is a separate thing that references a library problem: statements, tests, limits, checkers and code templates all stay on the library problem, and the contest keeps only its position, its attempt limit and its scoring switch.

That separation is what lets the same library problem appear in two contests without the contests interfering with each other, and it is also why editing a statement mid-contest means editing the library problem, not anything here.

You need permission to write contests to change any of this, and the problems have to exist in the library first — create or import them there before you start.

Add problems

Open the contest and go to Problems.
Click Add problem.
Pick one or more problems from the library. They are all added in one go.
Optionally set, for the problems you are adding:
- Attempt limit — how many times one participant may submit that problem.
- Score using best result per testset — score the problem as the sum of the best result in each testset across all of the participant's submissions, instead of the score of a single submission.
Confirm.

Each problem added becomes an independent contest problem and leaves the library problem untouched, so the same problem can be added again — here or to another contest.

Adding is refused on a finalized contest, and once the plan's problems-per-contest quota is reached. If Add problem isn't there at all, see Why a section is missing.

Reorder problems

Drag the rows. Moving a problem renumbers the problems it passes so the sequence stays contiguous, and the letters participants see — A, B, C… — follow the position, so reordering renames problems for everyone looking at the contest.

Dragging is disabled without permission to write contests, and on a finalized contest.

Change a problem's contest settings

Click the row, or choose Edit in the row menu. The dialog holds the library problem it points at — locked once the contest problem exists — the attempt limit and the best-testset scoring switch. Everything else about the problem is edited in the library; Go to problem in the row menu takes you there.

The problem's maximum score comes from the library problem and is shown here, not edited.

Rejudge every submission for a problem

Rejudge in the row menu retests every submission made for that problem in this contest. It asks for confirmation, then runs in the background — the Problems tab shows a banner while it is queued or running, with a link to the contest's Activity tab where you can follow it.

Scores can come out different, so rebuild the scoreboard afterwards if the standing looks stale. Rejudging is not offered on a finalized contest. For rejudging a single submission, see Rejudge submissions.

Remove a problem

Delete in the row menu takes the problem out of the contest and closes the gap in the numbering. The library problem is untouched.

You can add it back, but it comes back as a new contest problem — submissions made against the removed one are not picked up by it. Removing a problem from a running contest is not a reversible edit.

Removing is not offered on a finalized contest.

Export the statements as a booklet

Export statements, in the menu beside Add problem, renders the contest's statements into one printable PDF in a language you choose and downloads it. Statements are taken in contest order, and problems with no statement in that language are left out — check the booklet has every problem in it before you print a hundred copies.

Rendering is slow and heavily rate-limited, so generate it well before you need it rather than repeatedly.