Nintendo Wii U Instruction Manual

Wii Programming Guidelines
Version: 1.01a
The contents in this document are highly
confidential and should be handled accordingly.
©2006 Nintendo RVL-06-0132-001-I
CONFIDENTIAL Released: October 11, 2006

Wii Programming Guidelines
Confidential
These coded instructions, statements, and computer programs contain proprietary information of Nintendo
of America Inc. and/or Nintendo Company Ltd. and are protected by Federal copyright law. They may not be
disclosed to third parties or copied or duplicated in any form, in whole or in part, without the prior written
consent of Nintendo.
RVL-06-0132-001-I 2©2006 Nintendo
Released: October 11, 2006 CONFIDENTIAL

Wii Programming Guidelines
Table of Contents
1Overview .....................................................................................................................................................11
1.1 Ranking System..................................................................................................................................11
1.2 Wii Programming Guidelines Note......................................................................................................11
2All ................................................................................................................................................................12
2.1 Prohibition of Dependency on Device Specifications [Information] ....................................................12
2.2 Memory and Register Initialization [Required]....................................................................................12
2.3 Startup Time Restriction [Recommended] ..........................................................................................12
2.4 Startup Disc Error Handling [Required]...............................................................................................12
2.5 Compliance with Legal Rights Display [Required]..............................................................................13
2.6 Library Version [Recommended] ........................................................................................................13
2.7 Deletion of Debug Information [Required] ..........................................................................................13
2.8 Device Access without the Use of a Library Prohibited [Required].....................................................13
2.9 Do Not Include Development Support Libraries in Release Version [Required] ................................13
2.10 Demo Screen Loop Processing [Required] ........................................................................................14
2.11 Integrating Banners, Comments, and Icons [Required]......................................................................14
2.12 Referencing and Changing Wii System Settings [Information]...........................................................14
2.13 Prohibition of Warning Screen Display by Application [Required] ......................................................14
2.14 [N. American Version Only] Onscreen Warning Display for Applications Using Online Features
[Required] .......................................................................................................................................................15
2.15 Program Distribution Method [Required] ............................................................................................15
2.16 Parental Controls [Information] ...........................................................................................................16
3Wii Game Disc and Drive............................................................................................................................17
3.1 Prohibition on Drive Specification Dependency [Required]................................................................17
3.2 Wii Game Disc Error Handling [Required] ..........................................................................................17
3.3 Infinite Loops During Multiple Data Streaming Prohibited [Required].................................................17
3.4 [Only for Multiple Disc Games] Independent Startup of All Discs [Required] .....................................18
3.5 Normal Operation after the Disc Drive Motor Is Shut Off From a Period of Inactivity [Required].......18
3.6 Display for Disc Drive Motor Shut Off From a Period of Inactivity [Recommended] ..........................18
3.7 Data Layout for Double Layer Disc [Recommended] .........................................................................18
©2006 Nintendo 3RVL-06-0132-001-I
CONFIDENTIAL Released: October 11, 2006

Wii Programming Guidelines
4Sound ......................................................................................................................................................... 19
4.1 Sound Setting [Information]................................................................................................................ 19
4.2 Applying Wii Console System Sound Settings [Required] ................................................................. 19
4.3 Sound Output for Applications Supporting Multiple Sound Settings [Required]................................. 19
4.4 Do Not Modify the Audio Playback Frequency Within an Application [Required]............................... 19
5Photosensitivity........................................................................................................................................... 20
5.1 About Photosensitivity and These Guidelines [Information]............................................................... 20
5.2 Restrictions on Flashing Images and Lights [Recommended] ........................................................... 21
5.3 Restrictions on Flashing Saturated Red Colors [Recommended]...................................................... 21
5.4 Restrictions on Image Reversals [Recommended] ............................................................................ 22
5.5 Restrictions on Regular Patterns [Recommended] ............................................................................ 22
5.6 Screen Brightness Calculations [Information] .................................................................................... 23
6Video........................................................................................................................................................... 26
6.1 Display within the Safe Frame [Recommended] ................................................................................ 26
6.2 Video Settings [Information] ............................................................................................................... 26
6.3 Support for Progressive Display [Recommended] ............................................................................. 26
6.4 Settings and Display for Progressive Display Supported Application [Required]............................... 26
6.5 Switching Between Interlaced and Progressive Display Output [Recommended]............................. 27
6.6 Addition of Interlaced/Progressive Switch Operation [Recommended] ............................................. 27
6.7 Reset Operation during Progressive Output [Recommended]........................................................... 27
6.8 Progressive Output Supported TV [Recommended].......................................................................... 27
6.9 PAL 50 Support [Required]................................................................................................................. 27
6.10 Settings and Display for EU RGB 60 Supported Application [Required]............................................ 28
6.11 Switching between PAL and EU RGB 60 [Recommended]................................................................ 28
6.12 Addition of PAL/EU RGB 60 Switch Operation [Recommended]....................................................... 28
6.13 Reset Operation during EU RGB 60 Output [Recommended]........................................................... 28
6.14 Maintaining Appropriate Video Output [Required] .............................................................................. 28
6.15 Display Method for 16:9 Screen Ratio [Recommended] .................................................................... 29
6.16 Settings and Display for Applications That Support 16:9 Screen Ratio Display [Required]............... 29
6.17 Trap Filter [Recommended]................................................................................................................ 29
6.18 Support for 4:3 Aspect Ratio [Required]............................................................................................. 29
6.19 Checking the On-screen Display during Application Startup [Required]............................................ 29
6.20 Check Before Switching to Progressive Display [Required]............................................................... 30
6.21 Applying the Raster Burn Mitigation Setting [Information].................................................................. 30
RVL-06-0132-001-I 4©2006 Nintendo
Released: October 11, 2006 CONFIDENTIAL

