Documentation
Rating Types Explained
Understanding how different match formats affect player and team ratings
What are Rating Types?
Rating types determine how matches are grouped for calculating Elo ratings. The Team Up system supports ten different rating types, allowing you to track performance in various ways depending on your game's needs.
For example, you might want to track a player's overall performance across all match types, or maintain separate ratings for 1v1s vs 2v2s. Rating types give you the flexibility to organize your leaderboards however makes sense for your community.
Player Ratings
Individual player ratings across different match formats
Player Global (All)
player_global_allTracks player performance across ALL match types - 1v1s, 2v2s, 3v3s, free-for-alls, everything combined into one universal rating.
USE CASE
Best for communities that play multiple formats and want one overall skill rating per player.
PARAMETERS
None required
EXAMPLE
A player with 1500 rating who plays 1v1s, 2v2s, and 4-player FFA all affecting the same rating.
Player Global (Even)
player_global_evenTracks player performance only in matches with evenly-sized teams (2v2, 3v3, 1v1v1, etc.). Excludes uneven matches like 2v3.
USE CASE
For games where even team sizes represent the core competitive experience.
PARAMETERS
None required
EXAMPLE
All 2v2 and 3v3 matches count toward this rating, but 1v2 or 2v3 matches don't.
Player Global (Uneven)
player_global_unevenTracks player performance only in matches with uneven team sizes (2v3, 1v2, etc.). Useful for asymmetric game modes.
USE CASE
For games with intentional team size imbalances or asymmetric gameplay.
PARAMETERS
None required
EXAMPLE
A 1v2 match where the solo player is expected to be higher skilled.
Player Broad
player_broadTracks separate ratings for each team size category where ALL teams in the match are the same size (all 2s, all 3s, etc.).
USE CASE
When you want separate ratings for playing with different team sizes in evenly-matched formats.
PARAMETERS
Requires: team_size (e.g., 2 for all matches where every team has 2 players)
EXAMPLE
A player has separate ratings for: 2s (includes 2v2, 2v2v2, etc. where all teams are size 2), 3s (includes 3v3, 3v3v3, etc. where all teams are size 3), etc.
Player Specific
player_specificTracks separate ratings for exact match formats (1v1 separate from 2v2 separate from 1v1v1, etc.).
USE CASE
When each specific format represents a unique competitive mode that should be ranked separately.
PARAMETERS
Requires: versus (e.g., '2v2', '1v1v1', '3v3v3')
EXAMPLE
A player has completely separate ratings for: 1v1 matches, 2v2 matches, 3v3 matches, 1v1v1 FFA matches.
Player Choices
player_choicesTracks separate ratings for each unique combination of player choices (character, class, weapon, etc.) configured on the leaderboard. The same player can have different ratings for different in-game selections.
USE CASE
For games where selections like characters, classes, decks, or weapons significantly affect performance and you want per-selection skill tracking.
PARAMETERS
Requires option sets configured on the leaderboard from the web dashboard (Option Sets page, then Customize → Player Choices)
EXAMPLE
A fighting game player has separate ratings per character: Ryu (1580), Ken (1320), Chun-Li (1450). With multiple option sets (Character + Weapon), each combination gets its own independent rating.
Team Ratings
Ratings for persistent teams playing together
Team Broad
team_broadTracks ratings for consistent teams based on team size, where ALL teams in the match are the same size.
USE CASE
For tracking premade team performance in evenly-sized team matches.
PARAMETERS
Requires: team_size
EXAMPLE
A specific duo (Player A + Player B) has one rating for 2s matches (2v2, 2v2v2, etc. where all teams are size 2).
Team Specific
team_specificTracks ratings for consistent teams in specific match formats.
USE CASE
For competitive teams that specialize in specific formats.
PARAMETERS
Requires: versus (e.g., '2v2')
EXAMPLE
A duo has separate ratings for: their 2v2 performance vs their performance in 2v2v2 matches.
Team Alias Ratings
Ratings for named teams created with team IDs (requires /team_admin)
Team Alias Broad
team_alias_broadRatings for named teams (created with /team_admin) based on team size, where ALL teams in the match are the same size.
USE CASE
For organized teams with official names competing in evenly-sized team matches.
PARAMETERS
Requires: team_size
EXAMPLE
Team 'Phoenix Squad' has ratings as a 5-player team in 5s matches (5v5, 5v5v5, etc. where all teams are size 5).
Team Alias Specific
team_alias_specificRatings for named teams in specific match formats.
USE CASE
For organized league play with teams specializing in specific formats.
PARAMETERS
Requires: versus (e.g., '5v5')
EXAMPLE
Team 'Phoenix Squad' has separate ratings for 5v5 vs 5v5v5 matches.
Quick Reference
| Rating Type | Value | Required Parameters |
|---|---|---|
| Player Global (All) | player_global_all | None |
| Player Global (Even) | player_global_even | None |
| Player Global (Uneven) | player_global_uneven | None |
| Player Broad | player_broad | team_size |
| Player Specific | player_specific | versus |
| Player Choices | player_choices | option sets |
| Team Broad | team_broad | team_size |
| Team Specific | team_specific | versus |
| Team Alias Broad | team_alias_broad | team_size |
| Team Alias Specific | team_alias_specific | versus |
How to Use Rating Types
In Discord Commands
Specify the rating type when displaying leaderboards, viewing player stats, or creating tiers:
/leaderboard display_leaderboard rating_type: player_global_all/player stats rating_type: player_specific versus: "2v2"/tiers create rating_type: player_broad team_size: 2Setting Default Rating Type
Set a default rating type for your server to avoid specifying it every time:
/default_rating_type set rating_type: player_global_allIn the REST API
Include rating_type in your API requests:
GET /api/leaderboard?rating_type=player_global_all
GET /api/player/stats?rating_type=player_specific&versus=2v2
GET /api/leaderboard?rating_type=player_broad&team_size=3Choosing the Right Rating Type
Use Player Global All When:
- • You want one universal skill rating per player
- • Players compete in multiple formats casually
- • You have a small community and want to keep it simple
Use Player Specific When:
- • Different formats require different skills
- • You run competitive leagues for specific formats
- • Players specialize in certain match types
Use Team Ratings When:
- • You have premade teams competing together
- • Team synergy is important in your game
- • You want to track team performance separately
Use Player Choices When:
- • Your game has character, class, or weapon selection
- • You want to know who's the best with each pick
- • In-game selections significantly affect performance
Use Multiple Rating Types When:
- • You have diverse competitive modes
- • You want separate ranked ladders for different formats
- • Your community is large and active
Common Questions
Can I use multiple rating types at once?
Yes! Each match automatically updates all applicable rating types. A 2v2 match will update player_global_all, player_global_even, player_broad (team_size=2), player_specific (versus=2v2),
and any team ratings if players are on registered teams. You just choose which one to display.
Can I switch the rating type I display?
Yes. Since all rating types are calculated automatically for every match, you can switch which
one you display at any time without losing data. Just update your /leaderboard display_leaderboard command with a different rating_type parameter.
Do I need to recalculate ratings if I switch types?
No recalculation needed. All rating types are maintained in parallel from the start. Switching which rating type you display is instant - the historical data already exists.
What's the difference between Broad and Specific?
Broad groups by team size across all formats. A player's "2s" rating includes 2v2, 2v2v2, 2v2v2v2, etc.
Specific tracks exact formats separately. A player's 2v2 rating is different from their 2v2v2 rating.
Which rating type should I start with?
Start with player_global_all - it's the simplest and works for most communities.
As your community grows and you identify specific needs (separate 1v1 vs 2v2 rankings, team tracking, etc.),
you can switch to or add more specific rating types.
What is Player Choices?
Player Choices tracks separate Elo ratings based on in-game selections like characters, classes, or weapons. Create option sets on the Option Sets page, then assign them to a leaderboard from its Customize → Player Choices tab.
The same player can appear on the leaderboard multiple times with different choice combinations and independent ratings. Standard rating types still update alongside choice ratings.