Fighting Game · Guides & deep dives

V2 Racing Regional Variant Policy

Every regional racing SKU must declare whether cop and pursuit content is unchanged, visually adjusted, relabeled, or disabled.

5sections1 minread

On this page

This document records the racing-specific regional variant gates for Section 119. It is an implementation checklist for content cooking and QA; regional legal counsel owns final publication approval.

Cop And Pursuit Content#

Every regional racing SKU must declare whether cop and pursuit content is unchanged, visually adjusted, relabeled, or disabled. The China publisher SKU uses adjusted cop visuals and publisher-approved terminology. Pursuit objectives must describe non-Death-Race outcomes as incapacitate, immobilize, evade, or busted.

Combat-Racing Weaponry#

Combat-racing weaponry is region-gated by SKU. Regions that restrict weapon presentation can substitute abstract effects, disable explicit weapon meshes, or fall back to non-lethal impact language. Death Race variants are reviewed separately from standard pursuit and combat-racing modes.

Speed And Plates#

Every regional SKU defines a speed-limit display unit and a number-plate format. Global and China publisher SKU defaults use km/h. United States SKU defaults use mph and state-style number plates. Runtime UI must read the variant table rather than hard-code the unit or plate format.

Safety Gates#

No V2 racing SKU may depict drunk or impaired driving. Region variants must not weaken the impaired-driving prohibition. Non-Death-Race pursuit content must not depict cop killing, and text/audio must use incapacitate or immobilize language.

Validation#

RacingComplianceCert_V2_Contract.json, racing-compliance-cert.json, and check-v2-racing-compliance-cert.py validate that the regional variant policy is registered in source, data, docs, and CI.