Wii Programming Guidelines
7Controllers...................................................................................................................................................31
7.1 All Controllers......................................................................................................................................31
7.1.1 Display When Extension Controller is Necessary [Required] .....................................................31
7.1.2 Avoid Game Design Forcing Extended Period of Continuous Operation or Strenuous Activity
[Information] ................................................................................................................................................31
7.1.3 Explanatory Message for Wii Remote Strap Use (Required)......................................................32
7.1.4 Handling +Control Pad Input [Required] .....................................................................................32
7.1.5 Operations on the Unused Buttons [Required] ...........................................................................32
7.1.6 Lower Limit Value of the Controller Stick and Button Analog Input Value [Recommended] .......33
7.1.7 Upper Limit Value of the Controller Stick and Button Analog Input Value [Required] .................33
7.1.8 Analog Input Value Range of Controller Stick and Button [Required].........................................33
7.1.9 Regarding Applications that Support the Rumble Feature [Required] ........................................34
7.1.10 Avoid Continuous Operation of the Rumble Motor [Recommended]..........................................34
7.1.11 Stop Rumble Motor When Controller Not in Use [Required].......................................................34
7.1.12 Rumble Motor Run/Stop Switch Frequency Requirement [Recommended]...............................34
7.1.13 Hot Swapping Extension Controllers [Recommended] ...............................................................34
7.1.14 Frequency Band Usage when Using a Wireless LAN [Information] ...........................................34
7.1.15 Do Not Use Origin Reset Command for Analog Input to Extension Controller [Required] .........35
7.2 Wii Remote .........................................................................................................................................35
7.2.1 Using the Relative Distance between the Wii Remote and the Sensor Bar [Recommended]....35
7.2.2 Handling HOME [Required].........................................................................................................35
7.2.3 Disabling Pointer for Applications Without Pointer Function [Required] .....................................35
7.2.4 Disabling Pointer for Applications With Pointer Function [Recommended] ................................35
7.2.5 Do Not Use of Wii Remote Memory and Wii Remote Speaker Simultaneously [Required]........35
7.2.6 Restriction on Contents of Data Written to Wii Remote Memory [Required] ..............................36
7.2.7 Checking for Errors in Wii Remote Data [Required]....................................................................36
7.2.8 Message Display When Writing to Wii Remote Memory [Required]...........................................36
7.2.9 Message Display When Loading Wii Remote Memory [Recommended) ...................................36
7.2.10 Error Handling When Writing to Wii Remote Memory [Required] ...............................................36
7.2.11 Error Handling When Reading From Wii Remote Memory [Required] .......................................36
7.2.12 Data Compatibility for the Same Application Using Wii Remote Memory [Required] .................37
7.2.13 Prohibition of Application Dependent on Wii Remote Memory Access Speed [Required]..........37
7.2.14 Handling Damage to Wii Remote Memory [Recommended] ......................................................37
7.2.15 Displaying a Message when Overwriting Wii Remote Memory [Required].................................37
7.2.16 Continuous Play on the Wii Remote Speaker [Required] ...........................................................37
7.2.17 Halting Data Transfers When No Output Occurs on the Wii Remote Speaker [Recommended]37
7.2.18 Audio Cutoff of Speaker due to Poor Signal Sensitivity [Recommended]...................................37
7.2.19 Displaying a Message Notifying the User That Battery Charge Is Low [Recommended] ........38
7.2.20 Displaying a Message Notifying Users That Wii Remote Transmissions Have Terminated
[Recommended]..........................................................................................................................................38
©2006 Nintendo 5RVL-06-0132-001-I
CONFIDENTIAL Released: October 11, 2006

