mtg tournaments: multi-stage Top cut for pod tournaments (semifinal pods)
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 25/100
- Issue type
- Feature
- Clarity
- Mostly clear
- Activity status
- Active
- Tech stack
- typescript
- Domain
- backend
Research direction
Start with the tournament vocabulary in services/mtg/GLOSSARY.md and locate the existing pod tournament planner and its single-table Top cut. Map how standings seed participants, how seat choice works, and how results are represented before defining multi-stage cuts. Done means supporting semifinal pods and advancing winners to a final table, including win/draw outcomes, deeper cut seeding, and seed-based seat choice at each stage.
Written by the indexing model from the issue text.
Description
The first version of the mtg tournament planner gives pod tournaments (Table size 3–5) a single final table as their Top cut: the top n Participants by standings, n = Table size, the top seed picking their seat.
Larger cEDH events cut deeper, e.g. Top 16 into four semifinal pods whose winners meet at the final table (or Top 10 with a play-in round). This issue tracks supporting such multi-stage Top cuts:
- cut sizes beyond one table and how they are seeded into semifinal pods
- how semifinal results (win / draw) advance to the final table
- seat choice by seed at each stage
Out of scope for the first version; see services/mtg/GLOSSARY.md (Tournaments) for the vocabulary.
- Dominant language
- TypeScript
- Stars
- 0
- Forks
- 1
- Avg merge
- 10h 56m
- Merged PRs (30d)
- 34
Getting set up
This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.
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.
More from myOmikron/code
-
wayfinder:task
Difficulty 1/5 Under an hour Newbie friendliness 90/100
Maintainers usually reply within 1 day
-
wayfinder:task
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
myOmikron/code#102 · 2 comments ·
Maintainers usually reply within 1 day
-
ready-for-agent
Difficulty 5/5 Over a week Newbie friendliness 18/100
Maintainers usually reply within 1 day
-
needs-triage
Difficulty 5/5 Over a week Newbie friendliness 25/100
Maintainers usually reply within 1 day
-
needs-triage
Difficulty 5/5 Over a week Newbie friendliness 25/100
Maintainers usually reply within 1 day
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 1 day
-
enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 79/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
Maintainers usually reply within 1 day
-
Renaming a projectOpen
Difficulty 2/5 1-3 hours Newbie friendliness 66/100
equinor/prisma-decision-web#927 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
bigbluebutton/bigbluebutton#26166 ·
Maintainers usually reply within 1 day