CustomQueue
Built for smarter players
Competitive match insight for players who want more structure, clearer feedback, and less noise around the games they already enjoy with friends.
Public routes stay read-only. Member routes such as `Member Matches` and `Member Login` require existing access.
Read your game
Less noise, more insight for players who want to have fun with friends.
CustomQueue helps competitive players read their performance, understand their patterns, and improve with more clarity.
Built for custom sessions, repeat nights, and groups that want cleaner feedback than a spreadsheet or a noisy highlight reel.
Read your trends
See how sessions, wins, losses, and recurring outcomes add up over time.
Spot your habits
Notice repeat decisions and player tendencies that casual scorekeeping usually misses.
Improve with clarity
Keep custom nights fun and competitive while still learning something useful.
How it works
CustomQueue keeps the match night structured from queue to result so players can review what happened without turning the experience into admin noise.
01
Track the night
Create matches, keep lineups readable, and hold the session inside one clean queue.
02
Finish results cleanly
Use Standard API where it helps, then fall back to Riot JSON or fast manual import where customs need a practical path.
03
Read the pattern
Use player, team, and leaderboard views to understand what keeps repeating and what is worth changing.
What you can read
The product is meant to turn matches into signals that are actually useful after the game ends.
Form shifts across repeated match nights
Win and loss patterns that matter over time
Player and team trends without loud presentation
A clearer sense of what to repeat, fix, or ignore
Why it helps
CustomQueue is designed to feel useful first: precise structure, calm presentation, and enough competitive clarity to make a session worth reviewing.
Premium utility
Clean structure and useful context instead of loud gaming-shop energy.
Competitive, not dramatic
Serious enough to help players improve without turning friendly sessions into theatre.
Built for repeat nights
Designed around custom sessions, rematches, and reading the shape of a whole evening.
Less noise. More direction.
The goal is clarity: what happened, what keeps repeating, and what is worth adjusting next time.
Built for smarter players
Play with more structure, confidence, and direction.
CustomQueue is not trying to be loud. It is trying to be useful. Read your game, understand the patterns behind a session, and keep custom nights competitive without losing the fun.
Works today
Match flow, leaderboards, recovery tooling, and structured result import are already part of the product.
Riot scope
Standard API support exists where useful. Tournament API creation and Riot account linking are intentionally outside this phase.
Public player access
The product is being prepared for real online review, so player-facing entry points now explain how public review and future onboarding are intended to work.
Available now
Public read-only leaderboard, player registration, player-access guidance, legal pages, support contact, and member login.
Still coordinated
New public accounts start as Player only. Elevated roles and live Riot account onboarding remain outside this phase.
Why future Tournament API access would help
This is a future-facing product explanation, not a claim that Tournament API support already exists.
Tournament API access would make online match creation, lobby association, and result linkage more reliable for a real public player flow.
It would reduce reliance on manual imports and reviewer-only explanations when the platform is shown as a product rather than only an internal tool.
Today, the platform already demonstrates the product foundation: tracked match flow, leaderboards, admin operations, and structured result handling.
Reviewer note
Public clarity first. Technical cues second.
This landing page is meant to explain the product quickly. Reviewer and staging checks still exist, but they stay lower in the page so the public surface feels like a product, not a checklist.
Open `Leaderboard` and `Matches` to review the real product surface.
Use `Privacy`, `Terms`, `Contact`, and `riot.txt` to confirm the public shell is coherent.
Use `Member Login` only when someone explicitly needs the protected internal workflow.
Read Riot scope conservatively: Standard API support exists, Tournament API creation does not.
Staging cues
Domain target: customqueue.com
Metadata host: customqueue.com. `riot.txt` stays placeholder-only until Riot requests a real token.