1.1 How to Use This Documentation
Volumes

This documentation is split into multiple volumes. Each volume explains the guidelines applying to a certain feature or set of features. The individual volumes are described below. Applications that fall under "Applications to Be Tested" must comply with the guidelines given in that volume.

Table 1-1 Volumes in This Documentation
Volume Applications to Be Tested Description
2 General All applications. This volume describes the guidelines and recommendations common to all applications.
3 File System All applications. This volume describes the guidelines and recommendations to follow when using the file system.
4 Safety All applications. This volume describes the guidelines and recommendations for promoting a fun and safe user experience with systems in the Nintendo 3DS family.
5 StreetPass and Local Communication
  • Applications which use local communication
  • Applications which use StreetPass

This volume describes the guidelines and recommendations to follow when using Local Communication or StreetPass.

Local communication includes the types of communication below: For information regarding infrared communication between systems, see volume 2 General.

  • UDS Communication
  • RDT Communication
  • PiaLocal
  • Download Play
6 Internet Communication Applications which use Internet communication.

This volume describes the guidelines and recommendations to follow when using Internet communication. You must follow these guidelines when using the following communication features, or when using the socket or http libraries to connect to independent licensee servers.

  • Nintendo Network accounts
  • AC
  • Friend Presence
  • NEX
  • SpotPass
  • Miiverse
7 UGC
  • Applications that use various communication features to exchange UGC (including infrared communication between systems).

This volume describes the guidelines and recommendations to follow when using various communication features to exchange user-generated content (UGC).

UGC refers to user-generated content, such as text, images, characters, photographs, videos, or audio. Text, audio, video, animation, or other content exchanged by users via chat or similar means is also considered UGC.

8 Mii Characters Applications that use Mii characters.

This volume describes the guidelines and recommendations to follow when using Mii characters. If your application exchanges Mii nicknames as text data, you must also read volume 7 UGC.

9 Patches Applications that apply patches. This volume describes the guidelines and recommendations to follow when applying patches.
10 Remastered Versions Remastered versions of applications. This volume describes the guidelines and recommendations to follow when creating remastered versions.
11 E-Commerce Applications that use e-commerce. This volume describes the guidelines and recommendations to follow when using e-commerce.
12 Demos Applications that support demos. This volume describes the guidelines and recommendations to follow when creating demos.
13 Internet Browser Applications which use the Internet browser built into systems in the Nintendo 3DS family. This volume describes the guidelines and recommendations to follow when using the built-in Internet browser of a system in the Nintendo 3DS family.
14 NFP Applications that use NFP. This volume describes the guidelines and recommendations to follow when using NFP.
Backgrounder Items and Guideline Items

Each volume is divided into chapters. Each chapter covers a specific topic.

The 3rd-level headings (X.X.X) in each chapter are the backgrounder items, which provide details about the guideline items Within the backgrounders, the rules the application must follow (and any exceptions to those rules) are displayed in bold text. Some items might not have any bold text. Such items are included simply as recommendations from Nintendo or as additional information.

If a backgrounder item contains bold text, it is followed by a guideline item under a 4th-level heading (X.X.X.X) that describes in detail the guideline the application must follow. A single backgrounder item might be followed by multiple guideline items. All guideline items are presented in a table similar to the following. The column on the right describes the content given in each row of the table.

Table 1-2 Description of a Guideline Item
Guideline Item
The guideline that an application must follow.
Software to Be Tested
The software for which this guideline item applies.
Exceptions
Any exceptions exempting software for which this guideline item would otherwise apply.
Not all guideline items have exceptions.
Test Method
The recommended test method.
Pass/Fail Determination
The criteria for passing the Test Method.

 

Before you submit your application to Lotcheck, check that your application complies with all of the required guideline items. You must always contact Nintendo beforehand if you have some reason to request an exemption from compliance with guideline items.

Note:

If a guideline's test method states "Check the source code," then there is no established test method. You must make sure that your application complies with the guideline during the implementation stage. You do not need to submit your source code when you submit your master ROM.

Developing Virtual Console Applications

If you are developing a Virtual Console application (an application originally developed for a past game platform, but playable on the Nintendo 3DS system), there are technical and other reasons that make it difficult to adjust the contents of the original ROM. Virtual Console applications are therefore handled as exceptions to a number of guidelines.

 

1.1.1 Referring to Different Systems

There are various lineups of systems in the Nintendo 3DS family, but in this document they are separated into the following categories.

Figure 1-3 Classification of Systems in the Nintendo 3DS Family in this Document
Overall Subcategory Development Name Product Name
Nintendo 3DS CTR CTR Nintendo 3DS
SPR Nintendo 3DS XL
FTR Nintendo 2DS
SNAKE SNAKE, KTR New Nintendo 3DS
CLOSER, RED New Nintendo 3DS XL

 

Because the majority of requirements and recommendations in this document describe or result in the same behavior on all systems in the above table, as a basic rule this document uses the term for the largest overall category, and thereby refers to all the systems. Therefore, unless the chapter differentiates between systems, any section that refers to "Nintendo 3DS" refers to all systems in the Nintendo 3DS family, not just CTR systems. Pertaining to this, note that any text that mentions SD Cards refers also to microSD cards in the case of the New Nintendo 3DS and New Nintendo 3DS XL systems.

There are some exceptions, listed below.

  • There is no Circle Pad Pro accessory for the Nintendo 2DS, New Nintendo 3DS, or New Nintendo 3DS XL systems.
  • Stereoscopic display is not supported on the Nintendo 2DS.

In addition to this, note that any chapters that differentiate between CTR and SNAKE are using these terms to refer to the subcategories in the table above. There are also places where development names are used in order to show the different hardware attributes of the different systems.

Note:

Because some aspects of SNAKE hardware are not compatible with CTR hardware and subsequently the system processing is different, you must test all Nintendo 3DS titles on both CTR and SNAKE.

For points to keep in mind when testing, see chapter 17 Appendix: Testing the Operations of CTR Titles on SNAKE in the Nintendo 3DS Programming Manual: System.

Lotcheck uses either a SNAKE system or a CTR system to test each single guideline.

No required guideline items.

 


CONFIDENTIAL