Phantom Blade Zero’s current arsenal evidence supports two different lookup questions. First, how large is the equipment system? Official materials say more than 30 weapons and more than 20 Phantom Edges. Second, how do those tools behave? The official gameplay article shows a two-main-weapon structure, Phantom Edge tools, and melee/ranged systems, but does not publish a complete database.
Confirmed fields and open fields
Confirmed or strongly supported
- The game has an extensive weapon system.
- Public descriptions use the scale of 30+ weapons and 20+ Phantom Edges.
- Gameplay material distinguishes main weapons from Phantom Edges.
- Melee and ranged weapon systems are part of the public combat presentation.
Not confirmed by the current source set
- The complete item names and catalog order.
- Weapon rarity, damage, upgrade costs, or final balance.
- Phantom Edge cooldowns, charges, ammunition, or resource rules.
- Whether a shown item is early-game, late-game, optional, or platform-specific.
- A universal best weapon or a final tier list.
A useful future record format
When a release-build catalog is available, give every entry a build date and a stable identity. Record the exact displayed name, category, acquisition location, upgrade path, primary role, resource requirement, and the test context. If a field is not visible, write “not shown” instead of filling it from a copied list.
For a combat comparison, state the objective: single target, crowd control, ranged safety, interruption, mobility, or a particular boss. A tool that is efficient for one objective may be poor for another. This is why the Arsenal hub should not become a ranking page by default.
Why Phantom Edges deserve their own label
The name signals that these tools are not merely alternate swords. Their exact role is still a release-build question, but the official distinction is enough to give players a dedicated concept. Future coverage should explain their input, resource, and tactical purpose only after those fields can be reproduced.
The same evidence rule applies to footage. An official clip can establish that a move or tool is shown; it cannot establish that it is unlocked at the same point for every player or remains unchanged at launch.
Where to continue
Read Parry, Dodge and Weapons for how to interpret the combat preview. Use Technical for platform boundaries rather than assuming that a weapon demonstration represents every supported device. Return to Updates when official arsenal details are added.
A player-facing comparison without a ranking
Before the catalog is final, compare tools by questions that remain stable: does the item work at close range, create space, interrupt an attack, affect more than one target, or help a player reposition? These are decision categories, not claimed stats. They can organize a future test without telling players that one item dominates every encounter.
For each tested entry, capture the displayed name exactly, the menu or location where it was found, the build, and the action that was tested. Record a resource change before and after use if one exists. If the tool was only shown in a trailer, mark its acquisition and resource fields as unknown instead of copying a community assumption.
Why counts are not a catalog
The 30+ and 20+ figures are useful because they establish scale, but they also warn against premature completeness. A list with ten invented or unverified entries is worse than a shorter list that tells players why the remaining fields are pending. When official material names a new item, add the source first and wait for a usable description before expanding its route.
If a future patch changes a weapon or Phantom Edge, update the item record and note the old build. Do not rewrite a historical observation as if it described the new balance.
How to read a weapon record
For an item that is officially named, begin with the source and the exact role the source supports. An official page may establish that a tool exists, while a trailer may show it in a particular scene without showing its menu, cost, or unlock. Keep those as separate fields. “Shown in official footage” is stronger than an anonymous screenshot for existence, but it is still not evidence of final damage, rarity, resource consumption, or upgrade scaling.
Once a public build is available, add one dated observation at a time: menu location, starting state, action used, target context, result, and whether the result repeated. If the item has several modes, record each mode separately instead of collapsing them into a single adjective such as versatile. Link the observation to Combat when it affects parry, dodge, range, or recovery, and to Systems when the important question is acquisition or progression.
Phantom Edges and main weapons are different fields
Do not treat the two categories as interchangeable slots. The public framing distinguishes the main weapons from Phantom Edges, so a future comparison should say which category is being discussed and what the player can change. A clip that combines a weapon strike with a Phantom Edge effect does not prove which resource, cooldown, or progression rule belongs to either component. Those fields need a menu or release-build test.
If a player asks for the strongest combination before those rules are available, answer with the comparison criteria: encounter goal, distance, defensive risk, recovery, and version. A cautious framework helps players evaluate a later catalog without filling the current index with unsupported names or numbers.