SYSTEM DEEP-DIVE

PVP — the versus layer

Compare the stats that matter in player-vs-player combat, the extracted constants and a reconstructed damage model. Worked examples and the calculator use the rules text’s 85% base hit assumption; recent Star Scramble testing disputes that value in live play.

The PvP landscape

Wing Fighter never lets two players actually fly against each other with live piloting. Every versus mode resolves through simulated battles between saved formations — your roster's sheet fights their roster's sheet. What differs per mode is the wrapper: the matchmaking, the attrition rules, and what a win pays.

Leader Duel (Cybertron) is a sixth "versus" event but contains no combat at all — two camps donate Energon and the bigger pile wins. It lives on the events overview.

One engine, many wrappers

Star Scramble's and Planet Wars' rule texts describe the same combat core, line by line. These are the engine's fixed rules, verbatim from the game's own rules screens:

The battle-report strings confirm what the simulator actually rolls per attack — damage, a 10-hit batch, a crit, or a dodge:

"Your {0} attacked {1}, dealing {2} points of damage"
"Your {0} attacked {1}, dealing {2} points of damage (10 times)"
"Your {0} attacked {1}, dealing {2} points of crit damage"
"Your {0} attacked {1}, but {1} dodged the attack"

What survives the PvP filter — 63 stats of 142

The attribute registry (attrs_base) carries an explicit isPvP flag on every one of its 142 buff channels. Only are honored in PvP; the other are silently zeroed. This is the config-level mechanism behind every skill description that ends in "(not effective in PvP)" — pierce, ricochet, explosion and slow effects on drones all ride dead channels.

What's dead tells you how the simulator works: everything geometric is gone. No bullet counts, spreads, speeds or sizes, no piercing or ricochet, no movement speed — the sim doesn't fly bullets across a screen, it rolls dice against stat sheets. And everything that cheats death is gone: extra revives, revival shields, "prevent die" procs, god mode.

Alive and sometimes PvP-only: the whole damage-mod stack (attack, crit, defense break, damage inc/red, final damage), accuracy & dodge, attack rate (firingInt), life-steal, damage reflect, immunity procs — and healing, which several Sentinel and Mech-Spirit skills state only works in PvP. The full live list is printed in the appendix at the bottom.

The duel math — every stat has a counter-stat

PvP stats come in attacker/defender pairs that subtract head-to-head. The pairing isn't a guess: the game's own attribute panel groups one side as "Combat Attributes Boost" (advantage) and the other as "Combat Resistance Boost" (resistance) — two meta-stats (rolled on Chips) that feed five offensive and five defensive channels at once.

CP counts crit as (crit − 0.1 + advantage) and crit damage as (critDmg − 2), supporting the 10% crit chance and 200% crit damage baselines. The rules text lists 85% starting hit chance, but its current Star Scramble applicability is disputed. The tooltips for both dodge and crit say "Maximum effect against player is 80%."

85%
rules-text hit baseline · disputed
10%
base crit chance
200%
base crit damage
80%
cap on dodge and crit vs players
Players are "aerial enemies." The five enemy families (Combat System) put enemy players in the Air branch — the tooltips for atk_air and dmgInc_air / dmgRed_air all read "aerial enemies (including players)". Anti-air stats are secretly PvP stats; anti-boss and anti-ground stats do nothing in a duel.

The damage formula

The gameplay code ships as encrypted hot-update blobs, so the exact evaluation order isn't recoverable — but the config exposes every term: each attacker stat, its defender counter, the baselines, the caps, and four global constants. Assembled in the standard order such stat systems use (each pair its own factor), one attack resolves like this:

// per-attack rolls (dodge is checked first, then crit — per the battle-log strings) P(hit) = 0.85 + hit_rate − evade_rate // dodge effect capped at 80% P(crit) = 0.10 + crit − critRst // capped at 80% vs players // damage of a landed hit damage = ATK(weapon) × ( 1 + dmgInc_total − dmgRed_total ) // "vs all enemies" pair × ( 1 + dmgInc_air − dmgRed_air ) // players are aerial × ( 1 + pvpDmgInc − pvpDmgRed ) // the PvP-only pair × ( critDmg − critDmgRed ) // only if the crit roll passed × ( 1 + (physicAtk − physicDef) × 0.001 ) // defense break, physical bullet × ( 1 + finalDmgInc − finalDmgRed ) // final pair, floor −50% × 0.75 // pvp_ratio_all — the global PvP haircut × ( 1 + damup(t) ) // sudden-death ramp (long fights)

Line by line, here is what's config-certain and what's reconstruction:

The four global constants

What the ×0.75 means in play: the in-game buff string says it outright — "Reduce damage dealt by both sides by {0} in combat". Both duelists deal 25% less than their sheet suggests. It exists to stretch fights toward the 40-second window: with symmetric power, a straight stat read would end fights too fast for dodge/crit variance to matter.
The sudden-death ramp: time_pvp_damup raises both sides' damage +100% at 50 s and +300% at 60 s. Star Scramble fights hard-stop at 40 s, so the ramp exists for the modes with longer or open-ended timers (Military Drills' live duels) — it guarantees somebody dies.

Worked examples

Both examples use this page’s reconstructed model, including the disputed 85% rules-text hit baseline. The account stats are illustrative mid/late-game values — to run your own, use the calculator below.

