PHANTOM EDGES / database planEffects stay pending until verified
Database / ability layer

Phantom Edges

Phantom Edges are part of the game's public vocabulary and a likely center of build decisions. The useful details - cost, trigger, scaling and weapon links - still need an honest source.

20+ referencedEffects pendingBuild-linked

Why this deserves its own index

A weapon list answers what you hold. A Phantom Edge index should answer what changes when you activate it, what it costs, what it interrupts and how it reshapes a fight. Those are player decisions, not just nouns, so the data model needs more than a name and a short description.

Entry contract

  • Effect: the exact behavior observed in the current version.
  • Trigger: input, timing or resource condition, if the game exposes one.
  • Cost: meter, cooldown or other resource, not a guessed number.
  • Pairings: weapon or boss use cases supported by testing.
  • Acquisition: where it is earned, found or upgraded.

What will not be published

We will not turn a cinematic name into a fabricated ability, translate speculative forum lists into 鈥渙fficial鈥?entries or attach a tier rank before the player economy and difficulty context are understood. A smaller verified index will be more useful than a complete-looking one that collapses at launch.

Planned roster20+ references in public marketing language
Published entriesOpening gate: verified name, effect and source
Build plannerUses labels and preferences before it uses fake numbers
Spoiler levelAbility names can be mild; acquisition and boss links may be spoiler-marked
Pair this page with Build Lab for a pre-release planning profile.