Every framedata change must list the patch, public test build signal, A/B result, affected move, before/after values, and design rationale.
| Patch | PTB Signal | A/B Result | Move | Before | After | Rationale |
|---|---|---|---|---|---|---|
patch-2026.05.s1 |
ptb.s1.cross-up-kick.block-winrate |
balance.s1.cross-up-kick |
Cross-Up Kick startup | 12f | 14f | Win-rate-on-block and hot/cold heatmaps showed the move converting too often from safe pressure. |
patch-2026.05.s1 |
ptb.s1.heavy-launcher.pick-rate |
balance.s1.heavy-launcher |
Heavy Launcher recovery | 23f | 25f | Pick-rate and win-rate-on-hit exceeded the target band across Competitive and EsportsAspirant segments. |
Review Gate#
- Public before/after metrics are published under
V2/balance/public-results/. - Official forum and survey feedback are attached before patch signoff.
- Community-flagged regressions during PTB trigger patch hold until design, QA, and live-ops review the replay set.