3.3 Extra Data

This chapter describes restrictions on extra data (extended save data). The specifications for card-based applications and downloadable applications are unified as much as possible for Nintendo 3DS systems. As a result, unless noted otherwise, the required restrictions for extra data are the same for both card-based applications and downloadable applications.

When you use extra data, you must comply with both the guidelines in this chapter and the guidelines in chapter 3.4 Save Data and Extra Data: Common Items.

By specification, data downloaded to a Nintendo 3DS system using BOSS is also saved in extra data.
Therefore, the guidelines in this chapter as well as some of the guidelines in Save Data and Extra Data: Common Items and chapter 3.5 File System Error Handling may apply when you are using BOSS.
The specific sections that apply are listed in the BOSS guidelines. Refer to the chapters prefixed with "BOSS" in volume 6 Internet Communication.

 

Note:

Most of the guidelines related to extra data are recommendations. This is because Nintendo has decided that extra data is basically a bonus element, and even if it is created accidentally or becomes corrupted, this will not result in a fatal error. However, depending on the specifications of your application and on user playstyles, there could be cases where extra data is valued as much as save data. As a result, it is up to you as the developer to be familiar with both the required items and the recommendations below, and to decide as appropriate for your application whether the recommendations are truly optional or whether you should treat them as required.

Note:

See the Nintendo 3DS Family Overview and the Nintendo 3DS Programming Manual for details on the characteristics and main uses of extra data. (Extra data may also be called "extended save data" in those references.)

3.3.1 Data Saved as Extra Data

There are no particular restrictions on what data can be saved as extra data. However, for card-based software we recommend that you use the save data region on a Game Card—instead of extra data on an SD Card—to store data that is required for application progress. By recognizing that a Game Card contains not only ROM data but also their application progress, players will probably develop a stronger connection to their Game Cards.

You do not need to pay particular attention to this issue for downloadable applications because both their save data and extra data is stored on the same SD Card.

If your application saves data required for application progress or other similarly important data as extra data, Nintendo recommends informing the user what kinds of data are being saved as extra data. This is to prevent the user from accidentally deleting important data.

No required guideline items.

3.3.2 Readable and Writable Extra Data

Do not access extra data created by an application that is released by a different publisher. Contact Nintendo at support@noa.com if your application needs to access the extra data of an application not released by the same publisher. Your application may freely create or delete data files within the data archives of any title released by the same publisher.

3.3.2.1 Compliance with Restrictions on Readable and Writable Extra Data

Guideline Item
The application must only be able to read and write extra data for titles released by the same publisher.
Software to Be Tested
Applications that access extra data.
Test Method
Go to the CXI tab of Master Editor and check the content of either the Expanded save data number or AccessibleSaveDataIds fields.
Pass/Fail Determination
Passes if the extended save data number of an application created by the same publisher is displayed.

3.3.3 User Confirmation When Creating New Extra Data

Extra data that is created without user confirmation is more likely to be accidentally erased when the user attempts to organize their extra data from the Data Management screen. Consequently, Nintendo recommends that you get user confirmation or otherwise notify the user when your application creates a new extra data archive. You can notify the user at any time before the extra data is created or immediately afterwards.

There is no particular need for user confirmation when creating new extra data files within an existing extra data archive.

No required guideline items.

3.3.4 Extra Data Size

No limit is set on the amount of extra data one application can manage. However, from the user's viewpoint, it is not considerate to reserve an overly large amount of space that is then not used. Nintendo recommends a limit of 32 MB per application as an amount of extra data which applications can manage without users needing to monitor the amount of free space on the SD Card. Furthermore, based on historical use of extra data, Nintendo considers a size of approximately 200 MB to be sufficient for the amount of extra data required for a single application. If your application will need to use more than 200 MB of space for extra data, contact Nintendo at support@noa.com with information about what data you will be saving and how much space you will need.

It is not necessary to contact Nintendo if your extra data will never exceed 200 MB in size or if user operations could cause the amount of extra data to exceed 200 MB. Contact Nintendo only if you know that, at minimum, you will need more than 200 MB of space in order to use extra data.

No required guideline items.

3.3.5 Displaying Titles on the Extra Data Management Screen

When creating extra data using the nn::fs::CreateExtSaveData function, for the iconData argument you must specify an ICN file created with the ctr_makebanner tool. The one- and two-line title names specified in the BSF configuration file used to create this ICN file are also used for display on the HOME Menu’s Extra Data Management screen. You can enter title names in the BSF file for each of the languages supported by the Nintendo 3DS system, such that the title displayed on the Extra Data Management screen will match the currently selected system language.

Specify appropriate title names for each language in the BSF file to prevent garbled title display on the Extra Data Management screen. Also make sure that one-line titles fit properly within one line of display, and that two-line titles likewise fit within two lines of display. Note that entering strings longer than the display width will cause abrupt and unfortunate line wrapping.

It is not absolutely necessary for the title of the extra data to be identical to the title of the application. In general it is desirable for the two to be identical, but, for example, if a series of several applications share extra data it is acceptable to use the name of the series. However, you must ensure that the title of the extra data allows users to identify which application, series, or software company is associated with it. For example, vague names like "Data1" or "Collection Data" are not allowed, as users would be unable to figure out what application the extra data is associated with.

3.3.5.1 Supporting the Display of Titles for Extra Data

Guideline Item
The title name must display normally in Extra Data Management, regardless of the language selected in System Settings.
Software to Be Tested
Applications that create extra data.
Test Method
  1. Create extra data.
  2. From System Settings, select Data ManagementNintendo 3DSExtra Data.
  3. On the Saved Software Titles screen, check the title name of the application being tested.
  4. On the Saved Software Titles screen, select the extra data of the application being tested and check the title name that is displayed.
  5. Applications for regions which allow language selection in System Settings:
    1. Select Other SettingsLanguage, and conduct steps 1 through 4 for all languages.
Pass/Fail Determination

Passes if all of the following conditions are met.

  • The application’s title name is displayed properly without corrupted characters in steps 3 and 4.
  • In steps 3 and 4, the title of the extra data allows users to identify which application, series, or software company is associated with it.
  • In step 3, the title name is displayed on a single line.
  • In step 4, the title name is displayed within two lines.

 


CONFIDENTIAL