Hello, welcome to a mock CCC! Here are the parameters of the contest:

• Contestants must write the mock CCC under CCC rules. Notably, contestants may not consult the Internet outside of accessing the relevant parts of the contest via the DMOJ platform or consulting language documentation, and contestants may not use any prewritten code.
• Contest duration: 3 hours.
• Number of problems: 5, full feedback, with subtasks. The problems follow the CCC format of being worth 15 marks each. All problems have explicit subtasks.
• Not rated. This change was made after the contest ended.
• Scoreboard will be hidden.
• Number of submissions allowed per problem: 50.
• Checkers for problems: Unless otherwise specified, identical. The contest will follow the standard convention of having all lines terminate in a \n character.
• Testers for this contest: Cthulhu, Kirito, koosaga, ksun48, quantum, WallE256, and y0105w49.

Clarification requests for the contest must be routed through the clarification system provided on DMOJ, and not through other channels including but not limited to Slack. Furthermore, all clarification requests will be handled the way they normally are in IOI. Note that, in particular, clarification requests must come in the form of yes/no questions.

Due to rampant issues with cheating on contests that has happened recently, any suspicious behavior during the contest window may result in your rating being impacted negatively. Such behavior includes, but is not limited to:

• Registering for the contest with at least two accounts.
• Participating in the contest with an account that is not your primary account.
• During the contest window, talking about the contest in more detail than answering a yes/no question about whether one participated in the contest. This includes, but is not limited to, posting spoilers about the contest and public speculation of the contest.
• Attempting to exploit bugs in the platform to subvert the constraints of the contest.

Punishments may include performance being unrated or, for more serious infractions, being forcibly ranked at the bottom of the scoreboard.

Before the contest date, you may wish to check out the tips and help pages.

The contest consists of 5 questions with a range of difficulty from CCC Senior 1 to CCC Senior 5. It is highly recommended to read all of the problems. You will have 3 hours to complete the contest. After the contest window begins, you may begin at any time. Your personal timer will start counting down, and you will be able to submit until 3 hours from when you started, or until the hard deadline, whichever comes first.

After joining the contest, you proceed to the Problems tab to begin. You can also go to Users if you wish to see the rankings.

We have listed below some advice as well as contest strategies:

• Start from the beginning. Ties will be broken by the sum of times used to solve the problems starting from the beginning of the contest. The last submission time of your highest score will be used.
• Remove all extra debugging code and/or input prompts from your code before submitting. The judge is strict — your output must match the judge output exactly.
• Do not pause program execution at the end. The judging process is automated. You should use stdin / stdout to perform input / output, respectively.
• It is guaranteed that all the problems will be solvable with C++. We do not guarantee that all problems are solvable in C, Java or Python.

At the end of the contest, you may comment below to appeal a judging verdict. In the case of appeals, the decision(s) of our staff is final.