Unreal Engine 5 Documentation has been moved to the Epic Developer Community

Leaderboards give players a way to compete with their friends or the rest of the world for the top score in your game. Games can feature multiple modes that award scores, and each mode can have its own leaderboard. Scoring modes can be ranked highest-to-lowest, as in traditional point-based games, or lowest-to-highest, such as in timed or racing games. The Leaderboard Interface provides developers with the tools they need to display and update leaderboards from within their games.

Scoring Methods

There are three different aspects to defining the way a leaderboard treats scores, each defined within an enumerated type.

• ELeaderboardSort dictates whether scores are sorted at all, and if so, if they are in ascending or descending order.

• ELeaderboardFormat controls formatting. Scores can be raw numbers (like points), or time, either in seconds or milliseconds.

• ELeaderboardUpdateMethod indicates whether the leaderboard should keep a player's most recent score, or that player's best score (according to the sorting method).

Retrieving Leaderboard Data

Leaderboard data can be fairly large, as there may be an entry in each leaderboard your game supports for each user account that has ever played. For this reason, retrieval is done in chunks, and games can request portions of the leaderboard in a few different ways. All methods of retrieving leaderboard data will take a parameter of type FOnlineLeaderboardRead (see FOnlineLeaderboardRead for the relevant data type) that holds the definitions of the tables you want the online service to send back, and will call a delegate of type FOnLeaderboardReadComplete with a bool to indicate success or failure upon completion. The following querying options are supported:

Uploading Leaderboard Data

To write a score for an individual player, use WriteLeaderboards to cache an update (of type FOnlineLeaderboardWrite ) that will later be transmitted to the online service. Each FOnlineLeaderboardWrite object is associated with a session name and a player (identified by an FUniqueNetId ). When the game is ready to commit the session data to the online service's records, FlushLeaderboards will send the cached data and clear it from the local system, calling the Online Subsystem's OnLeaderboardFlushComplete delegate upon completion.