Map pooling
Public and internal suggestions, votes, flairs, pool slots, imports, publishing, reuse and archive behavior.
Configuration toggles
| Control | Effect |
|---|---|
| Allow public map suggestions | Players can submit maps into the public suggestion queue. |
| Automatically add maps after threshold | A public suggestion reaching the configured vote score enters internal suggestions. |
| Minimum vote score | Threshold used by automatic eligibility. |
| Require threshold before poolers can use a map | Prevents using below-threshold public suggestions in a pool. |
| Hide public suggestions from other players | Submitters do not see competing public submissions. |
| Show public pooling recommendations | Poolers can copy maps from archived public pools into internal suggestions. |
| Archive published pools when concluded | Completed tournament pools are copied to the public archive. |
People and visibility
Head poolers configure the process, staff and flairs. Poolers add internal suggestions, review public submissions, import playlists, inspect map details/difficulties, discuss, vote and place maps. Players should see final contents only when a pool is deliberately published. Draft does not mean public.
Suggestions and review
Every suggested map should be evaluated for hash/version, characteristic, difficulty, duration, BPM/NJS where relevant, mapping quality, safety, gameplay category, bias and rule compliance. Comments hold detailed pooling notes. Votes support review but do not replace head-pooler judgment or conflict-of-interest handling.
Filters include minimum score, text, flair, target pool, target type, best-of, status, vote state and “only missing slot flairs.” Analysis is permission-gated (pooling:maps:runAnalysis) and should be treated as decision support.
Flairs, targets and slots
Flairs classify maps (for example technical, speed, accuracy or stamina). A pool can target qualifiers, a best-of number or a custom use, with target map count and notes. Slots have labels and optional required flairs. Validate that imported/selected map difficulty and flair satisfy the intended slot.
Pool lifecycle
- Create a draft with name, artwork, target, target count and slot plan.
- Add maps from internal suggestions, playlist imports or permitted archive recommendations.
- Resolve duplicates, missing flairs and difficulty/characteristic mismatches.
- Review discussion and votes; confirm the set is balanced and rule-compliant.
- Publish at the announced time.
- Assign the pool to the intended matches and match flows.
- After completion, verify archive behavior if enabled.
Pools can be downloaded and reused as resources. Publishing and archiving can expose previously private decisions, so remove confidential notes from public-facing fields.