11.2.1 Clearly Indicating What is Included in a Content Set
You must clearly state what add on content items are included in a content set if your application supports sales of content sets containing multiple add-on content items.
You are welcome to discount the price you set for content included in a content set compared to the price you set for content items sold individually. However, Nintendo recommends that you inform the user of any potential disadvantage associated with purchasing the content set (such as when the set includes content items that the user has already purchased separately).
11.2.1.1 Supporting Sales of Content Sets
Guideline Item |
If the application supports the sale of multiple add-on content items as a content set, what items are included in the set must be clearly stated. |
---|---|
Software to Be Tested |
Applications that provide multiple pieces of add-on content as a content set. |
Test Method |
Check how the content set is displayed. |
Pass/Fail Determination |
Passes if the add-on content items included in the content set are clearly indicated. |
11.2.2 Data Title Icons and Titles
Be sure to configure an icon and a title for the data title as a whole, not just for each content item. Check whether icons have been configured properly from the Data Management screen of System Settings.
If you have multiple data titles that correspond to a single title (that is, if you have multiple variations on that title), you must configure these settings for all your data titles.
The Data Management screen of System Settings displays the icon and title of the data title with the smallest variation number out of all of the data titles downloaded to the local system.
11.2.2.1 Data Title Icon and Title Settings
Guideline Item |
An icon and a title must be configured for the data title itself. |
---|---|
Software to Be Tested |
Applications that use add-on content |
Test Method |
Note: In situations where it is not possible to check each data title individually (such as when initializing multiple data titles at once), perform the test by checking the icons and titles under the CFA 1 tab of Master Editor. |
Pass/Fail Determination |
Passes if in step 2, the data title's icon and title are displayed. |
11.2.3 Items Included in Add-On Content
■ Prohibition of Changing Add-On Content Item Names After Items Have Been Released
If you change the item name of an add-on content item on IMAS, the item name displayed on the user's purchase details in Nintendo eShop is also changed. To avoid cases where the item name displayed at time of purchase does not match the item name displayed later in the purchase details, it is prohibited in principle to change the item name of any add-on content after releasing it.
■ Compatibility with the Application
If your application has revisions (either patches or remastered versions), or if there have been changes to its add-on content, all versions of add-on content must work without problems in all versions of the application, in all possible combinations. In general, partial deletion and/or alteration of purchased content is prohibited. However, if a bug is discovered in add-on content, it is acceptable to replace it with corrected content.
■ Prohibition on Ratings Deviations
Add-on content must not exceed the application's age rating. For example, it is prohibited to provide add-on content that contains violent imagery for an application rated for all ages.
11.2.3.1 Prohibition of Changing Add-On Content Item Names After Items Have Been Released
Guideline Item |
It is prohibited to change the item names of add-on content after releasing the add-on content. |
---|---|
Software to Be Tested |
Applications with already-released add-on content. |
Test Method |
Check the catalog on IMAS. |
Pass/Fail Determination |
Passes if there are no changes to the item names. |
11.2.3.2 Compatibility with Applications
Guideline Item |
All versions of add-on content must work without any problems with all versions of the application. |
---|---|
Software to Be Tested |
Applications and/or add-on content that have revisions (either patches or remastered versions). |
Test Method |
Play through every mode of the application where add-on content is used, using all combinations of all add-on content versions with all application versions. |
Pass/Fail Determination |
Passes if the application can be played without problems. |
11.2.3.3 Prohibition on Deleting or Altering Subsets of Sold Content
Guideline Item |
Once content has been sold, it must not be deleted or altered in subsequent revisions. |
---|---|
Software to Be Tested |
Add-on content with revised versions. |
Exceptions |
If the content was revised to fix an issue with the content. |
Test Method |
Check the source code. |
Pass/Fail Determination |
Passes if content which has been made available for sale is not deleted or altered. |
11.2.3.4 Prohibition on Rating Deviations due to Add-On Content
Guideline Item |
Add-on content must not deviate from the rating of the application. |
---|---|
Software to Be Tested |
Applications that use add-on content |
Test Method |
Check the source code. |
Pass/Fail Determination |
Passes if the add-on content does not deviate from the rating of the application. |
11.2.4 Sale of Executable Data
In principle, the sale of executable data, such as DLLs, is prohibited.
11.2.4.1 Prohibition Against Sale of Executable Data
Guideline Item |
The application must not support the sale of executable data. |
---|---|
Software to Be Tested |
Applications that use add-on content |
Test Method |
Check the add-on content. |
Pass/Fail Determination |
Passes if executable data is not included in add-on content. |
11.2.5 Precautions Regarding Save Data
■ When Linking Save Data to Add-On Content
It is not a problem to link save data to specific pieces of add-on content, but as a general rule the save data must be usable without problem (no lockups, no prevention of game progress, etc) if that add-on content is deleted.
For example, imagine that you save while your character has equipped the "Mario Suit" add-on content, and then you delete the "Mario Suit." If you then load your save data, the application will not be able to find the "Mario Suit." In this case, it is preferable if the application can continue without the "Mario Suit" equipped.
As long as your application provides a way for the user to redownload the add-on content and prompts them to do so by displaying instructions or a similar message, it is acceptable if deleting add-on content prevents the user from progressing any further in your application.
There are several ways to cause a situation where required content has been deleted. For example, deleting data titles from the Data Management screen of System Settings or swapping out the SD Card can cause this situation.
■ When Including Add-On Content in Save Data
If you save actual add-on content data inside save data or extended save data, be aware that the add-on content can then be used by systems which either never had the license to use it or have lost the license to use it. Nintendo recommends not saving such data in save data or extended save data.
11.2.5.1 When Linking Save Data to Add-On Content
Guideline Item |
The application must run without issues when add-on content that is linked with save data is deleted. |
---|---|
Software to Be Tested |
Applications that use CTR-ECDK and that link add-on content to save data. |
Exceptions |
Cases where all of the following conditions are met:
|
Test Method |
|
Pass/Fail Determination |
Passes if in step 4, the application is playable without any problems. |
11.2.6 Precautions When Distributing Add-On Content
When distributing purchased add-on content to another Nintendo 3DS or other device via the network, such as when displaying add-on content to a communication partner during online play, you must encrypt the channel by which the content is sent and prevent it from being saved on the other system or device.
This requirement is intended to prevent the interception, hacking, and illegal copying of purchasable add-on content. Therefore, it does not apply to free add-on content (including item download codes that are distributed free of charge), or to data that is included in purchasable add-on content but would be meaningless if intercepted or illegally saved, such as the text string of the name of an additional stage.
By design, it is not possible to transfer the license of add-on content. For this reason, if a user gives data to another user and that data no longer remains on their system, then as long as they have a license for the data they can redownload it. In contrast, if the user who received the data has no license for it, they cannot redownload it. If your application distributes add-on content, be aware of this point and consider how best to handle it in a robust and user-friendly way. Nintendo recommends explaining this to users to avoid confusion, as well as avoiding mechanisms that allow unlimited proliferation of copies.
11.2.6.1 Encrypting Add-On Content When Distributing, and Preventing Saving
Guideline Item |
The application must encrypt purchased add-on content when distributing it to devices other than the Nintendo 3DS on which it was purchased (such as other Nintendo 3DS systems), and must prevent it from being saved on such other devices. |
---|---|
Software to Be Tested |
Applications that are able to use add-on content through communication with other devices. |
Exceptions |
|
Test Method |
|
Pass/Fail Determination |
Passes if all of the following conditions are met.
|
11.2.7 Redownloading Add-On Content
Implement your add-on content so that once the content license has been purchased or redeemed via a download code, the user has an option to download the content again at any time, even if the content has been deleted from the SD Card. For example, implement a management menu within the application that lists content for which the user has purchased a license, and allow the user to redownload content from this list (via the application calling the nn::ec::EcApplet::RequestDownloadContents function).
If you add a redownload feature to a menu listing purchasable items (that is, the menu includes items for which the user has not yet purchased a license), make sure the display clearly distinguishes between items available for purchase and items available for redownload. Avoid implementations that could confuse the user, such as listing prices for all items including those for redownload.
11.2.7.1 Support for Redownloading Add-On Content After It Is Deleted
Guideline Item |
Applications must implement add-on content so that once the add-on content license has been purchased or redeemed via a download code, the user has an option to download the content again at any time, even if the content has been deleted from the SD Card. |
---|---|
Software to Be Tested |
Applications that use add-on content |
Test Method |
|
Pass/Fail Determination |
Passes if all of the following conditions are met.
|
11.2.7.2 Distinguishing Purchasable Items from Purchased Items
Guideline Item |
If the list screen has both purchasable items and purchased items at the same time, it must distinguish between the two. |
---|---|
Software to Be Tested |
Applications that display redownloadable items together with purchasable items on the list screen. |
Test Method |
|
Pass/Fail Determination |
Passes if in step 3, there is a clear distinction between purchasable items and purchased items. |
11.2.8 Handling Discontinuation of Sales
Implement your add-on content so that users can still redownload the content even after the sales period has ended. It is acceptable to display just those items available for purchase on a list of purchasable items, or to display all items with some indication shown for items that are no longer available for purchase. Implement this even if there are no current plans to end sales in preparation for future legal issues or similar problems that would end sales. Call the nn::ec::ContentSetCatalogFilter::SetSelectionFilter function and pass SELECTION_FILTER_ALL as an argument to get information about items for which the sales period has ended.
11.2.8.1 Support for Redownloading Add-On Content After Sale Is Ended
Guideline Item |
The implementation must enable users to redownload any add-on content they have purchased before at will, even if sale of that content has been discontinued. |
---|---|
Software to Be Tested |
Applications that use add-on content |
Test Method |
|
Pass/Fail Determination |
Passes if all of the following conditions are met.
|
11.2.9 Size Restrictions
■ Size Restrictions
The upper limits for data title sizes are given in Table 11-2 Add-On Content Limits. When creating your data titles, take care not to exceed these limits. Contact Nintendo at support@noa.com if you must exceed the 512 MB limit for a single add-on content item. Depending on the details of your design, Nintendo may grant an exception to this limit. The number of add-on content items that can be saved at one time to an SD Card is limited on the system side to 2,000 items per data title. Note that required content is counted as one item.
Upper Limit | ||
---|---|---|
Capacity | Per add-on content item | Up to 512 MB |
Number of add-on content items that can be sold at one time | Per data title | 2,000 items maximum |
Size of metadata content | Per data title | Up to 5 MB |
Size of 1 data title | Per data title | Up to 2 GB |
■ Restrictions on Number of Data Titles
In general, use one data title for one game title. This does not apply to sequels of previously sold data titles.
11.2.9.1 Compliance with Size Restrictions of Add-On Content
Guideline Item |
The size of a data title must not exceed the upper limits given in Table 11-2 Add-On Content Limits. |
---|---|
Software to Be Tested |
Applications that use add-on content |
Test Method |
Check the add-on content. Note: In CTR Master Editor, for each item of add-on content it is possible to check whether the metadata content and the overall data title comply with the size restrictions. If the size exceeds the restriction, the result is output as an error in the error information. For details, see the CTR MasterEditor manual. |
Pass/Fail Determination |
Passes if all of the following conditions are met.
|
11.2.10 Implementing a Deletion Feature
Nintendo recommends implementing a feature in your application to select specific add-on content and delete it.
This is to provide the user with a feature to delete specific add-on content when the SD card is full so that the user can purchase new add-on content. Otherwise, the user must go to the Data Management screen of System Settings and delete an entire data title.
No required guideline items.
11.2.11 Restrictions on Number of Mounted Files
There are limits on the number of add-on content items and metadata items you can mount simultaneously, because doing so consumes the system's globally shared resources.
The nn::fs::MountAddOnContent function can mount a maximum of two add-on content items at a time.
The nn::ec::CTR::MetaDataReader::Initialize function can mount only one metadata item at a time.
No required guideline items.