This chapter summarizes the items you must support when linking SpotPass and NEX data stores. If your application links SpotPass and NEX data stores, you must comply with chapters 6.14 BOSS: Common Items and 6.12 NEX: Data Stores as well as this chapter. Regarding data size, you must comply with section 6.12.1 Limits on Data Handled by Data Stores.
If your application links to NEX data stores and also performs immediate execution with the same NADL task, you must also comply with 6.16.3 Displaying Errors during Immediate Execution.
Linking data stores and SpotPass enables the exchange of data between friends via data stores. If you link SpotPass with data stores, then as a general rule you must comply with all the guidelines for SpotPass and for data stores. However, there are some restrictions which change when linking the two. The content of those changes is explained here.
6.17.1 Specifying the Serial ID Used for Linking With SpotPass
If your application sends a notification when it gets data via linking with SpotPass, the library sends notifications locally. In this case, the nn::boss::DataStoreDownloadAction::SetNewsPublication function is used to specify the notification's ID. However, you must set the notification's ID to match the SpotPass Link Serial ID registered on OMAS.
6.17.1.1 Confirming the Serial ID Used for Linking With SpotPass
Guideline Item |
If the application sends a notification when it gets data via linking with Data Store, the notification's ID must be identical to the SpotPass Link Serial ID. |
---|---|
Software to Be Tested |
Applications which send notifications when getting data, and which link with data stores. |
Test Method |
|
Pass/Fail Determination |
Passes if the same SpotPass Link Serial ID registered on OMAS is set as the notification ID.
|
6.17.2 Settings for DataStore Download and Upload Tasks
When linking with data stores, comply with the following settings for DataStore download and upload tasks.
Item |
Value to set |
---|---|
Execution Interval and Execution Count (Download) |
Set the execution interval to a value ranging from 1 to 168 hours (one hour to one week); set the execution count to a value ranging from 1 to 720 times. (A task with an execution interval of 168 hours and an execution count of 720 times will be active for roughly 14 years.) |
Execution Interval and Execution Count (Upload) |
Set the execution interval to a value ranging from 1 to 168 hours (one hour to one week); set the execution count to a value ranging from 1 to 24 times. |
Execution priority |
Use the default value of PRIORITY_MEDIUM. Contact Nintendo at support@noa.com before setting any other value. |
Access point information |
Do not provide this information. |
Task permissions |
Set a value of TASK_PERMISSION_IN_NONE. Since the default value is TASK_PERMISSION_IN_PARENTAL_CONTROL, set this explicitly using the SetProperty function of the nn::boss::TaskPolicy class. |
Task ID |
Use the task ID that you used on your application to Nintendo. |
6.17.2.1 Confirming Settings for DataStore Download and Upload Tasks
Guideline Item |
The settings for DataStore download and upload tasks must follow the standards established by Nintendo. |
---|---|
Software to Be Tested |
Applications that register DataStore download or upload tasks. |
Test Method |
After registering a DataStore download or upload task, use BossLotcheckTool to check the value of each setting. |
Pass/Fail Determination |
Passes if all of the following conditions are met.
|