Instances of SC_Score model the score achieved by a particular user in a particular game session.

Instances of SC_Score must contain, at minimum, a result, which is typically the main numerical outcome achieved by a user of the game. A Score is achieved by a player of your game at the end of gameplay.

  • Result is the primary score that is achievable in your game.

  • A score can be a simple numerical score, one that is based on time or something more complex, having multiple criteria, such as the number of hits made, the average speed, or the maximum speed.

  • You can model the score using the following:
    • Result: Primary score, mandatory

    • Minor result: secondary score, optional

    • Level: secondary score, optional

  • A score is submitted to the server. Score sorting decides the winner of a challenge and the leaderboard rankings.

  • Scores can be sorted in ascending or descending order.
    • Descending order: Highest score is on top.

    • Ascending order: Lowest score is on top. E.g., the fastest user wins a game; sorting as time.

  • If modes are defined, Scoreloop generates separate leaderboards for each mode in the game.

The result, minor result, and level are used to compare scores. You can configure the comparison schema on our developer website.

Two data controllers that manage the scores are:

Instances of SC_Score can also contain information about score rank, which is the position of the score on a Scoreloop leaderboard. However, the rank of a score will generally only have a meaningful value when it is retrieved from the server using an SC_ScoresController.

Basic use: Score objects are returned in the following scenarios:

See also:

SC_ScoreController, SC_ScoresController, Leaderboards

Last modified: 2014-05-14

Got questions about leaving a comment? Get answers from our Disqus FAQ.

comments powered by Disqus