The table diff browser — 26.2.0 → 27.0.0

We've decoded Version 27.0.0 table by table (the walkthrough, the codex, raid scoring, Invasion) — but every number in those posts is a claim we made from the data. This page is the data itself: every table that changed between the 26.2.0 and 27.0.0 extractions, with sampled row-level diffs you can check against anything we've written. Trust, but verify — preferably against us.

55tables in the diff

+5620rows added

−8rows removed

~2418rows edited in place

13new A/B override tables

How matching works

Table filenames carry a numeric suffix (CostumeData_63.json) that is not a version number — it moves between builds when the table's contents do. So the two extraction dumps are matched by stem (CostumeData), including the separate _AB_ A/B-test variants, and each side's rows are diffed by their id (or map_key/key where the table uses one). Rows are then classified: added (id new in 27.0.0), removed (id gone), or edited (same id, one or more fields changed). Unchanged tables: 107 matched pairs, identical at row level — where a pair exists on both sides. A _AB_ override table with no counterpart in 26.2.0 has no pair to match, so the 13 that 27.0.0 introduces are counted as fully added rows (see the A/B layer below).

This page reports what changed, not why. Where we've interpreted a change — the INVASION_BAL keys, the codex ladder, the raid scoring split — that reading lives in the linked decoded post, built from the same diffs you can check here.

The browser

Each row is a table from the dumps: click it to open its sampled diff. Sampling caps at 20 ids and 15 edited rows per table to keep the page under ~50 KB — counts are always complete; the samples are the first 20/15 by insertion order.

Table	26.2.0	27.0.0	diff

The A/B layer this page used to drop

13 of 27.0.0's new tables are _AB_ overrides — a parallel row set keyed by ref_id back into a base table, carrying only the columns it replaces and an ab_test_group of 1. They have no 26.2.0 counterpart, so the matcher skipped them and their base tables went on being reported as unchanged: IngameRVData read 3,200 → 3,200 here while 1,672 of its rows were being overridden.

They now appear in the browser above as new tables, every row counted as an addition:

Override table	rows
`CodexData_AB`	1880
`IngameRVData_AB`	1672
`GiftChestData_AB`	400
`ChallengeTowerStageData_AB`	250
`EnemySpawnGroupData_AB`	96
`EnemyData_AB`	93
`LevelUpRewardData_AB`	80
`SevenDayEventMissionData_AB`	34
`MinimapRewardData_AB`	20
`ChestSlotUnlockCostData_AB`	12
`ChestSpawnerData_AB`	12
`ChestData_AB`	9
`ShopProductRewardData_AB`	3

An override row is not a value. The number a player sees is the base row with the override merged in, and the page above shows only the raw fields. We did the merge for the reward tables — the ad, codex, level-up and tower payouts — in The gem cut.

Tables on only one side

Stems without a partner are just as real as the diffs above — brand-new systems in 27.0.0, plumbing the client dropped by 26.2.0:

Only in 27.0.0

ABTestGroupData
CostumeCodexData
CostumeCodexGroupData
CostumeCodexStarGradeData
CostumeStepupPackageData
HalloweenPassRewardData
LiveopsFieldMonster
PlayGamesRewardData
RuneUniqueOptionSubSkillData

Only in 26.2.0

BalancingData_Currency
BuildingLumberMillData
BuildingStoneHouseData
StatDefaultData

Diffs computed from the shipped TextAssets of both builds (game v27.0.0 today): rows compared by their per-row key; non-data files (bundle_info.json, the nv-* obfuscation templates) are excluded. XP Hero is developed by Supercent — XPHero Fans is unofficial and not affiliated with or endorsed by them. Values shown are raw table fields, not gameplay-corrected numbers, and remote-config balance can change between builds and regions.