Sort by opener family
Claw, blade, glow, knives, drift-back, and tree-jump rows should stay separate. The fight feels random when every starter is flattened into one parry tip.
Bloodbath thread
Bloodbath Bai Langzhu Move Notes
A forum-style Bai Langzhu desk for players who need P1/P2 opener families, claw and blade string distinctions, yellow-light caution, and proof labels instead of a vague one-build answer.
Bai LangzhuWhite Wolf LordMove stringsBloodbath
Maintained byHeavenskiss
Pinned Bai Langzhu questions
Learn the starter before arguing with the damage.
Bai Langzhu is a good source row because it is not trying to sell a build. It names the little places where players get tricked: similar-looking starts, second-layer sword qi, and phase-2 rows that need proof before they become final advice.
Is Bai Langzhu a build problem or a move-recognition problem?
Start as if it is a move-recognition problem. The source is valuable because it separates opener families and follow-up counts, so the English page should act like a move ledger before it talks about builds.
Why do the claw and blade rows feel similar after the opener?
The practical answer is to name the opener first, then prepare for the longer claw chain when the first read is unclear. Counts are useful practice notation, not a final input chart.
What changes in phase 2 besides the boss getting faster?
P2 adds flying knives, faster blade pressure, drift-back returns, and close-range yellow-light rows. The source threshold and timing language need Global clips before they become final advice.
Can I trust the 70% phase threshold and yellow-light deflect note?
Use them as test targets, not guarantees. The public page should expose the source claim, then say exactly what screenshot or clip is still missing.
Prepare the longer claw chain
When a blade or claw start is unclear, practice as if the longer claw pressure is coming. It is safer than swinging after the first readable hit.
Keep counts as notation
Source counts like 12, 3 or 1, 23456 are useful memory hooks. They are not frame data and should not be sold as final Global timing.
Flag threshold and yellow-light claims
The 70% phase note, close-range yellow-light deflect, and fast second-swing timing all need current-client proof.
Pre-pull triage
This page is useful only if it stays honest about uncertainty.
The source gives strong move-family notes, but the risky details are exactly the details English players will copy: 70%, 0-frame, fast flash, and yellow-light answers. Those stay labeled until the Global client proves them.
Search intent
The likely reader searches Bai Langzhu, White Wolf Lord, Bloodbath Bai Langzhu, or white wolf boss after dying to a similar-looking string.
Lead with opener families and practice rows, then send build questions back to the build checklist.
Source shape
The source is not a broad build guide. It is a move-string analysis with P1/P2 notes, counts, and several timing claims.
Preserve the string distinctions and mark counts as source notation.
Name proof
Bai Langzhu and White Wolf Lord are working English search labels until the Global client name is captured.
Use both names for discovery, but keep exact move names behind proof rows.
Timing risk
The source includes fast-flash, about-one-second, 0-frame, 0.5-second, and 70% threshold language.
Show these as proof targets, not as final English guide timings.
Practical use
The useful reader action is naming the opener after a death: glowing hand, claw chain, blade charge, flying knives, drift-back return, or yellow-light row.
Make the after-death loop visible so the page feels like a forum note players can actually use.
Move ledger
Keep each opener family in its own row.
This is the desk to open after a death. Name the first cue, read the likely follow-up, then decide what still needs proof before it can be promoted into an exact English walkthrough.
Backjump into two-hit follow-up
The source separates a retreating jump from the follow-up pressure instead of treating it as a simple disengage.
Do not chase the backjump. Watch whether it becomes the two-hit follow-up or a charged dash, then answer the return.
Hold: Needs Global clip proof for the exact return animation and punish window.
Both hands glow, fast flash
The source warns that this fast-flash row should not be treated like a normal deflect window.
Treat it as a danger cue during practice. Test dodge, spacing, and deflect separately before publishing a final answer.
Hold: The cannot-deflect reading needs current-client proof.
One-hand glow into delayed re-entry
The source describes an answer, then a delayed return that needs a second answer as the boss bounces away and rushes again.
After the first answer, keep watching the boss instead of spending the punish early. Prepare the second response on re-entry.
Hold: The delay length is source notation, not a final timer.
Claw string
The source gives count-style claw notation and treats the claw family as a memorization row.
Practice this as a family, not a single hit. If the opener is ambiguous, assume the longer chain and punish after the string is truly over.
Hold: Exact hit count and current Global animation variants need clips.
Charged blade plus sword-qi pressure
The source distinguishes the blade charge from the claw strings and calls out a second pressure layer from sword qi.
Respect the second layer. A good first answer does not mean the row is over if sword qi follows.
Hold: Needs clip proof before turning this into a two-deflect chart.
Tree jump or howl
The source frames this as the low-pressure row compared with claw and blade strings.
Use it to reset camera, heal only if safe, or take a measured punish. Do not confuse it with the charged return rows.
Hold: Current punish window and recovery safety need verification.
Flying knives
The source writes the knives as a countable rhythm, with a grouped first part and a later third beat.
Count it as source notation while practicing. Keep your eyes on the boss after the first two beats instead of assuming the row is done.
Hold: The 12, 3 rhythm needs a current Global clip before final wording.
Fast claw opener
The source says the phase-2 claw opener can start extremely quickly and resembles the phase-1 claw family.
Treat early P2 as a readiness check. When the first tell is unclear, hold your punish and prepare for claw pressure.
Hold: Zero-frame language is a source warning, not a measured frame claim.
Blade starter into multi-claw pressure
The source warns that one blade-looking starter can be confused with a longer claw sequence.
If you cannot tell which row started, defend as if the five-claw continuation exists. The page should teach caution before damage greed.
Hold: Exact string split and hit count need Global proof.
Charged blade, faster second swing
The source contrasts this with P1 and says the later swing arrives faster in phase 2.
Practice the P2 version separately from P1. The correct habit is preparing early for the second layer, not memorizing a fake universal timer.
Hold: The 0.5-second wording needs clip proof before publication as timing.
Drift-back return with spin and sword qi
The source describes a retreating movement that comes back into spin pressure and sword qi.
Do not chase the drift-back. Keep the boss centered, then read the return instead of swinging into the spin.
Hold: Needs Global clip for camera, spacing, and sword-qi follow-up.
Close-range yellow-light rows
The source says some close-range yellow-light rows can be answered at the flash moment and may be followed by a back-kick style hit.
Treat this as a test row: learn the yellow cue, then prove whether the flash answer, dodge, or spacing answer is best in Global.
Hold: Yellow-light deflect and follow-up behavior are proof holds.
| Phase | Cue | Source read | Practice note | Proof hold |
|---|---|---|---|---|
| P1 Opener row | Backjump into two-hit follow-up | The source separates a retreating jump from the follow-up pressure instead of treating it as a simple disengage. | Do not chase the backjump. Watch whether it becomes the two-hit follow-up or a charged dash, then answer the return. | Needs Global clip proof for the exact return animation and punish window. |
| P1 Proof hold | Both hands glow, fast flash | The source warns that this fast-flash row should not be treated like a normal deflect window. | Treat it as a danger cue during practice. Test dodge, spacing, and deflect separately before publishing a final answer. | The cannot-deflect reading needs current-client proof. |
| P1 Two-step row | One-hand glow into delayed re-entry | The source describes an answer, then a delayed return that needs a second answer as the boss bounces away and rushes again. | After the first answer, keep watching the boss instead of spending the punish early. Prepare the second response on re-entry. | The delay length is source notation, not a final timer. |
| P1 Count row | Claw string | The source gives count-style claw notation and treats the claw family as a memorization row. | Practice this as a family, not a single hit. If the opener is ambiguous, assume the longer chain and punish after the string is truly over. | Exact hit count and current Global animation variants need clips. |
| P1 Blade row | Charged blade plus sword-qi pressure | The source distinguishes the blade charge from the claw strings and calls out a second pressure layer from sword qi. | Respect the second layer. A good first answer does not mean the row is over if sword qi follows. | Needs clip proof before turning this into a two-deflect chart. |
| P1 Reset row | Tree jump or howl | The source frames this as the low-pressure row compared with claw and blade strings. | Use it to reset camera, heal only if safe, or take a measured punish. Do not confuse it with the charged return rows. | Current punish window and recovery safety need verification. |
| P2 Count row | Flying knives | The source writes the knives as a countable rhythm, with a grouped first part and a later third beat. | Count it as source notation while practicing. Keep your eyes on the boss after the first two beats instead of assuming the row is done. | The 12, 3 rhythm needs a current Global clip before final wording. |
| P2 Danger row | Fast claw opener | The source says the phase-2 claw opener can start extremely quickly and resembles the phase-1 claw family. | Treat early P2 as a readiness check. When the first tell is unclear, hold your punish and prepare for claw pressure. | Zero-frame language is a source warning, not a measured frame claim. |
| P2 Ambiguous row | Blade starter into multi-claw pressure | The source warns that one blade-looking starter can be confused with a longer claw sequence. | If you cannot tell which row started, defend as if the five-claw continuation exists. The page should teach caution before damage greed. | Exact string split and hit count need Global proof. |
| P2 Retest row | Charged blade, faster second swing | The source contrasts this with P1 and says the later swing arrives faster in phase 2. | Practice the P2 version separately from P1. The correct habit is preparing early for the second layer, not memorizing a fake universal timer. | The 0.5-second wording needs clip proof before publication as timing. |
| P2 Sight-read row | Drift-back return with spin and sword qi | The source describes a retreating movement that comes back into spin pressure and sword qi. | Do not chase the drift-back. Keep the boss centered, then read the return instead of swinging into the spin. | Needs Global clip for camera, spacing, and sword-qi follow-up. |
| P2 Yellow hold | Close-range yellow-light rows | The source says some close-range yellow-light rows can be answered at the flash moment and may be followed by a back-kick style hit. | Treat this as a test row: learn the yellow cue, then prove whether the flash answer, dodge, or spacing answer is best in Global. | Yellow-light deflect and follow-up behavior are proof holds. |
Risk labels
These are useful notes, not final frame data.
Threshold overclaim
70% phase trigger
Keep the number as a source checkpoint only. A final walkthrough needs a current Global clip showing the transition and HP context.
Counterplay overclaim
Cannot-deflect fast flash
Do not say the move cannot be deflected until dodge, spacing, and deflect attempts are checked in the current client.
Measured-timing overclaim
Zero-frame or 0.5-second language
Use these as warning labels. They are source impressions until a clipped test gives real timing or a safer visual cue.
Cue-type confusion
Yellow-light deflect
Yellow-light rows often invite bad advice. Publish the source claim only as a test target until Global clips confirm the answer.
Notation treated as command chart
Count strings
Counts are useful for memory. They should not become a guaranteed input chart without variant checks.
Practice loop
After a P1 death
Write down the first family you saw: backjump, glow, claw, blade, or tree jump. Practice that family for a few pulls before changing gear.
After a P2 opener death
Assume similar starters can split into different strings. Hold punish until you know whether knives, claw, blade, or drift-back return is active.
After a yellow-light death
Clip the attempt if possible. This row needs visual proof because the source answer may not match every current Global behavior.
Before writing final advice
Capture the Global boss name, phase transition, yellow-light response, and one clean clip for each high-pressure P1/P2 family.
Proof queue
Promote this from move notebook to exact guide only after these checks exist.
- Exact Global boss name and whether White Wolf Lord is the current English label
- Current phase transition proof for the source's 70% P2 note
- Clip proof for P1 glow, claw, blade charge, sword-qi follow-up, and tree-jump recovery
- Clip proof for P2 flying knives, fast claw opener, blade-to-claw ambiguity, drift-back return, and yellow-light rows
- Current answer proof for source claims about cannot-deflect, flash-moment deflect, and fast second-swing timing
Source desk
Keep the move ledger traceable.
Bloodbath Boss Routes
Use for Bai Langzhu next to Qianye, Tian Ying, Shui Daoren, and all-boss pressure rows.
Open threadBloodbath Qianye Phase Notes
Compare this move-ledger page with Qianye's phase-practice structure and risk labels.
Open threadBoss Mechanics Ledger
Use when a Bai Langzhu row needs a tell, response, failure state, proof field, or owner route.
Open threadCheese and Skip Labels
Use if a Bai Langzhu route becomes a shortcut, terrain, skip, or old-patch claim.
Open threadNext boss step
This is the move-string thread. A final Bai Langzhu guide should come later, after each P1/P2 row has current Global clips and the English-client names are proven.