Hyperion integration · in development
In developmentSix proposed queues, two rulesets
The local integration defines classic Rule 1 and anti-meta Rule 2 identities for 1v1, 2v2, and 3v3. Each is a separate matchmaking identity.
Hyperion working-tree integration- Rule 1 maps to classic rules without a mutator object.
- Rule 2 maps to Hyperion rules with exactly mutators.antiMeta = 1.
- The 1v1 Rule 3 identity remains in result/type schemas but is not queueable.
- Public availability still requires map pools, enabled schedules, installation configuration, and a deployed service.
- Formats
- 1v1 · 2v2 · 3v3
- Map style
- Veto
- Ratings
- Independent per identity
- Release state
- Needs confirmation