Phantom Blade Zero Arsenal

The public scale of the Phantom Blade Zero arsenal is already distinctive: Steam and the official site describe more than 30 weapons and more than 20 Phantom Edges. The first gameplay trailer also separates two main weapons from the Phantom Edge tools and shows melee/ranged variety.

What belongs in an arsenal index

An honest pre-release index should record a weapon or tool only when its name or category is supported by a first-party source or clearly attributable official footage. Each record should eventually answer: what is it called, where is it shown, what role does it suggest, what inputs or resources does it use, and which build confirms its final behavior.

At this checkpoint, the high-confidence facts are the scale—30+ weapons and 20+ Phantom Edges—and the existence of multiple combat distances and tool types. The full catalog, acquisition routes, rarity, upgrade materials, damage, status effects, and final balance are not public in a complete form.

Read the count correctly

“More than 30” and “more than 20” are scope claims, not a promise that every item is immediately available, equally useful, or present in every mode. Do not turn those numbers into a numbered database with missing entries. A missing name is an unknown field, not an invitation to copy a fan list from an unrelated demo or platform.

The official site uses extensive arsenal language alongside its kungfu and Kungfupunk presentation. That supports a broad topic hub, but it does not establish a tier list. A tier list would require a stable build, a defined use case, and enough testing to compare tools fairly.

Useful categories for future pages

• Main weapons: the two-weapon framing shown in gameplay material; record the actual pairing rules only after a playable test.
• Phantom Edges: named as a distinct tool category; verify resource, cooldown, and progression behavior in the release build.
• Melee tools: compare reach, interruption, and recovery only from tested data.
• Ranged tools: verify ammunition, targeting, and encounter role rather than assuming a shooter-style loop.
• Unresolved inventory fields: acquisition, upgrades, rarity, passive effects, and exact stats remain pending.

How to avoid a misleading “best weapon” page

Separate the player question from the source claim. “Which weapon is best?” has no universal answer without a build, enemy, difficulty, and objective. “Which weapons are officially shown?” can be answered now. “Where do I obtain this weapon?” requires an in-game route or official launch documentation.

Use Combat for timing and decision-making, and Progression and Exploration for future acquisition context. Keep this hub as the canonical index so a later balance update does not require copying the same uncertain numbers into several articles.

How the index should grow

Start with official names and roles, then add player-facing fields only when a release build exposes them. A useful entry can include a source clip, the date it was checked, the menu where the item appears, its acquisition route, and a short description of its practical role. If the item is visible but its unlock condition is not, leave that field marked unknown.

Avoid a single giant table that forces mobile readers to scroll sideways or hides uncertainty in tiny columns. Cards or short sections can keep the name, evidence, role, and verification state together. When a balance patch changes one field, the canonical entry can be updated without rewriting every combat guide.

Acquisition is a separate question

The existence of more than 30 weapons does not tell a player where to find a particular one. Acquisition may depend on story progress, exploration, a challenge, or another system that has not been publicly documented. Keep “shown in a trailer” separate from “obtainable at launch,” and link any confirmed route to a dated Systems or Updates entry.

This is also why the hub does not publish a tier list. A ranking would need a stable catalog, defined encounters, tested inputs, and a version. Until then, the index is more valuable as a trustworthy map of evidence than as a speculative leaderboard.

A practical catalog schema

When the released game exposes a real inventory, build each entry around fields a player can verify. Start with the exact displayed name and the section of the menu where it appears. Add the weapon or Phantom Edge category, the source or unlock condition, the resources required to use or improve it, and the public version in which the record was checked. Only then add observed reach, recovery, status effect, interruption, or ranged behavior. A field that is not shown should remain unknown rather than receiving a value borrowed from a similar action game.

The same record should explain scope. Say whether the item belongs to the base game, a separate product, a preview, or a release branch. If an official clip shows a tool but does not name it, describe the evidence as an unnamed preview example and do not invent a catalog name. If a community guide supplies a working label, identify it as community terminology until an official source confirms the term.

Comparing tools without a false tier list

“Best weapon” is not one stable intent. A player may mean highest damage, safest defense, longest reach, easiest learning curve, or best fit for a particular encounter. A useful comparison therefore names the goal, build, enemy, difficulty, and version before making a recommendation. If those inputs are unavailable, publish the comparison criteria and the evidence boundary rather than ranking the arsenal.

Keep the index readable on a phone by using compact cards or stacked fields. Do not force an unknown-heavy table to scroll horizontally. Each card can link to Combat for tested use and Systems for the future acquisition route, while Updates owns balance or availability changes. This structure preserves a single canonical record as the catalog grows.