Example 1 — the roll chain

Attacker: hit_rate +12% · crit 15% stacked · critDmg +30% stacked  vs  Defender: evade 18% · critRst 6% · critDmgRed 15%

Example 2 — one Maingun bullet, factor by factor

Attacker: ATK 120,000 · dmgInc_total 15% · dmgInc_air 20% · pvpDmgInc 32% (maxed Mothership 20% + Camp Tech 9% + fetter 3%) · physicAtk 60 · finalDmgInc 10%
Defender: dmgRed_total 10% · dmgRed_air 8% · pvpDmgRed 9% · physicDef 40 · finalDmgRed 5%


PvP duel calculator

Compare both builds at equal attack cadence. Enter attack and HP, then open advanced stats as needed.

Hit-rate assumption: this model still starts at 85%. On November 2, 2026, Landplage0815 reported no missed normal attacks in Star Scramble with zero effective dodge; Toxaholic acknowledged the stale tooltip. This review did not reproduce the tests or establish a replacement formula. See the dated community correction before using the estimate for a matchup.

Valid inputs auto-save in this browser. Use Copy shareable link to share a matchup.

Estimated result · equal attack cadence

Reconstructed model; support shares are estimates. Reflect and life-steal are excluded.

You

Opponent

verdict

you → opponent

factor breakdown

opponent → you

factor breakdown
How this estimate works

A PvP fight isn't one damage number — it's a race. Both sides fire simultaneously, each rolls its own hit/crit chain against the other's defense sheet and HP, and the winner is whoever kills first (with the higher-power side landing the opening volley). So the calculator takes both full sheets — offense, defense including Max HP, and the support layer: drone element enhancement (elec/burn/ref Up vs Down), Sentinel enhancement (guardUp vs guardDown) and PvP healing (cureUp vs cureDown), modeled as damage streams and sustain. Percentages as on your stat panel (crit and crit damage on top of the 10% / 200% baselines), defense break and defense in raw points.

Your inputs auto-save in this browser and are carried in the address bar as you type — copy the link to share a matchup or bookmark a build; opening a shared link loads its numbers (older 18- and 36-field links still load). Two live PvP channels — damage reflect and life-steal — are documented above but not modeled here: their per-hit math isn't recoverable from the config.


Mode overlays — what each wrapper adds to the math

Star Scramble — the Fuel siege

Defenders in Star Scramble aren't just fought, they're worn down. Every defender holds 100 Fuel; each incoming attack burns an amount set by the attacker's power as a fraction of the defender's, and every point of Fuel lost cuts the defender's primary attributes by 1% — a pre-battle multiplier on the whole stat sheet:

Legion Clash — the stamina decay formula

Legion Clash (internally melee) locks your attributes when a battle starts, then applies the only stat formula the game ever prints on screen, quoted verbatim:

Current Attribute = Base Attribute × (1 + Opening Bonus) × (1 − Stamina Decay) Stamina Decay: −1% attack & HP for every 5 stamina lost

Military Drills — the daily ladder's economy

Military Drills (internally exercise / arena) runs the engine as an asynchronous 1v1 ladder against other players' defence teams. The wrapper is pure economy:


Where PvP stats come from

The dedicated PvP pair (pvpDmgInc / pvpDmgRed) has exactly four permanent faucets in the config — and every one of them is fed by PvP-adjacent content, a deliberate loop:

Beyond the dedicated pair: Pilots carry PvP skills (the Star-Scramble-exclusive Pilots convert mode play into "damage against players" stacks — see the Coin shop), Chips roll the advantage/resistance meta-stats, Talents and drone refits carry the physical/energy defense-break pairs, and everything that raises Maingun/Winggun/Missile attack, crit or HP carries straight into the duel. Stack check: maxing Mothership Space Training (+20%), the Charnik camp tech (+9%) and the four-Sentinel "Finale Overture" fetter (+3%) yields a permanent +32% damage against players before Pilots.


Sources & caveats

Extracted values: the rules text’s disputed 85% base hit, the 10%/200% crit baselines (visible in the CP formulas as crit−0.1 and critDmg−2), the 80% caps (stat tooltips), pvp_ratio_all 0.75, pvp_param_p 0.001 / q 1000, final_dmg_param −0.5, the time_pvp_damup ramp, the Fuel table, the Legion Clash formula (printed in-game), the isPvP flag census, and stat-source magnitudes. Presence in a snapshot or tooltip does not independently verify current live behavior.

Reconstructed: the multiplication order of the damage pipeline and the linear read of defense break ((physicAtk − physicDef) × pvp_param_p). The client's combat code ships as encrypted HybridCLR hot-update blobs, so the true expression isn't in the APK; pvp_param_q = 1000 could alternatively be a softcap denominator (def/(def+1000)-style). Either read agrees at small values, where all real accounts sit.

Seen but unplaced: pvp_power_down_param 1.2 / 1.5 / 0 (a power-gap damper by its name), common_pvp_rate 0.025 vs common_pve_rate 1.875 (exactly 75× apart — likely the per-hit conversion scalars for the two contexts; 0.025 = 1/40, the kill window), and military_rank_crit [1,2,3,5]. They're listed so future dumps can pin them down.

Appendix — all 63 PvP-active stat channels

← Combat System Star Scramble →