Wii Programming Guidelines
7.3 Nintendo GameCubeTM Controller...................................................................................................... 38
7.3.1 Application Support for the Nintendo GameCube Controller [Information]................................. 38
7.3.2 Use of Origin Reset Command as Game Input Prohibited [Required] ....................................... 38
7.3.3 Support for Origin Reset Command [Required].......................................................................... 38
7.3.4 Hot Swapping Support for Nintendo GameCube Controller Socket Devices [Required] ........... 39
7.3.5 Frequency of Checks for Nintendo GameCube Controller Hot Swapping [Recommended]...... 39
7.3.6 Nintendo GameCube WaveBird Wireless Controller Support [Required]................................... 39
8Wii System Memory.................................................................................................................................... 40
8.1 Restrictions on Wii System Memory [Required]................................................................................. 40
8.2 Limits on Frequent Rewrites [Required] ............................................................................................. 40
8.3 Error Handling [Required]................................................................................................................... 41
8.4 Write Operation Display [Required].................................................................................................... 41
8.5 Data Compatibility Within the Same Program [Required] .................................................................. 42
8.6 Applications Dependent on Wii System Memory Access Speed Prohibited [Required] .................... 42
8.7 Reset Handling [Required] ................................................................................................................. 42
8.8 Data Unit for Users [Required] ........................................................................................................... 42
8.9 Checking the Number of Free i-nodes and Amount of Free Memory Using NANDCheck[Async]
[Required]....................................................................................................................................................... 42
8.10 Timing for Checking the Number of Free i-nodes and the Amount of Free Memory [Required]........ 43
8.11 Notification When the Number of i-nodes or the Amount of Free Memory Is Insufficient [Required].43
8.12 Do Not Change Created File Size [Required] .................................................................................... 44
8.13 Handling Corrupted Files [Recommended] ........................................................................................ 44
8.14 Handling Corrupted Wii System Memory [Recommended]................................................................ 44
8.15 Saving Data During the Shutdown Process [Recommended]............................................................ 44
9Nintendo GameCube Memory Card........................................................................................................... 45
9.1 Nintendo GameCube Memory Card Compatible Application [Information]........................................ 45
9.2 Use of Write Functions Prohibited [Required] .................................................................................... 45
9.3 Programs Must Not Depend on the Access Speed of Nintendo GameCube Memory Cards
[Required]....................................................................................................................................................... 45
9.4 Support for High Capacity Nintendo GameCube Memory Card [Required]....................................... 45
9.5 Errors Displayed when Memory Cards Cannot be Used [Required].................................................. 46
9.6 Compatible Slots [Recommended] ..................................................................................................... 46
9.7 Memory Card Menu in Application [Required].................................................................................... 46
9.8 Limit on Accessible Memory Card Files [Required]............................................................................ 46
RVL-06-0132-001-I 6©2006 Nintendo
Released: October 11, 2006 CONFIDENTIAL

Wii Programming Guidelines
10 Reset.........................................................................................................................................................47
10.1 Wii Console RESET [Required] ..........................................................................................................47
10.2 Wii Power Button [Required]...............................................................................................................47
10.3 Reset the Nintendo GameCube Controller Origin during Reset Operations [Required] ....................48
10.4 Use of Hot Resets [Recommended] ...................................................................................................48
10.5 Required Preparations Before Using the Reset/Shutdown Functions [Required] ..............................48
10.6 Do Not Use the Nintendo GameCube Controller Reset Command [Required]..................................48
Tables
Table 2-1 Rating Agencies by Market.......................................................................................................16
Table 8-1 Directory Size Limits.................................................................................................................40
©2006 Nintendo 7RVL-06-0132-001-I
CONFIDENTIAL Released: October 11, 2006

