This chapter summarizes restrictions related to handling patches. Refer to this information when you consider making a patch.
9.1.1 Limitation on Size
A patch can be a maximum of 128 MB.
If the application specifications make it impossible to meet this restriction, contact Nintendo at support@noa.com.
9.1.1.1 Patch Size
Guideline Item |
The maximum size of the patch is 128 MB. |
---|---|
Software to Be Tested |
Patches |
Test Method |
Check the patch size in Master Editor. |
Pass/Fail Determination |
Passes if the Title Information in Master Editor lists the file size as 128 MB or less. |
9.1.2 Prohibition Against Exceeding Previous Software Rating
The rating of a patched application must not be higher than the rating of the original unpatched application. It is prohibited to raise the rating of an application by applying a patch.
If you set a rating in a patch that is different from the rating of the original unpatched application, the system still refers to the original application rating upon application startup. The system does not refer to the rating that you set in the patch. Therefore, if the user has enabled Parental Controls to restrict access to applications based on their ratings, and you raise your application's rating with a patch, Parental Controls refers to the original rating and does not prevent your application from starting. If you need to raise your application's rating, or if you need to add a rating that was not included in the original application (for example when adding support for a ratings board in a new market), use a remaster instead of a patch.
9.1.2.1 Ratings after Patches are Applied
Guideline Item |
The rating of a patch must not exceed the rating of the unpatched application. |
---|---|
Software to Be Tested |
Patches |
Test Method |
|
Pass/Fail Determination |
Passes if the rating of the patch does not exceed the rating of the unpatched application. |
9.1.3 Prohibition of Either Adding or Removing Rollback Prevention
It is prohibited to use a patch to either add rollback prevention as a new feature, or to remove rollback prevention features that were implemented in the unpatched application.
Using patches to either add or remove save data rollback prevention could cause problems in maintaining compatibility between patched and unpatched applications. So, at this point in time, it is prohibited to either add or remove this feature in a patch.
9.1.3.1 Comparing Rollback Prevention in Patched and Unpatched Versions
Guideline Item |
Rollback prevention must be neither added to nor removed from a patched version of an application in comparison with unpatched versions. |
---|---|
Software to Be Tested |
Patches |
Test Method |
|
Pass/Fail Determination |
Passes if the status of rollback prevention, as indicated by "NINTENDO:SaveDataSecureValueEX," does not change between step 1 and step 2. |
9.1.4 StreetPass, Local Communication, and Infrared Communication
As a basic rule, patched versions and earlier versions of an application must successfully communicate with each other. On the other hand, if the design of your application prevents you from ensuring compatibility, you must display a message informing the user that patched versions and earlier versions cannot communicate. This message must be displayed within the application at some point before communication would take place. Make sure that the message is not displayed exclusively in sequences where the user does not necessarily see the message before communication takes place, such as the application's configuration screen. That said, it is not required to display this message at startup or otherwise ensure that it displays absolutely every time the user plays the application.
We offer the following example messages to display to users for your reference.
You cannot communicate with other players using a different version of this application. You can check what version you have from the {location where the version is displayed}.
|
You cannot communicate with other players using version x.x.x or earlier of this application. You can check what version you have from the {location where the version is displayed}.
|
9.1.4.1 Supporting StreetPass, Local Communication, and Infrared Communication
Guideline Item |
Applications that do not maintain communication compatibility between patched and unpatched versions must display a message to that effect to the user before communication is performed. |
---|---|
Software to Be Tested |
Patched versions of applications that support StreetPass, local communication, or infrared communication. |
Test Method |
|
Pass/Fail Determination |
Passes if at least one of the following conditions is met.
|
9.1.5 Add-On Content Compatibility
When you release a patch for an application that supports add-on content, all versions of add-on content must work without problems with all versions of the application in all combinations, as described in section 11.2.3 Items Included in Add-On Content.
See section 11.2.3 Items Included in Add-On Content for the guideline items for this section.
No required guideline items.