This reference covers the 12 predefined WCA events available when creating a new tournament category in ruTournament. Each event has a short display abbreviation, a Tailwind CSS colour token used in the UI, and a corresponding csTimer puzzle-type identifier used during scramble generation. Understanding how event names map to csTimer puzzle types is important when troubleshooting missing or incorrect scrambles.Documentation Index
Fetch the complete documentation index at: https://mintlify.com/SdazaP/ruTournament/llms.txt
Use this file to discover all available pages before exploring further.
Predefined events
The table below lists every event defined inWCA_EVENT_CONFIG (src/common/wcaEvents.ts), together with the csTimer puzzle type and inspection time parameter drawn from wcaEventMap in src/pages/Tournament/Scrambles.tsx.
The first 12 rows correspond to events with full colour-token support in WCA_EVENT_CONFIG. The final 4 rows (3x3 BLD, 3x3 FM, 4x4 BLD, 5x5 BLD) are present in wcaEventMap only — they support automatic scramble generation but do not appear in WCA_EVENT_CONFIG and therefore have no built-in colour token or abbreviation.
| Event key | Display name | Abbr | csTimer puzzle | Inspection (s) |
|---|---|---|---|---|
3x3 | 3×3 Cube | 3×3 | 333 | 0 |
2x2 | 2×2 Cube | 2×2 | 222so | 0 |
4x4 | 4×4 Cube | 4×4 | 444wca | 0 |
5x5 | 5×5 Cube | 5×5 | 555wca | 60 |
6x6 | 6×6 Cube | 6×6 | 666wca | 80 |
7x7 | 7×7 Cube | 7×7 | 777wca | 100 |
3x3 OH | 3×3 One-Handed | OH | 333 | 0 |
Clock | Rubik’s Clock | CLK | clkwca | 0 |
Megaminx | Megaminx | MGA | mgmp | 70 |
Pyraminx | Pyraminx | PYR | pyrso | 10 |
Skewb | Skewb | SKB | skbso | 0 |
Square-1 | Square-1 | SQ1 | sqrs | 0 |
3x3 BLD | 3×3 Blindfolded | — | 333ni | 0 |
3x3 FM | 3×3 Fewest Moves | — | 333fm | 0 |
4x4 BLD | 4×4 Blindfolded | — | 444bld | 40 |
5x5 BLD | 5×5 Blindfolded | — | 555bld | 60 |
3x3 BLD, 3x3 FM, 4x4 BLD, and 5x5 BLD are not listed in WCA_EVENT_CONFIG and therefore have no built-in colour token or abbreviation badge. They are, however, recognised by wcaEventMap in Scrambles.tsx, so naming a custom category with one of these exact key strings will enable automatic scramble generation using the correct csTimer puzzle type.WCA_EVENT_CONFIG
The full configuration object exported fromsrc/common/wcaEvents.ts. Each key is the canonical event name string used throughout the application — in CategoryLocal.name, route parameters, and result views.
| Property | Type | Purpose |
|---|---|---|
abbr | string | Short abbreviation rendered in compact badges and table headers |
color | string | Tailwind text-colour class for foreground text on dark backgrounds |
bg | string | Tailwind background-colour class for filled badge backgrounds |
Custom categories
ruTournament fully supports custom (non-WCA) categories. During category creation, type any name that does not match a key inWCA_EVENT_CONFIG and the category will be saved with that name. Custom categories work identically to predefined ones for round management, group generation, competitor assignment, and result entry.
There are two limitations to be aware of:
- No colour token —
WCA_EVENT_CONFIG[category.name]will beundefinedfor custom categories. Components that render event badges should fall back gracefully (e.g. a neutral grey badge). - Scramble generation fallback — The scramble generator looks up the category name in
wcaEventMap. If no match is found, it falls back to the333(3×3) csTimer scrambler. This means custom categories will receive 3×3-style scrambles unless you name them to match a key already present inwcaEventMap.
Inspection time
Several larger WCA puzzles require extra time for physical inspection before each solve. This is modelled as the second element of eachwcaEventMap tuple in Scrambles.tsx and passed to the csTimer worker at scramble-generation time.
0 means no inspection countdown is displayed. This parameter is used by the csTimer scramble engine only and does not affect result entry or average calculation within ruTournament.