Wii Programming Guidelines
Revision History
Version Revision Date Description
1.01 10/6/2006
•Deleted “Boot Caching.”
•Added “Prohibition on Drive Specification Dependency.”
•Updated “Sound Setting,” and “Sound Output for Applications
Supporting Multiple Sound Settings.”
•Added “Video Settings.”
•Updated “Settings and Display for EU RGB 60 Supported
Application” and “Reset Operation during Progressive Output.”
•Updated “Test of Different TV Reception Formats” as “Maintaining
Appropriate Video Output.”
•Added “Checking the On-screen Display during Application
Startup” and “Check Before Switching to Progressive Display.”
•Updated “Applying the Raster Burn Mitigation Setting.”
•Updated “Explanatory Message for Strap Use.”
•Updated “Using Wireless LAN” as “Frequency Band Usage when
Using a Wireless LAN.”
•Updated “Support for Changes in the Wii Remote and Sensor Bar
Distance” to “Using the Relative Distance between the Wii
Remote and the Sensor Bar.”
•Added “Restrictions on Contents of Data Written to Wii Remote
Memory.”
•Updated “Continuous Play on the Wii Remote Speaker.”
•Updated “Handling Audio Data Transmissions Stopped by the
Feature for Avoiding Audio Cutoff” as “Audio Cutoff of Speaker
due to Poor Signal Sensitivity.”
•Updated “Write Operation Display,” “Data Unit for Users,”
“Checking the Amount of Free Memory and Number of Free i-
Nodes Using NANDCheck[Async],” “Notification When the
Amount of Free Memory or Number of i-Nodes is Insufficient,” and
“Handling Corrupted Wii System Memory.”
•Added “Prohibition on Programs Depending on the Access Speed
of Nintendo GameCube Memory Cards.”
•Updated “Wii Console RESET Button,” and “Wii Power Button.”
•Changed the title heading “Reacquisition of Origin for GameCube
Controller during Reset Operation” to “Reset the
Nintendo GameCube Controller Origin during Reset Operations.”
1.00 9/21/2006
•Updated “Prohibition of Dependency on Device Specifications.”
•Updated “Handling +Control Pad Input.”
•Updated “Support for Changes in the Wii Remote and Sensor Bar
Distance.”
•Changed “Limitations on Use of HOME” to “Handling the HOME.”
•Added “Prohibition of Simultaneous Use of Wii Remote Memory
and the Wii Remote Speaker.”
•Added “Data Compatibility for the Same Application using Wii
Remote Memory,” “Prohibition of Application Dependent on Wii
Remote Memory Access Speed,” “Handling Damage to Wii
Remote Memory,” and “Displaying a Message when Overwriting
Wii Remote Memory.”
•Updated “Handling Audio Data Transmissions Stopped by the
Feature for Avoiding Audio Distortion.”
•Changed “Specifying a Message Notifying the User that Battery
RVL-06-0132-001-I 8©2006 Nintendo
Released: October 11, 2006 CONFIDENTIAL

Wii Programming Guidelines
Charge is Low” to “Displaying a Message Notifying the User that
Battery Charge is Low.”
•Changed “Specifying a Message Notifying Users that Wii Remote
Transmissions Have Terminated” to “Displaying a Message
Notifying Users that Wii Remote Transmissions Have Terminated.”
•Updated “Notification When the Amount of Free Memory or
Number of i-Nodes is Insufficient,” “Handling Corrupted Files,” and
“Handling Corrupted Wii System Memory.”
•Changed “Support for Non-Japanese Spec GameCube Memory
Cards” to “Errors Displayed when Memory Cards Cannot be
Used.”
0.98 9/15/2006
•Standardized terminology to use “Wii system memory.”
•Added Section 2.18, “Parental Control.”
•Added that the feature for stopping the disk drive motor does not
work under Revolution SDK 2.2 Patch.
•Deleted “Error Display when Disc Eject Button is Pressed.”
•Updated text. Added figures, graphs, and tables. Added
information on calculating screen brightness.
•Added “Applying the Raster Burn Mitigation Setting.”
•Updated “Explanatory Message for Wii Remote Strap Use.”
•Updated “Lower Limit Value of the Controller Stick and Button
Analog Input Value,” “Upper Limit Value of the Controller Stick and
Button Analog Input Value,” and “Analog Input Value Range of
Controller Stick and Button.”
•Deleted “Vibration Enabled/Disabled Mode Switch Function.”
•Updated “Do Not Use the Origin Reset Command for the Analog
Input to an Extension Controller.”
•Updated “Limit Use of HOME” and “Disabling Pointer for
Application Without Pointer Function.”
•Deleted “A Caution about Data Loss for Wii Remote Memory.”
•Changed the rank of “Message Display when Writing to Wii
Remote Memory.”
•Standardized terminology to use the word “speaker.”
•Combined “Handling Audio Cutoff of Speakers Due to Plugging In
the External Extension Controller” and “Handling Audio Cutoff of
Speakers Due to Packet Loss” to form “Handling Audio Data
Transmissions Stopped by the Feature for Avoiding Audio Cutoff.”
•Added “Specifying a Message Notifying the User that Battery
Charge is Low” and “Specifying a Message Notifying Users That
Wii Remote Transmissions Have Terminated.”
•Updated “Checking the Number of Free i-nodes and Amount of
Free Memory Using NANDCheck[Async]” and “Notification When
the Number of i-nodes or the Amount of Free Memory Is
Insufficient.”
•Changed the rank of “Handling Corrupted Files.”
•Updated “Handling Corrupted Wii System Memory.”
•Updated “Memory Card Menu in Application.”
•Updated “Note for Using CARDFastOpen Function” and changed
the title to “Limit on Accessible Memory Card Files.”
•Updated “Wii Console RESET” and “Wii Power Button.”
0.97 09/07/2006
•Updated "Boot Caching".
•Added description of Wii console setting values when using a 16:9
aspect ratio.
©2006 Nintendo 9RVL-06-0132-001-I
CONFIDENTIAL Released: October 11, 2006

