---

MMR Range

We adjusted the MMR range of our rating system to bring it down a bit. Due to the large range we had before, MMR differences between teams could be interpreted as if teams were more unbalanced than they actually were. If you want to know how balanced or unbalanced a match was, you should look at the win probability charts of the match.

This change does not affect the inner workings of the system; it only changes how we display our MMR numbers. We expect rating changes to decrease by 20% to account for the smaller MMR range.

Uncertainty Interval

We also changed another aspect of MMR display. Previously, we were showing the player's most likely MMR; now, we show the minimum MMR the player most likely has, which is the recommended way to display MMR for the rating algorithm we use.

This change has the benefit that new accounts won't overshoot in MMR anymore if they have a small win streak, as the system now accounts for the uncertainty in the rating when displaying it. New players naturally have high uncertainty in their rating, as the system can't know yet if the player's rating is accurate. 'Minimum' refers to the lower bound of the uncertainty interval for the player's rating, representing the lowest rating that the player is estimated to have with a probability of 99%.

New Subranks

In addition, we have implemented subranks for the Master rank, categorizing players into more groups for higher precision. Previously, the Diamond rank had a broad range, overlapping with the Master MMR range. With the influx of new players, we can now further subdivide this range into distinct ranks.

As a last note, I want to clarify that our ratings represent skill relative to the current player base a player plays against. This means that PlayStation players who disable crossplay have a separate pool of players they play against, and therefore, their rank is relative to those players, not the full player base, including PC players. This also technically means that all ranks of players in a certain region are relative to the other players in the same region, as most players play mainly in one region.

---

We don't impose rate limits at the moment, but I'd kindly ask for responsible usage to avoid the need for it.

---

Dashboard hero statistics

Returns general stats about the heroes.

/dashboard/hero_statistics.json

Optional arguments:

hero_ids=[{hero_id},{hero_id},...]   // takes an array of hero ids - leaving this empty returns all heroes
time_frame={value}                   // accepts: [ALL, 3M, 2M, 1M, 3W, 2W, 1W, 1D]

---

Matches:

Returns matches in chronological order.

/matches.json

Optional arguments:

timestamp={some_timestamp}          // unix timestamp from when to start fetching, do not use to paginate!
cursor={some_cursor_id}             // leave empty in first request
                                    // following requests should contain the cursor of the previous API response

per_page={number}                   // max number of matches per page - limited to 100

---

Match:

Will give you all sorts of data of a single match.

/matches/{match_id}.json

---

Leaderboard

/players.json

Optional arguments:

page={number}                       // lets you paginate
filter[name]={name}                 // search for player names
filter[include_inactive]={number}   // include inactive players - accepts: [0, 1]
filter[include_unranked]={number}   // include unranked players - accepts: [0, 1]

---

Player:

This endpoint will give you general information about a player.

/players/{player_id}.json

---

Player matches:

This endpoint will give you the match history of a player.

/players/{player_id}/matches.json

Optional arguments to filter and paginate the match history:

time_frame={value}             // accepts: [ALL, 3M, 2M, 1M, 3W, 2W, 1W, 1D]
page={number}                  // lets you paginate
per_page={number}              // max number of matches per page - limited to 100
filter[hero_id]={hero_id}      // hero the player played
filter[role]={role}            // role the player played - accepts: [offlane, jungle, midlane, carry, support]
filter[player_name]={name}     // player that was present in the game

---

Player statistics:

General player statistics.

/players/{player_id}/statistics.json

Optional arguments:

time_frame={value}   // accepts: [ALL, 3M, 2M, 1M, 3W, 2W, 1W, 1D]

---

Player hero statistics:

Returns general stats about the heroes of a player.

/players/{player_id}/hero_statistics.json

Optional arguments:

hero_ids=[{hero_id},{hero_id},...]   // takes an array of hero ids - leaving this empty returns all heroes
time_frame={value}                   // accepts: [1Y, 3M, 2M, 1M, 3W, 2W, 1W, 1D]
filter[role]={role}                  // role the player played - accepts: [offlane, jungle, midlane, carry, support]

---

Player common teammates

Returns information about the teammates a player played most with.

/players/{player_id}/common_teammates.json

Optional arguments:

time_frame={value}   // accepts: [ALL, 3M, 2M, 1M, 3W, 2W, 1W, 1D]
count={number}       // number of mates to return - limited to 100

---

Items & Heroes

These are self-explanatory.

/items.json
/items/{item_name}.json

/heroes.json
/heroes/{hero_name}.json

---

Builds

/builds.json
/builds/{build_id}.json

Optional arguments:

page={number}                       // lets you paginate
filter[player_id]={player_id}       // player who created the build - only works for users who claimed a profile
filter[hero_id]={hero_id}           // hero the build is for
filter[role]={role}                 // role the build is for - accepts: [offlane, jungle, midlane, carry, support]
filter[name]={name}                 // title of the build
filter[skill_order]={any_value}     // has skill order? - if set to any value, returns only builds with skill orders
filter[current_version]={any_value} // is current_version? - if set to any value, returns only builds of the current game version
filter[modules]={any_value}         // has modules? - if set to any value, returns only builds with modules
filter[order]={value}               // sorts builds - accepts: [latest, trending, popular]

---

New features

/whatis With this new command, you can query words and phrases that you'd like to find information on. Ever wanted to know what a lane freeze is? Or what cs stands for? This command is for you to learn; beginner, intermediate and advanced techniques or phrases! If you wish to quickly look something up in the middle of a conversation, you may use the optional parameter my-eyes-only: True to stop you from embarrassing yourself.

The right page didn't show up? Perhaps there are grammatical mistakes? Feel free to provide feedback on this new feature on what it could improve on. You may also provide feedback on resources to create. I would like to help everyone and provide questions for everything to help introduce new players to MOBAs and Predecessor while also providing resources for veterans.

Verified users

New features are available for a small group of trusted users. Verified players will be able to verify three other friends of theirs. Once you've been verified, you may recieve a notification on some of the new commands available to you:

Available commands to verified users: /verify You can pass on this verification to 3 other friends of your choice. BE AWARE: You cannot take away verification that you have given. So choose wisely.

/comment You can now leave comments on player's profiles. Tell them how well they've played or just insert some unfunny joke.

/claim You can now claim a Predecessor player ID. You're restricted to 1 player ID and you can switch it anytime. Once you've claimed an ID, you may bring up your corresponding Predecessor account in ANY narb.app player query by using your Discord @

Remember that you cannot claim an ID that is already claimed. If someone is sitting on your ID, let a bot developer know and they'll sort it out for you.

/resource "resource" refers to the information pages fetched from using /whatis You can now view all available resources at once as well as create new ones. The newly created ones will have to be approved first before they are available to anyone else, as well as editing a previously approved resource will require approval after submiting the edit.

Helping in the creation of resources will be heavily appreciated. Chat GPT usage is recommended :PepeBusiness:

Duplicate resources with similar topics will not be approved.

Changes

• Changed /profile stats look slightly to accommodate for verified users. Also removed unnecessary spacing on the bottom.
• Removed footer on /profile stats when viewing a singular hero. ## :hammer: Bug fixes
• Fixed rank emojis not displaying on match stats
• Fixed sorting by match on /player heroes [player:] [order:match]
• Now it correctly displays Magical Lifesteal as a percentage
• Updated Estimated potential gold efficiency for patch v0.7.2
• Fixed progress bar to correctly display a 0%
• Added missing % sign in /player stats when viewing singular hero stats to compact the view.

What to expect next?

/memory save [match-id] [title] [description] /memory show You'll be able to save matches and give them titles and descriptions. This way you'll never lose that 27/0 Kallari stomp game that you're so proud of. You can also save your friends' games! This will also be available in Context Menu form.

/explore-patch [version] [compare-version] [query] You'll be able to compare Hero, Item and general changes with patches. You want to know what Murdock's stats were at the beginning of the game as compared to now? This command will highlight the changes. You'll also be able to specify the current patch by using 'current' in the [version] parameter.

You don't have to compare two versions. [compare-version] and [query] will be optional so you can simply learn about changes on a certain patch.

/compare multiple-players [players] [stat] [recent-performance] [hero] You'll be able to compare multiple players and rank them based on a stat. The stats you'll be able to compare the players on are: * MMR * Average KDA * Matches played You can only select 1 of those stats

You'll also be able to optionally specify hero and/or recent recent performance. Recent performance will only look at their last 10 games. Any player name that was not able to be found will not be included in the result; as well as if recent performance is enabled, anyone who did not have at least 10 games will also not be shown.

/remind-me [options:("Comp Night", "Ranked")] As my understanding is, Ranked mode will have similar availability as Comp Night has; so with this command, you can toggle on/off notifications from the bot in your DMs for when Comp Night and Ranked Mode will be online. You'll get a notifcation 15 minutes before it goes live to ensure you have time to prepare for it.

/role You'll be able to choose your main role. This would expand functionality in some future commands.

/lobby My idea for this is still not finalized; but it would be used for friends to setup custom lobbies to play on. Server owners may schedule a custom lobby where server members will be able to show interest. The lobby will also have functionality to randomize teams. Additionally, the server owner would also be able to choose to enable role-locked lobby, which will allocate players based on their chosen /role and what they play. This way, everyone will be able to see what players are still needed for the lobby.