18. Rules for Designing Peripherals 
 
When designing the various peripherals, refer to the rules outlined in this document. 
 
18.1  Vibrating Peripheral (product name: "puru-puru pack") 
 
 <> Recommendation: 
At the start of a game, when the controller checks available peripherals and detects the presence of a vibration peripheral, a message such as "Activating puru- puru pack" or a user-confirmation prompt such as "Activate puru-puru pack? YES/NO" should be displayed, allowing the user to decide whether the peripheral is to be turned on or not. 
 
 <> Recommendation: 
An ON/OFF setting should be available under options. 
 
 <> Recommendation: 
During pause, the vibrating peripheral should also stop. 
 
 
--------------------- 
20. Play History 
 
 <> Recommendation: 
Saving the play history in the unit memory should be made possible by each application. 
 
This will allow future collection of play history data via a network, for use during further game development. 
 
20.1  Saving Play History 
 
Play history information saved in the unit memory should be handled by applications according to the following rules. 
 
 <> Recommendation: 
Under options, the user should be able to enable or disable play history. 
 
 [] Requirement: 
Essential data identifying the user, such as name, address, telephone number, etc. may not be stored in the free area in the unit memory. 
 
 [] Requirement: 
Essential game data without which correct game play is not possible (such as option settings, game data backup, etc.) may not be stored in the free area in the unit memory. 
 
The reason for the above requirements is as follows. 
The free area in the unit memory can hold play history information for up to 100 titles. When this limit is exceeded, data will be overwritten starting with the oldest data. Therefore information in the free area may be overwritten. 
 
20.1  Sending Play History 
 
For play history sending, preparations at the server side are still necessary. Therefore play history sending is currently not enabled on all PJs. To provisionally send play history data, follow the rules below. 
 
 [] Requirement: 
When sending play history data, the user must be made aware that play history data are included in the send data. 
 
 <> Recommendation: 
The user should be able to check the contents of the play history before sending. 
 
This could be implemented for example by showing a confirmation screen with the choices "Send/View Data/Do not send". 
 
20.1.1  Continuously Sending Play History Data from an Application 
 
The assumption is that after starting a game, play history data are sent continuously and that game progress changes depending on these data. 
 
 [] Requirement: 
At game start, the user must be informed that play history data will be sent during the game, and the user must be given a choice to disable sending. 
Whether the game content (difficulty, story, etc.) changes when the user disables play history sending is left to the application. 
 
Example: "Use play history in unit memory? (Some data will be sent via modem during a session.) YES/NO" 
 
 [] Requirement: 
Under options, sending of play history data during the game must be selectable. 
 
20.1.2  Play History Sending by Explicit User Action 
 
The assumption is that in an application including a web browser, the user switches to the browser and uses its upload function to send data. 
 
Because a different browser may also be used, the user should be able to select play history data sending with the browser used for receiving web data. 
 
--------------------- 
 
25. License and Patent Information Display 
 
 [] Requirement: 
 
When using a library provided by a third party or patents or copyrights belonging to a third party, copyright information and the name and logo etc. of the owner must be displayed in a specified location, according to the licensing agreement. 
 
 [] Requirement: 
The name and logo etc. of the copyright owner must be displayed in a size that is clearly visible on a 14-inch monitor (video output). 
In principle, display duration must be at least 2 seconds, and the size of logo data may not be altered. If the size must be altered for example for inclusion on a credits screen, the minimum sizes shown below must be observed. 
 
        320 dots x 240 dots (for screen size 640 x 480 dots) 
        160 dots x 120 dots (for screen size 320 x 240 dots) 
 