Wii Programming Guidelines
•Added a note that the screen for describing how to wear the strap
is currently being studied.
•Added the section “Prohibition on the Use of the Origin Reset
Command for the Analog Input of the Extension Controller”.
•Updated notes regarding message displayed when reading or
writing to Wii Remote memory.
•Standardized terminology to use the term “Wii system memory”
(old term: Wii console internal flash memory)
•Deleted “Free Space Check” (the old 8.4)
•Updated sections 8.1, 8.2, 8.3, 8.4, 8.5, and 8.8.
•Added new sections from 8.9 to 8.15.
•Updated the names of documents being referenced.
•Added sections 10.2 and 10.6.
•Changed the title of section 10.5.
0.96 08/24/2006
•Deleted the (tentative) appellation for Boot Caching.
•Added section on Support for 4:3 Aspect Ratio.
•Added indication that the pointer halt functionality is not currently
available in the KPAD library.
•Added sections on Wii Remote memory (7.2.5 to 7.2.9) and on
the speaker (7.2.10 and 7.2.11).
0.95 08/09/2006
•Added section on “Boot Caching (tentative).”
•Reorganized the entire section.
•Changed the title “Warning Message of Moving Controllers” to
“Explanatory Message for Strap Use,” and upgraded the ranking
to “Required.”
•Added section on “Data Unit for Users.”
0.94 07/21/2006
•Initial version.
RVL-06-0132-001-I 10 ©2006 Nintendo
Released: October 11, 2006 CONFIDENTIAL

Wii Programming Guidelines
1 Overview
The Wii Programming Guidelines provide programming cautions for the Wii console and peripherals.
1.1 Ranking System
The following rankings indicate the level of importance of the programming guidelines.
•[Required] Items that must be implemented
•[Recommended] Items that should be implemented
In addition, related items may be marked as [Information].
1.2 Wii Programming Guidelines Note
The Wii Programming Guidelines are established to reduce problems in the market. However,
following these guidelines does not guarantee that all problems will be avoided.
Also, some of the documents referenced in the Wii Programming Guidelines are currently being
created or updated, so they may not include the referenced information at this time. Please be patient
as the contents will be added as they become available.
©2006 Nintendo 11 RVL-06-0132-001-I
CONFIDENTIAL Released: October 11, 2006

Wii Programming Guidelines
2 All
2.1 Prohibition of Dependency on Device Specifications [Information]
Avoid designing a program with a dependency on the device specifications of the Wii console or its
peripherals, since this may result in a program malfunction or crash.
There will be some specification variance between devices. Performance will also decrease as the
device ages or a disc becomes damaged.
Specifically, the devices here refer to the disc drive, disc, Wii Remote, Wii system memory,
SD Memory Card, and Nintendo GameCube Memory Card. See the corresponding chapters for
details.
2.2 Memory and Register Initialization [Required]
The contents of memory are not guaranteed during application program startup. Do not assume a
specific initial memory value if memory has not yet been initialized by the application. Similarly, do not
use an uninitialized register assuming a specific initial value when using assembler.
The arena is cleared to zero using OSInit.
2.3 Startup Time Restriction [Recommended]
Display screen images within 2 seconds of switching to the application.
If the startup time is excessively long, the user may mistake this for a system malfunction.
This does not include the 100 or so frames necessary for switching display mode to either
progressive display or EU RGB 60 display.
Refer to the contents to be added to “Wii File Restriction” in “Revolution Optical Disc Drive Library
(DVD)” for details.
2.4 Startup Disc Error Handling [Required]
Always include the disc error handling routine (including error display) in a program read by IPL.
If there is no error handling routine (error display) in the section read by the IPL, errors that occur
before the reading of the error handling routine will not be processed.
Refer to “Revolution Optical Disc Drive Library (DVD)” for details on error handling.
RVL-06-0132-001-I 12 ©2006 Nintendo
Released: October 11, 2006 CONFIDENTIAL

