2. User Management

2.1. Managing User Information

NEX uses the principal ID to recognize users. The principal ID is assigned the first time the client connects to the friend presence server — hereafter, the friend server — and is saved in the CTR system as a completely unique ID. Although it never conflicts with another user, the principal ID is set to an invalid value before first connecting to the friend server, and it cannot be used.

2.2. Game Server ID and Access Key

With NEX, each application has a game server to use for matchmaking and ranking features. To log in to a game server, you need a game server ID to identify the server and an access key to access it. Maintain strict control over the game ID and password because they are given out specifically to each application. To have a new game server ID and access key issued to you, submit an application through the Online Title Management Service (OMAS).

Comments

A title is assigned the same game server ID and access key, and it uses the same game server in different regions. To perform matchmaking between different game titles, match these parameters to one of the titles.

Comments

If you do not want to make matchmaking and ranking data visible across regions, you must specify search criteria to restrict access from your application.

2.3. Managing Friend Relationships

CTR stores a common friends list that can be used by all games on the console, and the ability to register or delete other users is a standard function found on the HOME Menu. There is no need for applications to implement a unique interface for managing the friends list, or for users to register separate lists for each application. (For more information, see section 4.3 Friend Presence, in the CTR Programming Manual: Wireless Communication.)


CONFIDENTIAL