Section 105 defines Split/Second-style environmental Power-Play events for combat-eligible tracks. The ruleset is isolated from standard circuit, sprint, and time-trial play so ranked eligibility can be tuned separately.
Meter#
The Power-Play meter builds through drafting, drifting, proximity, clean-driving, and takedown actions. Level-1 spends trigger small events, Level-2 spends trigger medium destruction, and Level-3 spends trigger dramatic track-altering events.
Event Library#
Level-1 Power-Play events are oil drum explosion, falling barrel, runaway traffic, and sign collapse. They are minor environmental hazards with short reaction windows.
Level-2 Power-Play events are bridge cable snap, crane drop, building facade collapse, and fuel tanker explosion. They are medium destruction events with cinematic camera cuts, impact reactions, and counter windows.
Level-3 Power-Play events are entire bridge collapse, building topple, runway taxi-jet collision, stadium roof fall, and sinkhole opens. Every Level-3 event reroutes the track for the rest of the race.
Each combat-eligible track has a curated list of 4-8 Power-Play events per
level. The launch library binds these events to Track.Combat.IndustrialLoop
and stores the authored effect ids in power-play-track-events.json.
Trigger UI#
When the meter is ready, the Power-Play trigger UI shows a target indicator for the next viable event. The trigger button activates the event, plays the per-event cinematic camera cut, and displays the impact reaction.
Counter Rules#
Counter-Power-Play is enabled. Level-1 counters answer Level-1 events and Level-2 counters answer Level-2 events. Each authored event exposes a reaction-window dodge or evade input that can lessen damage.
Eligibility And Authoring#
Power-Play uses race mode id Race.PowerPlay, has its own ruleset toggle, and
uses a separate ranked eligibility ladder. Track Editor authoring is required
for every per-track Power-Play event and references the Section 99.5 race track
authoring workflow.
Verification#
PowerPlayTrackEvents_V2_Contract.json, power-play-track-events.json, the
RaceModes.Module automation spec, and check-v2-power-play-track-events.py
validate Section 105.