Wii Programming Guidelines
2.5 Compliance with Legal Rights Display [Required]
A separate indication of legal rights is required for some of the library tools provided by Nintendo. Use
the specified display method when using a library tool or other item requiring a legal rights display.
Not displaying the legal rights information in the specified method may result in licensing issues.
Note that the legal rights display can be shown in various ways, such as during game startup, in the
user's manual, and on the packaging. For details, refer to the instructions for the individual library
tools. We also plan to distribute a document compiling various library tool rights displays.
2.6 Library Version [Recommended]
Use the newest library version available since libraries may be modified to fix problems.
2.7 Deletion of Debug Information [Required]
When compiling and assembling the release version, set options so that debug information will not be
included in the program.
If debug information is included, it will not only decrease the execution speed, it will also increase the
program size. Leaving in the debug code outputs may also result in lock-ups.
Link to the release versions of libraries instead of debug versions. When using make, the OS debug
code is disabled by setting NDEBUG=TRUE.
2.8 Device Access without the Use of a Library Prohibited [Required]
Do not access the individual devices directly without going through the appropriate library.
The individual device libraries in the OS are created to avoid device compatibility issues and
hardware bugs. Also, the newly created I/O devices are designed with library access in mind.
Accessing the individual devices without going through the appropriate library first may result in
various unexpected problems.
2.9 Do Not Include Development Support Libraries in Release Version
[Required]
Do not include development support libraries in the release version master data. Specifically, the hio2
library falls into this category.
Including development support libraries may cause a Wii system malfunction.
©2006 Nintendo 13 RVL-06-0132-001-I
CONFIDENTIAL Released: October 11, 2006

Wii Programming Guidelines
2.10 Demo Screen Loop Processing [Required]
Make sure no problems occur when the demo screen (or the title screen, if there is no demo) is
executed in a loop for more than 24 hours. Demo screens may loop overnight in store fronts.
Be especially careful of counter overflow. Also, refer to information about normal operation when the
disc drive motor is shut off after a period of inactivity.
2.11 Integrating Banners, Comments, and Icons [Required]
Prepare a banner and comment for your Wii Game Disc.
For applications to be run on the Wii system memory, make an icon available in addition to a banner
and a comment.
The comments should not exceed the system menu display area.
This is for the display in the system menu. See individual chapters for details.
2.12 Referencing and Changing Wii System Settings [Information]
Apply the various settings configured on the Wii console to the application program as applicable.
Also, if these settings can be changed from the application side, apply these changes on the Wii
console.
This is to allow easier sharing of user-configured values between applications.
Refer to the guidelines for individual Wii console configuration items for details.
2.13 Prohibition of Warning Screen Display by Application [Required]
The Wii system will display the health and safety warning screen when the user presses the Wii
console Power Button. Nintendo believes that all warnings content are covered by this warning
screen. Therefore, do not display any other warning message on the application side.
RVL-06-0132-001-I 14 ©2006 Nintendo
Released: October 11, 2006 CONFIDENTIAL

Wii Programming Guidelines
2.14 [N. American Version Only] Onscreen Warning Display for
Applications Using Online Features [Required]
Applications using online features are required to display the following message specified by the
ESRB, the local ratings establishment body:
"Game Experience May Change During Online Play"
The ESRB regulation only requires that the message be displayed before the use of an online feature
and that the ability to circumvent is not permissible. However, with user appeal in mind, we
recommend that this message be displayed in the startup menu screen. The font size must be 20
points or larger and the text must be noticeable and easy to read. For example, the message may be
displayed along with other display messages, but it must not be in the same color as the background
or require scrolling to be visible.
If it is clear that this message does not need to be displayed or ESRB confirms that this message
display is not necessary, this will be considered inapplicable once the developer makes the request
not to display the message.
This message is to be displayed regardless of the user’s age.
2.15 Program Distribution Method [Required]
Do not run programs other than the following:
•Programs included on Wii Game Discs produced by Nintendo
•Programs distributed by the program distribution system provided by Nintendo
Do not read in programs or perform an external transfer of programs from the application using an SD
Card, a Nintendo GameCube Memory Card, a network, USB, Bluetooth, or other kind of interface.
Also, even if data is simply being read using these interfaces, always perform buffer overflow checks
or data encryption so that programs will not be executed as a result of buffer overflow.
©2006 Nintendo 15 RVL-06-0132-001-I
CONFIDENTIAL Released: October 11, 2006

