BI · Balance Telemetry

Mode is not a cosmetic filter. MISSION shares site values with TIME ATTACK while being a different thing — a compressed depth ladder (its S.30 is the 4th site of a 5-minute run, reached around Lv7, not the 30th site of a long run around Lv22), up to 3× the crowd, one extra centre challenge per site, a 3-weapon roster, no shop, and a deadline. expected_dps/expected_lv on a mission row describe a designed curve the mode deliberately keeps the player below, so leaving Mode on "All" biases the per-site difficulty read rather than merely widening it. Group mission data by mission_tier. Rows before schema_ver 10 have no mission_tier and a mission row among them is indistinguishable from a Normal one — read those as unknown, never back-fill them.

HP-Lock (god mode) rows report the damage that landed — real site pressure, and the only source with many samples per site — so they are included by default. They can never die, so read outcomes / death rate / death causes with "Exclude god mode". Rows sent before schema_ver 8 zeroed their damage and are dropped from these panels entirely. Sandbox = MAP TEST and other non-runs.

Danger zone

Deleting is permanent — there is no undo and no server-side backup. Needs the Worker's ADMIN_KEY secret.