Phantom Blade Zero Data Methodology

How this Phantom Blade Zero database is built: which game files each page reads, which numbers are calculated and how, what we cannot know yet, and when the data is refreshed.

Game build
26367565
Languages with game text
13
Map points placed
1,937
Region map sheets
8

What we read from the game

Game data

Every family of pages and the game tables it comes from. Row counts include entries that never get their own page (story variants, test rows, duplicates).

What we read from the game
DataRowsRead from
Weapons31DT_WeaponData, DT_WeaponSnapSoulText
Phantom Edges25DT_ShaqiWeaponData
Accessories66DT_Accessory
Medicines17DT_MedicineTable
Items278DT_InventoryData
Enemies177DT_CodexEnemyDataTable, DA_ActorConfig, ActorC_*
Talents32DT_AbilityNodesTable
Bells187DT_BellData
Regions15DT_MapData, DT_ChapterData
Tales70DT_QuestText, quest flow graphs
Merchants7DT_ShopTable, DT_ShopItemTable
Lore218DT_InventoryData
Achievements66DT_Achievement + Steam
Gallery146DT_BonusArt

Data: Phantom Blade Zero 26367565 (CL-302256, UE 5.7.4). How we source this

How the data is obtained

Game data

We read the PC game files of Phantom Blade Zero, build 26367565 (CL-302256, UE 5.7.4), with open-source Unreal Engine tools. The game's data tables (weapons, Phantom Edges, accessories, enemies, talents, Bells, quests and more) are exported as they are and loaded into our database without hand-editing.

Names and descriptions come from the game's own text in 13 languages. Where the game has no text in your language, names stay in English and the page says so.

Positions come from the game's level files: chests, pickups, Bells and Memory Flowers placed in the world (1,937 points on 8 region maps). Rewards handed out by the story or by quests come from the game's quest and dialogue flow graphs.

What is calculated

Calculated

Values marked Calculated are worked out from the game data with these rules.

  • Enemy stats at a level: every enemy has a base value per attribute (HP, Sha-Chi, attack) and the game's monster curve adds to it by level. Value at level L = Base + Base × curve(L), using the game's own curves.
  • Enemy level: the area level of the place the enemy spawns, from the game's area level table. Bosses placed by the story use their region's level range.
  • Remnant Dust per kill: the minimum and maximum the combat loot table gives at the enemy's level.
  • Upgrade totals (Remnant Dust and materials to max a weapon, Phantom Edge, accessory, medicine or the talent tree) are plain sums of the per-level costs in the game tables.
  • Map positions: the game ships hand-placed anchor points that tie world coordinates to each region map. We project every placed object with those anchors (a local fit over the nearest ones); tested against anchors left out, the error is 0.3 to 1.0% of the map width.
  • How to get an item: chests and pickups come from their placement in the level plus the loot table row they point to; boss, quest and story rewards come from the flow graph that grants them.

Steam statistics

Steam

Achievement unlock rates are Steam's public global statistics for Phantom Blade Zero, refreshed every few hours. If Steam cannot be reached, the page shows the last snapshot we saved. PS5 trophy status comes from the PS5 trophy ids in the game's achievement table.

How much has a known source

Rows with at least one known way to get them, out of all rows. The rest are granted in ways the data does not tie to a place, so their pages say so instead of guessing.

How much has a known source
DataWith a source
Weapons23 / 31
Phantom Edges23 / 25
Accessories61 / 66
Medicines16 / 17
Items204 / 278
Lore212 / 218
Boss rewards39 / 75
Quest rewards42 / 70

Limits

What these pages do not show, and why.

  • Difficulty: the multipliers for Wayfarer, Pathbreaker, Hellwalker and 66 Days are in the game's compiled code, not in its data tables, so enemy HP and damage are shown before difficulty is applied.
  • Later Cycles (New Game+): accessory tiers for later Cycles are in the data and shown, but any extra enemy scaling per Cycle is not, so it is not applied.
  • Story items: some gear and items are handed over by cutscenes or scripts with no fixed spot in the world. Those pages name the region or quest when the data has it and otherwise say no fixed spot is known.
  • Languages: Polish, Turkish, Czech, Arabic and Indonesian have no game text, so game names on those pages stay in English.
  • Unnamed entries: a few enemy attacks have no name in the game; where we label one from its internal id it is marked with an asterisk.

Updates

We extract the game again after each patch and reload the database; the build number at the foot of every page tells you which version you are looking at. If a number does not match your game, the report button on any page reaches us.

Every number in this database starts in the game files of build 26367565 (CL-302256, UE 5.7.4), read in 13 languages. Values derived from them carry a Calculated label and follow the rules above. Steam unlock rates are the only outside source; nothing is copied from other wikis or guides.

🔍

Help us maintain accuracy! If you notice incorrect stats, missing data, or any issues, your feedback directly improves the quality of our data for the entire community.

Report an Issue

Phantom Blade Zero data FAQ

Where does MetaBot's Phantom Blade Zero data come from?

From the PC game files of build 26367565 (CL-302256, UE 5.7.4): the game's data tables, its level files for positions and its quest flow graphs for rewards. Steam's public statistics supply the achievement unlock rates.

Are the boss HP values exact?

The base HP is exactly what the game data says. HP at a level is calculated with the game's own monster curve and area level, and is marked Calculated. Difficulty multipliers are not applied.

Do the numbers change on higher difficulties?

Yes in the game, but those multipliers live in compiled code rather than the data tables, so every value here is before difficulty.

How accurate are the map positions?

Positions are projected with the game's own map anchors. Checked against anchors left out of the fit, the error is 0.3 to 1.0% of the map width. 176 of the 187 Bells have a map position.

How often is the data updated?

After every game patch. The build number on every page shows which version the data comes from.