Wii Programming Guidelines
2.16 Parental Controls [Information]
The Wii system can restrict the startup of Wii games based on a Parental Control feature. This feature
can be used when a parent or guardian does not want the system to allow access to games that are
inappropriate for members of their household. The parent or guardian can set the restriction level
based on a game’s rating. The parent or guardian will set a PIN for temporarily releasing the Parental
Controls.
Games for the Wii system must be rated by the rating agency for each market in which the game is
released before submitting a master. When creating master data for submission, be sure to enter the
rating using the Master Editor program.
Table 2-1 lists the rating agencies for each market.
Table 2-1 Rating Agencies by Market
Market Rating Agency
Japan CERO
North America ESRB
Europe PEGI, USK, BBFC (varies by country)
Australia OFLC
The Wii console will restrict the startup of games according to the restriction level set by the parent or
guardian based on the rating stored in the game. Restricted games can be started only if the correct
PIN is entered when the user is prompted for it immediately before startup. Note that applications do
not need to perform any special processing for the restrictions based on their rating.
For details, see “Master Editor,” scheduled for release, and the “Parental Controls Programming
Manual.”
RVL-06-0132-001-I 16 ©2006 Nintendo
Released: October 11, 2006 CONFIDENTIAL

Wii Programming Guidelines
3 Wii Game Disc and Drive
3.1 Prohibition on Drive Specification Dependency [Required]
Ensure that programs do not run uncontrollably or freeze due to dependency on drive access speed.
Drive access speed differs depending on the status of the disc and/or drive. Furthermore,
specifications regarding drive access speed, cache size, and cache operations may change in the
future.
Be sure to thoroughly debug programs so that they do not freeze even when drive access speed
suddenly drops, particularly in cases where data is used sequentially as in movie scenes.
3.2 Wii Game Disc Error Handling [Required]
For Wii Game Disc error handling, adhere to the contents to be added to the “Revolution Optical Disc
Drive Library (DVD),” including the messages, unless there is a special reason not to do so.
Having each application handle Wii Game Disc errors differently will confuse users.
If there is a special reason to change error handling, contact [email protected] early in development.
3.3 Infinite Loops During Multiple Data Streaming Prohibited
[Required]
Avoid infinite looping of simultaneous multiple instances of data streaming.
Data streaming is defined as the method of reading data sequentially as it is used, as opposed to a
burst transfer where necessary data is loaded all at once from the disc before it is used. One good
example of data streaming is movie playback.
Similarly, if frequent non-sequential access is necessary over a long period of time, try to make the
access sequential or, in any case, prevent an infinite loop.
Also, seek noise created during simultaneous playback can be reduced significantly by placing files
that are played simultaneously as close to each other as possible.
When the drive enters an infinite loop while constantly moving the drive head at high frequency, this
may adversely affect the drive if the user leaves the game in this state.
If the application violates this requirement, the following steps may be taken to prevent such an
occurrence.
•Interleave the data file and the audio file into a single file and play back the audio portion.
•Interleave multiple files for data streaming into a single file so that they can be accessed
sequentially.
Another method to prevent infinite loops is to stop data streaming after several loops.
©2006 Nintendo 17 RVL-06-0132-001-I
CONFIDENTIAL Released: October 11, 2006

Wii Programming Guidelines
3.4 [Only for Multiple Disc Games] Independent Startup of All Discs
[Required]
Even if startup of the application from a particular Wii Game Disc is not expected, always make sure
that some kind of program is executed when the disc is started independently, even if it is just a
warning message. For example, if the inserted Wii Game Disc is one of a set of two Wii Game Discs
and the inserted disc is one that cannot be played standalone, have available a program that displays
a message such as “This is <game title> Game Disc 2. Please insert <game title> Game Disc 1 and
restart power.”
Not doing so may cause the user to think that there is malfunction in either the Wii console or the Wii
Game Disc when a Wii Game Disc is not designed for independent startup.
3.5 Normal Operation after the Disc Drive Motor Is Shut Off From a
Period of Inactivity [Required]
Make sure applications using Wii Game Discs do not crash or malfunction when the drive motor shuts
off.
When there is no controller input for a set period of time (TBD), the drive motor is shut off to extend
drive life. This requirement allows the user to resume the game after a long period of inactivity.
Note: In the Revolution SDK 2.2 Patch 2, there is no need to support automatic shutoff of the disc
drive motor due to controller inactivity for a fixed period of time. This is because the feature for
stopping the disc drive motor does not work. Be sure to support automatic shutoff in future
updates of the Revolution SDK when that feature becomes available.
3.6 Display for Disc Drive Motor Shut Off From a Period of Inactivity
[Recommended]
When the drive motor shuts off, applications using discs should display a specified message
(currently being studied) until normal operations are restored.
Note: In the Revolution SDK 2.2 Patch 2, there is no need to support automatic shutoff of the disc
drive motor due to controller inactivity for a fixed period of time. This is because the feature for
stopping the disc drive motor does not work. Be sure to support automatic shutoff in future
updates of the Revolution SDK when that feature becomes available.
3.7 Data Layout for Double Layer Disc [Recommended]
Avoid data layouts that require reading to alternate between the first and second layer. To minimize
reading from different layers, extra steps, such as placing the same data on both layers, may be
necessary.
Switching between the first and second layer adds extra latency.
RVL-06-0132-001-I 18 ©2006 Nintendo
Released: October 11, 2006 CONFIDENTIAL

