You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Feb 17, 2021. It is now read-only.
Displaying rankings may be done by showing the top 100 players as well as your position at the bottom (if position > 100) and may be sorted by points, gold/silver/bronze medals, kills etc.
We will updates these values once a game finishes and the .dll is validated on the back-end.
In theory there could be all kind of stats, including outposts taken, drillers produced and so on...
The text was updated successfully, but these errors were encountered:
@billyb2: Should be relatively simple. When asked by the user for global ranking, the server could just sort all players by rank and show the top 100, as well as showing the current player's position and the 5 players above and below them.
We currently have no way of storing, tracking or changing a player's MMR/ranking I don't think. This will eventually all be tied in to the /end_game action and once a game is over the player's MMRs will be updated automatically. Will need to look into how the MMR system works and try to implement it once we get there
@billyb2
But every player's rating is shown in player statistics. As for things like outposts taken, players eliminated, etc., we could add that as a column to player_statistics.
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Opened by @XATEV
Displaying rankings may be done by showing the top 100 players as well as your position at the bottom (if position > 100) and may be sorted by points, gold/silver/bronze medals, kills etc.
We will updates these values once a game finishes and the .dll is validated on the back-end.
In theory there could be all kind of stats, including outposts taken, drillers produced and so on...
The text was updated successfully, but these errors were encountered: