Coding problems, the solver, verdicts, tracks, and the record of what you solved.
Search the docs13 guides
What practice is
Coding problems you solve in the browser and a judge that actually runs them - what the parts are, what costs nothing, and what signing in adds.
Finding a problem
Searching the problem list by name or by meaning, the topic, difficulty and status filters, the sort control, and how the list you filtered becomes the one Next walks.
The solver
The layout of a problem page, moving between problems, why the editor holds only your function, how your draft survives a refresh, and what each tab is for.
Running and submitting
What Run checks and what Submit checks, how to try your own input, what gets kept, and what the daily allowance actually limits.
Verdicts and test cases
What each verdict means, why you see every case rather than only the first failure, which two verdicts are our fault, and when an old Accepted goes stale.
Languages and limits
The five languages you can solve in, the time and memory your code gets, why Java starts with less of the budget, and the one thing TypeScript does differently.
Hints and the Approach tab
Hints are free and ladder one at a time but lower a problem's points; the Approach tab is the author's walkthrough, and opening it before you solve makes the problem worth 0 points.
Asking AI for help
The three things Revquix AI will do on a problem, what it costs before you press it, and the four things it deliberately will not do.
How fast is my solution
The Performance report under an accepted submission, how it is measured and ranked, the whole-run charts, the growth analysis, and why none of them ever prints a Big-O.
How scoring works
How a problem's points are measured, how help changes them, how Revisit earns them back, and who appears on the practice leaderboards.
Your practice record
Your practice dashboard's four tabs - Overview, Submissions, Score and Lists - the practice streak, the activity graph shared with your projects, and why we never show your progress as a percentage.
Tracks
Ordered paths through the problem catalogue - how the counts work, what Continue picks, and what happens to a problem that is withdrawn after you start.
Writing a problem
Authoring a coding problem end to end - functions and design classes, test cases including generated ones, how answers are compared, time limits, the checks that must pass before it publishes, importing many problems, and what review looks at.