Wii Programming Guidelines
4 Sound
4.1 Sound Setting [Information]
In the Wii sound setting menu, three selection types are available: mono, stereo, and surround.
Use the function SCGetSoundMode to acquire the system sound setting.
4.2 Applying Wii Console System Sound Settings [Required]
If the application supports the sound setting specified on the Wii console, it must use this sound mode.
If the application does not support surround or mono sound output, it should treat these settings as
stereo.
4.3 Sound Output for Applications Supporting Multiple Sound Settings
[Required]
If the application does not have a menu where the sound settings can be specified, obtain the Wii
system sound settings at application startup and apply these to the application sound settings.
Also, if the application does have a sound setting menu, use the system sound setting as the initial
value.
4.4 Do Not Modify the Audio Playback Frequency Within an Application
[Required]
Although the Wii audio system supports playback at a frequency of either 32 kHz or 48 kHz, once one
of these frequencies has been set for an application at startup, be sure not to change the frequency
setting again. The ability to change the playback frequency is limited due to hardware specifications.
©2006 Nintendo 19 RVL-06-0132-001-I
CONFIDENTIAL Released: October 11, 2006

Wii Programming Guidelines
5 Photosensitivity
5.1 About Photosensitivity and These Guidelines [Information]
These guidelines are intended to be used in the development of video games for the Wii platform.
Unlike films and television programs, which produce only one sequence of images each time they are
played, one video game can produce an infinite sequence of images. This is because video games
are interactive, so that each time a game is played, a different sequence of pictures and images will
be displayed, depending on the choices and inputs made by the game’s player or—in the case of
multi-player games—players. In addition, the luminance of images displayed in three-dimensional
games are not simply those of the video game artist’s original image but are the result of the game’s
programming processes, which render the image in a three-dimensional form in a three-dimensional
space, with variations of light, shadow, distance, orientation and player perspective. These variables
also are affected by choices made by the individual player.
Because of these infinite variations that are possible within a single game, it may be possible with
many games that certain player inputs will cause screen imagery that will exceed the suggested limits
described below. Developers should try to design games that comply with the limits when the games
are played with normal gaming strategies and inputs, with the recognition that it may still be possible
for player inputs to cause sequences of images that may exceed the suggested limits, particularly if
the gameplay is idiosyncratic or counterintuitive. It must also be remembered that compliance with
these guidelines or with any other guidelines that have been or will be developed may reduce the
incidence of photosensitive seizures, but they will not eliminate them or eliminate seizures that occur
during video gameplay from causes other than the visual content of the games.
These guidelines attempt to take what medical science has learned about the images that can trigger
photosensitive seizures in the universe of susceptible individuals and, in a few paragraphs, apply it to
the infinite variety of imagery produced by modern video game technology. Medical research in this
area is still developing, and the particular susceptibilities of photosensitive persons vary widely from
individual to individual. As the developers of other guidelines have recognized, it is impossible to craft
guidelines that will eliminate all risk of seizures, and the measures taken should be proportionate to
the risks involved and should not stifle developers’ creativity, imagination or freedom of expression. It
may be possible that a game, even though complying with the guidelines, may produce a problematic
sequence. Alternatively, a sequence out of compliance with the guidelines may not be problematic in
its context. It is therefore recommended that all games, before final release, be reviewed by one or
more persons knowledgeable about photosensitivity who can check for potentially problematic
sequences. It is also recommended that such persons review decisions to deviate from the guidelines
when that may be desirable for the artistic or creative imperatives of a game.
These guidelines use the following lighting technology terms:
•Luminance is a quantifiable measurement of the observed brightness of an object—in this case, of
a video screen.
RVL-06-0132-001-I 20 ©2006 Nintendo
Released: October 11, 2006 CONFIDENTIAL