Distance is the mechanic
Do not turn this into a melee greed guide. The source value is the repeated warning to keep space and answer ranged pressure first.
Bloodbath thread
A forum-style Shui Daoren desk for players who need distance discipline, P1 rock and missile rhythms, P2 yellow-light caution, support labels, and proof holds instead of a vague burst setup.
Maintained byHeavenskiss
Pinned Shui Daoren questions
The useful part of the Shui Daoren sources is the discipline: keep enough space to see the ranged rows, clear detached projectiles, then spend damage only when the pattern is actually over.
Because the fight is a distance-discipline check. The source route says the player should keep space, answer ranged patterns, and avoid greedy melee trades before thinking about output.
Start with three rows: falling slam rhythm, six-rock rhythm, and four-missile variants. The useful note is clearing the whole detached projectile row before taking damage time.
P2 adds delayed vine-cage damage, missile into yellow-light pressure, and a five-missile rhythm. It is lower tolerance, not a different build problem by default.
Treat those as source context. They can explain how the source author created recovery or burst windows, but the public guide should not present them as the only current Global route.
Do not turn this into a melee greed guide. The source value is the repeated warning to keep space and answer ranged pressure first.
Rocks and missiles can keep resolving while the boss is punishable. Clear the pattern before spending the opening.
The source frames the P2 yellow-light answer as a dodge row. Keep any cannot-deflect or dodge-direction claim behind Global clips.
NPC help, Flamethrower, and Taibai Zuiyue can be useful source notes, but boss pages still need tells and response rows first.
Pre-pull triage
Shui Daoren is perfect for the forum-notebook style because a player can diagnose the pull quickly: spacing collapse, rock rhythm, missile branch, delayed vine, yellow-light panic, or support/build context.
Search intent
The likely reader searches Shui Daoren, Sleeping Daoist, Bloodbath Shui Daoren, rocks, missiles, or yellow-light dodge after losing to ranged pressure.
Lead with distance discipline and pattern rows before build or Mystic Skill context.
Source shape
The deep source gives a practical route: support creates recovery time, then the player handles P1 and P2 ranged patterns from distance.
Keep the route as a field notebook, not a final Global rotation guide.
All-boss cross-check
The all-boss source also frames Shui Daoren as a four-star distance fight with P1 variants and dangerous P2 yellow-light pressure.
Use that as confidence for the page angle, but still hold exact timings and English names.
Output context
Flamethrower, Taibai Zuiyue, and execution-window notes explain how the source turns openings into damage.
Label them as source build context until Global names, current scaling, and cancel windows are captured.
Practical use
The reader action after death is simple: did you die from distance collapse, rocks, missiles, delayed vine cage, yellow light, or late P2 add pressure?
Make the after-death loop visible instead of writing a loose translation.
Pattern ledger
Open this after a death. Name the row that killed the pull, practice that one pattern, and leave exact timings or skill routes behind Global proof.
The deep source uses support mainly to interrupt and create time to recover, not as the real damage plan.
Record support as tolerance. If support helps, still learn the ranged rows so the page remains useful for solo or changed routes.
Hold: Current NPC name, availability, interruption behavior, and solo relevance need Global proof.
Both source rows warn against greedy close-range play because the boss can start too quickly and punish for heavy damage.
Keep enough space to see ranged patterns. If you died in melee, the first fix is spacing, not a new rotation.
Hold: Exact safe distance needs current arena screenshots or clips.
The deep source treats the slam as a rhythm row and says the useful response is on the falling timing.
Answer each falling hit, then spend the opening only after the third slam is handled. Do not start burst while the row is still active.
Hold: Exact deflect wording and current English move label need proof.
The source describes a countable rock row: early rocks are closer together, then the later rocks arrive after a small beat.
Practice this as a separate rock drill. Clear all rocks first, because detached projectiles can still hit during a punish or execution window.
Hold: The count and pause-beat notation need current clips before becoming final timing.
The source distinguishes missile variants by whether the middle hits connect tightly, with one branch leading into red-light pressure.
Watch the middle pair. If the row chains into the red cue, wait for the actual strike instead of mashing the same rhythm.
Hold: Global red cue wording, exact missile spacing, and branch behavior need proof.
The deep source uses Flamethrower, Taibai Zuiyue, and execution windows to convert successful pattern defense into damage.
Keep this as build context: create the opening by solving the pattern, then decide whether your current setup has a verified burst route.
Hold: Skill names, damage scaling, cancel timing, and current Global route need proof.
The source says phase 2 keeps a slam-style row, but adds delayed vine-cage damage after the landing.
Answer the landing hit late enough, then keep moving as if a delayed hazard still exists. Do not celebrate the first answer too early.
Hold: Vine-cage timing, damage window, and English label need clips.
The deep source says the missile row can lead into a yellow-light move and frames that yellow row as a dodge problem.
Treat yellow as a separate dodge-test row. If you cannot dodge it yet, plan recovery resources rather than pretending the row is solved.
Hold: Cannot-deflect, dodge direction, and late-dodge timing all need current Global proof.
The source describes a five-hit missile rhythm where the early beats are slower before the final hits tighten.
Practice the rhythm without attacking. This is a tolerance row: one missed beat can turn into potion or revive pressure.
Hold: Exact count, speed change, and current animation variants need proof.
The deep source says later phase-2 clone and named pressure are not the main problem once practiced, but gives little detail.
Keep this as a low-detail watch row. Do not write a final solution until the cue, spawn behavior, and response are captured.
Hold: Needs Global clip proof for clone tell, attack name, and safe response.
| Phase | Cue | Source read | Practice note | Proof hold |
|---|---|---|---|---|
| Setup Context | NPC interrupt and potion space | The deep source uses support mainly to interrupt and create time to recover, not as the real damage plan. | Record support as tolerance. If support helps, still learn the ranged rows so the page remains useful for solo or changed routes. | Current NPC name, availability, interruption behavior, and solo relevance need Global proof. |
| P1 Rule row | Distance baseline | Both source rows warn against greedy close-range play because the boss can start too quickly and punish for heavy damage. | Keep enough space to see ranged patterns. If you died in melee, the first fix is spacing, not a new rotation. | Exact safe distance needs current arena screenshots or clips. |
| P1 Rhythm row | Triple falling slam | The deep source treats the slam as a rhythm row and says the useful response is on the falling timing. | Answer each falling hit, then spend the opening only after the third slam is handled. Do not start burst while the row is still active. | Exact deflect wording and current English move label need proof. |
| P1 Projectile row | Six-rock rhythm | The source describes a countable rock row: early rocks are closer together, then the later rocks arrive after a small beat. | Practice this as a separate rock drill. Clear all rocks first, because detached projectiles can still hit during a punish or execution window. | The count and pause-beat notation need current clips before becoming final timing. |
| P1 Variant row | Four-missile variants | The source distinguishes missile variants by whether the middle hits connect tightly, with one branch leading into red-light pressure. | Watch the middle pair. If the row chains into the red cue, wait for the actual strike instead of mashing the same rhythm. | Global red cue wording, exact missile spacing, and branch behavior need proof. |
| P1 Build hold | Burst after execution window | The deep source uses Flamethrower, Taibai Zuiyue, and execution windows to convert successful pattern defense into damage. | Keep this as build context: create the opening by solving the pattern, then decide whether your current setup has a verified burst route. | Skill names, damage scaling, cancel timing, and current Global route need proof. |
| P2 Delayed row | Twisting slam into delayed vine cage | The source says phase 2 keeps a slam-style row, but adds delayed vine-cage damage after the landing. | Answer the landing hit late enough, then keep moving as if a delayed hazard still exists. Do not celebrate the first answer too early. | Vine-cage timing, damage window, and English label need clips. |
| P2 Yellow hold | Four missiles into yellow-light pressure | The deep source says the missile row can lead into a yellow-light move and frames that yellow row as a dodge problem. | Treat yellow as a separate dodge-test row. If you cannot dodge it yet, plan recovery resources rather than pretending the row is solved. | Cannot-deflect, dodge direction, and late-dodge timing all need current Global proof. |
| P2 Count row | Five-missile rhythm | The source describes a five-hit missile rhythm where the early beats are slower before the final hits tighten. | Practice the rhythm without attacking. This is a tolerance row: one missed beat can turn into potion or revive pressure. | Exact count, speed change, and current animation variants need proof. |
| P2 Low-detail | Clone and Wan Shui pressure | The deep source says later phase-2 clone and named pressure are not the main problem once practiced, but gives little detail. | Keep this as a low-detail watch row. Do not write a final solution until the cue, spawn behavior, and response are captured. | Needs Global clip proof for clone tell, attack name, and safe response. |
Risk labels
Route-context overclaim
Support can create recovery or interrupt windows, but the page should not imply a helper is required or always available.
Build and skill-name hold
Keep source rotation notes as context until English names, current scaling, and cancel windows are verified.
Notation treated as timer
Six rocks, four missiles, and five missiles are useful memory rows. They are not final timing charts without clips.
Counterplay overclaim
The source treats this as a dodge row. Any cannot-deflect, right-back dodge, or late-timing language needs current Global proof.
Hidden-damage window
The useful warning is that the landing answer may not end the danger. Exact delay and safe movement need proof.
Low-detail source note
Do not promote this into a full mechanic explanation until a current clip shows the tell and response.
After a melee death
Stop changing damage tools. First ask whether you lost spacing and let the boss start a close-range hit you could not read.
After a rock or missile death
Practice that one projectile row for several pulls. Do not burst after the first opening if detached projectiles are still resolving.
After a P2 yellow-light death
Treat it as a separate dodge-test row. Capture a clip if possible, because this is the claim most likely to become bad advice.
Before writing final advice
Capture the Global boss name, projectile variants, vine-cage timing, yellow-light answer, and whether source skill routes still work.
Promote this from distance notebook to exact guide only after these checks exist.
Source desk
Best used for distance discipline, support context, P1 slam, rocks, missile variants, P2 vine cage, yellow-light dodge claims, five-missile rhythm, and burst-window labels.
Open sourceBest used as confirmation that Shui Daoren belongs in the distance and projectile-pressure lane, with P2 yellow-light and high-damage charge rows kept behind proof labels.
Open sourceUse for Shui Daoren next to Qianye, Tian Ying, Bai Langzhu, and all-boss pressure rows.
Open threadCompare distance discipline here with Bai Langzhu's opener-family and move-string structure.
Open threadUse when a Shui Daoren row needs a tell, response, failure state, proof field, or owner route.
Open threadUse after the death cause is known and the remaining issue is survivability, tools, or resource investment.
Open threadNext boss step
This is the distance-discipline thread. A final Shui Daoren guide should come later, after each P1/P2 projectile row has current Global clips and the English-client names are proven.