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.

Public Terms

Terms

These terms describe the intended use of the current CustomQueue build and keep the public shell aligned with the app’s actual scope.

Current state

The internal workflow already operates privately. These public routes exist so reviewers can understand the product without logging in first.

Riot scope

Standard API lookup exists where useful. Riot account linking and Tournament API creation are intentionally outside this public surface.

Intended use

The product is intended for a private EUW community that organizes custom matches and wants structured match history, rankings, and admin oversight.

CustomQueue is intended for a private EUW community that wants clearer match structure, cleaner review, and useful long-term context.

Only custom matches created through the application are intended to count toward tracked history and rankings.

Balanced 3v3, 4v4, and 5v5 match shapes are eligible for tracked processing. Uneven teams are untracked by rule.

Result completion may come from Riot Standard API lookup where available, pasted Riot JSON, or local manual import when the match is private/custom.

The current public surface is for explanation, staging, and future review readiness. It is not a promise of open public access.

Operational status

The repository is still in a staged pre-live lifecycle, and the public copy should be read in that context.

Private/local auth, match workflows, deterministic ranking, admin tools, backup/restore, and Standard API developer-key validation exist now.

Live Riot Tournament API orchestration is intentionally not part of this phase.

Future production terms should be expanded before any real public launch, verified staging rollout, or formal submission based on production access.

Access expectations

These terms do not grant public access to the internal workspace.

Local/private access is currently controlled through the application’s internal credential flow.

Reviewer-facing routes such as the landing page, public player pages, policy pages, contact page, and `riot.txt` exist to explain the product and support future staging verification.