6.11 NEX: Ranking

Applications that use the CTR-NEX ranking features must comply with all the Guidelines listed in this chapter. 

6.11.1 Linking Ranking Data

Ranking data such as scores and metadata can only be recorded once per each combination of category, principal ID and NEX unique ID.
Furthermore, shared data can only be recorded once per each combination of principal ID and NEX unique ID.

The principal ID is assigned the first time the system connects to the friend server, and only one is saved per system. You can use the UtilityClient::AcquireNexUniqueId function to get multiple NEX unique IDs. Since ranking data is linked to the combination of principal ID and NEX unique ID on the server, if you wish to manage ranking data separately for separate instances of save data, you can distinguish between save data by using separate NEX unique IDs. In contrast, if you use only one instance of save data but the same save data is used by more than one principal ID (as a result, for example, of playing the game on more than one system), then the ranking data for each principal ID is recorded separately.

Take care to avoid problematic situations where the scores stored in one instance of save data are registered to the server multiple times from multiple systems. Possible ways of handling this include:

  • Only register scores when the user has achieved a high score.
  • Only allow scores to be uploaded from the system that created the save data.
    If you use this method, Nintendo recommends notifying the user at an appropriate time that other accounts cannot upload score data.
Note:

The principal ID is an identifier that is unique to each system, and can only be changed by initializing the system with the Format System Memory operation.

■ Number of NEX Unique IDs Issued

Since NEX unique IDs are provided with the goal of allowing each user to record their own score, it is prohibited to get more NEX unique IDs than you need. Get up to a number of NEX unique IDs equal to the number of principal IDs multiplied by the number of instances of save data. Save the obtained NEX unique IDs in the backup memory region. It is acceptable to obtain NEX unique ID again if a saved ID got lost when save data was deleted. If you need NEX unique IDs in excess of this amount, contact Nintendo at support@noa.com.

■ Handling Launch on a Different System

If the user launches the application from a different system, then the principal ID will be different and therefore the scores will be registered on the server as from another user. For this reason Nintendo recommends displaying one of the messages below, in accordance with your application's specifications. Display the message at a time that does not disadvantage the user.

  1. If scores can be registered from different systems:

    If you are registering a new score from a different system, inform the user that ranking data is recorded separately for different systems, and moreover obtain the user's consent to register scores from a different system. For example, you could display a message such as, "Ranking scores are registered separately for each system. Register a new score with this system?" and get permission from the user before registering the score.

  2. If scores cannot be registered from different systems:

    Inform the user that ranking data is recorded separately for different systems, and that since this system is not the same system that registered ranking data previously, it cannot register any new scores. For example, you could display a message such as, "Ranking scores are registered separately for each system. You cannot register a new score with this system, because previous scores were registered from a different system."

Note:

Users who wish to continue using the same storage on a different system (for example, after purchasing a new system) must perform System Transfer. This will enable them to continue using the same scores, because their principal ID will also be transferred.

6.11.1.1 Getting NEX Unique IDs

Guideline Item

The number of NEX unique IDs gotten by the application must not exceed the number of principal IDs multiplied by the number of save data instances.

Software to Be Tested

Applications that implement CTR-NEX ranking.

Test Method

1. On NMAS, go to Check the Number of API Calls and enable logging of function calls.
2. Connect the target application to the game server, then execute the sequence you wish to check.
3. From Check the Number of API Calls on NMAS, check the function call history.
4. Disconnect the target application from the game server.
5. Reconnect the target application to the game server, and execute the same sequence as step 2.

Pass/Fail Determination

Passes if the number of calls to nn::nex::UtilityClient::AcquireNexUniqueId is either zero, or is no more than the number of save data instances per system.

 


CONFIDENTIAL