WIKI PBZ-WIKI
Menu

Language

English
  • English
  • Deutsch none
  • Español none
  • Español (LatAm) none
  • Français none
  • Italiano none
  • 日本語 none
  • 한국어 none
  • Português (Brasil) none
  • Português none
  • Русский none
  • ไทย none
  • Tiếng Việt none

Bosses

Three-Headed Woman

Three-Headed Woman: a boss tag and nothing else. A multi-target framework covering lock-on discipline, kill order and how to budget *Sha-Chi* for two bodies.

Last checked 23 Oct 2026 Thin record
On this page 6

Pre-release analysis. The source record holds a boss tag and nothing else: no moveset, no health value, no arena, no drop. Everything below is a framework for a multi-target boss, labeled where it is guesswork. We have not confirmed any of it in a build.

What the record says

Three-Headed Woman is a boss, and the two rosters disagree about her status: one files her as named, the other as provisionally named. That disagreement stays in this page rather than being resolved by us. Both agree on the part that changes your plan: a boss has its own health bar.

The name implies more than one head. Speculative — not confirmed: that could mean multiple hitboxes, multiple bars, or no mechanical weight at all. Prepare for the multi-body case, and drop it if the fight turns out to be a single target.

Assume more than one body

If two or more targets share the arena, four rules change.

  1. Stop locking the nearest body. Lock the one you are killing, and re-lock only after a kill.
  2. Kill the smaller target first if one exists. Fewer bodies beats more damage, every time.
  3. Never stand between two targets. Space so both are in front of you, or so one is off-screen and far.
  4. Spend your guard break on a kill, not on damage. A break that does not remove a body is a wasted bar.

Budget for a long fight

Speculative — not confirmed: multi-target fights should drain resources faster than duels, because chip damage comes from angles you are not watching.

ResourceWhy it matters hereFallback if it runs out
Sha-Chi barEvery break is a chance to delete a bodyParry plain attacks to refund; stop attacking
Second weaponClears your own guard break when two attacks land at onceHold guard stance and retreat — but only if the gauge allows
Potion bottles (2)Chip damage adds up between phasesClear trash elsewhere if the arena allows a reset
Phantom EdgeWide hits and shield breaks on clustered targetsSave charges for the second body, not the first
Sha-chi EssenceOne ultimate should end a body, not soften itBank it; do not fire it at half value

Camera and lock-on discipline

Speculative — not confirmed: most deaths in multi-target fights are camera deaths, not damage deaths.

  1. Fight with your back to open space. Corners kill you faster than any attack.
  2. Break lock the moment a second body leaves the frame. You need to know where it is more than you need the auto-face.
  3. Dodge sideways, not backwards. Backwards dodges walk you into the body you forgot about.
  4. Re-establish distance after every kill. Speculative — not confirmed: the remaining body gets faster, so you need the second to breathe.

Where this framework can be wrong

  • If she is a single body with three attack angles, the kill-order section is dead weight. Skip to spacing.
  • If the arena is a closed pit, the “fight with your back to open space” rule inverts: hold the center instead.
  • If she has an unblockable grab, guard stance is a trap. Dodge and parry only.
  • If her bar regenerates on body death, the whole budget table shifts toward burst.

Each is checkable in the first 60 seconds of a real attempt. Check before committing.

FAQ

Is there a confirmed moveset? No. Nothing beyond the boss tag is published, and we will not invent attack names to fill the gap.

Should I wait for launch data? Read this as preparation, not a route. System rules hold; specifics do not.

What is the safest loadout to walk in with? Two upgraded blades, both potion bottle slots filled, and one wide-hitting Phantom Edge. Nothing boss-specific is confirmed.

Last checked 23 Oct 2026.

Search the codex

Loading index…