The confirmed Phantom Blade Zero arsenal contains more than 30 main weapons and more than 20 Phantom Edges, with two of each equipped at once. The official sources do not yet publish all names, types, rarities, acquisition routes, or numerical effects. This index therefore begins with verified groups and a strict record template instead of presenting trailer nicknames as finished items.
Current catalog boundary
This is intentionally not a 50-item list. An identifiable animation is insufficient to establish the exact English item name, inventory classification, rarity, or retail source. Those fields become publishable when the Steam build or an official item description supplies them.
Fields required for every weapon
Each future card should include the displayed name, main-weapon or Phantom-Edge slot, in-game type, rarity label, acquisition source, effect, suitable player or matchup, evidence status, and detail page. Add range, resource, upgrade path, and patch only when the interface or repeatable testing supports them.
Use the game’s wording for rarity rather than importing a color hierarchy from another action RPG. Use a precise source such as “quest reward after [objective]” or “chest beside [landmark].” If there is a choice requirement, describe it before the reward so a player does not accidentally close the route.
Verification levels
Officially named
The English name and category appear in an S-GAME page, Steam description, official interface capture, or release material. This establishes identity, not final power.
Retail reproduced
The Steam build shows the item, source, and effect under recorded conditions. Numerical entries include a build or patch date.
Partially verified
The item identity is clear but one important field—often source, rarity, resource cost, or upgrade behavior—still lacks direct evidence.
Unlisted footage
An action is visible in promotional footage without enough information to create an item entry. It stays in research notes, not the player catalog.
How to record an acquisition source
Begin at a stable map landmark. Write the route in player order: starting point, turns or elevation changes, mechanism or fight requirement, container or NPC, and reward condition. Attach any quest state or chapter restriction. If the route is optional, say when the player can safely leave the main route.
For enemy drops, distinguish guaranteed first-clear rewards from repeatable random drops. A single observation cannot establish a drop rate. For vendors, record the currency, stock condition, and whether the item sells out. For edition items, separate an early entitlement from normal gameplay acquisition.
How to test effects
Test two weapons against the same enemy, difficulty, character state, and upgrade level. Record reach, commitment, recovery, visible resource, stagger behavior, and whether the action can be canceled. Damage is meaningful only with those conditions attached.
For Phantom Edges, identify the problem the effect solves. A tool might approach, create distance, control multiple enemies, extend an opening, or offer defensive utility. Describe the observed result before assigning a recommended audience. If a boss resists the effect, keep boss and regular-enemy results separate.
How to choose from an incomplete index
Before launch, choose by role, not rank. Plan one main weapon for dependable neutral interactions and a second for a different range or opening. Reserve the two Phantom Edge slots for missing functions. The Loadouts guide turns that four-slot structure into testable combinations.
After launch, filter first by what you can obtain at your campaign point. Then compare how safely each option handles the encounter that blocks you. A theoretical late-game damage leader is not a solution if its route is unavailable or its attack cannot fit the opening.
What the index will not do
It will not turn a demonstration loadout into an early-game recommendation, copy names from fan translations without an English game label, infer rarity from glow color, or publish damage without difficulty and upgrade context. It will not create separate canonical pages for spelling variants; aliases will point to the single verified item page.
Player contribution checklist
Useful evidence includes a clear inventory screen, acquisition location, map landmark, displayed description, equipped-slot proof, and build date. A clip should show setup and result rather than only the final hit. Remove personal account details before sharing captures. Conflicting observations remain flagged until the condition causing the difference is understood.