The following settings for related systems and networks must be configured prior to master ROM submission.
Configure all of the following settings that apply to your application, without exception.
Any functionality described in Managing Network Features > List of Network Features in the OMAS2 Manual is included.
OMAS submissions and approvals for each feature are needed for the application to use network features.
The OMAS request sets up and configures servers to enable development of the network features used by titles.
Applications that require an OMAS request as part of the applicability criteria cannot be submitted to Lotcheck until the OMAS request phase has progressed to During Development/Lotcheck Queue. Make sure that an OMAS request has been submitted before clicking the Submit button on NDP. Clicking the Submit button without progressing the OMAS request causes an error in NDP. (Reference: 9 FAQ/NDP Errors)
See 10 Common Problems and Bugs - OMAS Application.
Using BCAT Functionality
Lotcheck tests features that use BCAT.
The Lotcheck environment (sd1 or sp1) data is used at this point, so you must register the data before master ROM submission.
Independent server refers to a server that is not provided by Nintendo but that applications can connect to. It is configured and operated independently by the developer.
Supports services from an independent server, prepared by the developer.
Lotcheck tests features that use independent servers.
See 10 Common Problems and Bugs - Independent Server Settings.
When unavoidable maintenance of the independent server is scheduled while the title is in Lotcheck, contact Lotcheck by using the Messages tab. Lotcheck will work around the scheduled maintenance.
Supporting Subscription and Consumable Service Items
Lotcheck checks the sales information, after incorporating that data into a Lotcheck environment, for subscription and consumable service items configured for dd1 titles in NCMS.
Settings for NCMS are enabled after a product has been created on NDP.
CONFIDENTIAL