Headless Ring Mode
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 2
- Forks
- 1
- Avg merge
- 1m
- Merged PRs (30d)
- 5
Description
Summary
Add a headless mode for rings that allows a ring to operate without a moderator.
Problem
Some rings may not have a moderator available during the tournament. In these cases, the admin only needs to know which category is currently running and which category is coming up next.
Proposed Solution
Introduce a Headless Mode that can be enabled for a ring.
When enabled:
- No moderator session is required.
- No match tracking is performed.
- No
matches_completedupdates are required. - The system simply tracks the current category and the next category in the queue.
- Admin can manually advance the queue when a category is finished.
Expected Behavior
-
Admin enables headless mode for a ring.
-
The ring displays:
- Current running category
- Next category
-
When the current category is completed, the admin advances the queue.
-
The next category becomes the current category.
-
Queue progression continues until all categories are completed.
Acceptance Criteria
- Ring can operate without a moderator.
- Current and next categories are always visible.
- Admin can manually advance to the next category.
- Match-level progress tracking is bypassed.
- Queue order remains unchanged.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by tracing the ring queue, moderator session, and match-tracking entry points. Identify how the admin view exposes the current and next categories and how queue advancement is handled. Done means a ring can run without a moderator or match-level progress while preserving queue order and allowing manual advancement.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- full-stack
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100