Slow does not mean free
Xiao Shiqi's early strings are readable, but the page should still teach the full row before output.
Bloodbath route notes
Bloodbath Xiao Shiqi Route Notes
A forum-style Where Winds Meet Xiao Shiqi desk that turns slow-string, phase-2, stamina, helper, and proof-hold source notes into practical pull review rows.
Xiao ShiqiBloodbathRoute notesPhase 2
Maintained byHeavenskiss
Pinned Xiao questions
Slow strings are a study window, not permission to mash.
Xiao Shiqi source notes are useful because they explain why the fight can feel simple at first and expensive later: long health, fixed follow-ups, phase-2 learning cost, stamina pressure, and support tools that should be labeled as tolerance rather than universal answers.
Why does Xiao Shiqi feel easy, then suddenly expensive?
Because phase 1 is slow enough to study, while later rows punish greed, stamina loss, and assuming the fight is over after one health bar.
What should I learn before thinking about damage?
Learn the slow P1 string endings: opening leap plus follow-up, sweep into two slow fists, and the gold-charge headbutt branch.
How should I handle the second phase without memorizing everything?
Use the source rule as a practice frame: dodge the first hit of a combo, then only parry follow-ups you can actually read. Interrupts and disarm tools are recovery context.
Can I trust the helper, poison-blade, or 100% parry claims?
Not as final Global advice. They are useful source leads, but exact helper behavior, cannot-parry wording, input names, and timing claims need current clips.
Before the pull
Treat Xiao Shiqi as an endurance and decision boss.
The most useful source lesson is not one magic build. It is the decision order after a failed pull: did you hit too early, miss the gold-charge read, burn stamina in phase 2, trust a blade-state parry, or over-rely on support?
Process the whole string
The all-boss source warns that some starters have fixed follow-ups. Do not hit after the first dodge unless the row is actually over.
P2 is dodge-first
The dedicated source says phase-2 learning is costly and suggests dodging the first hit before deciding whether to parry follow-ups.
Tools are tolerance
Nameless Sword movement, interrupt windows, disarm skills, and helper shots should be labeled as route context until Global behavior is captured.
Thread shape
Three source rows become one pull-review ledger.
The page is organized by failure type rather than source order: slow P1, gold-charge branch, P2 survival, stamina recovery, support context, and proof holds.
Search intent
The likely reader searches Xiao Shiqi, Little Seventeen, Bloodbath Xiao Shiqi, phase 2, gold charge, poison blade, or why the boss returns after one bar.
Lead with failure rows and phase surprise, then route build/tool claims as context.
Source shape
The dedicated source gives a Bloodbath route note; two all-boss sources add slow-string, HP, helper, and phase-surprise context.
Use the dedicated source for route structure and all-boss sources for cross-check rows.
P1 value
The useful P1 lesson is not a perfect combo. It is learning slow openings, fixed follow-ups, and the fire-rocket or gold-charge branch.
Turn P1 into cue rows instead of a loose paragraph.
P2 value
The source does not ask readers to master every P2 chain first. It gives a fallback: dodge first hits, parry only known follow-ups, and use interrupts when available.
Publish the decision rule, but hold exact move names and input mappings.
Proof queue
100% parry language, cannot-parry poison blade, Yuan helper behavior, shift/Q/tilde inputs, and phase-health behavior all need current Global proof.
Keep every risky claim visibly labeled as source notation or proof hold.
Route ledger
Cue rows before tool advice.
Each row gives a source read, a practice answer, and the proof that still needs to be captured before this becomes exact Global advice.
| Row | Cue | Source read | Practice note | Proof hold | Status |
|---|---|---|---|---|---|
| Setup | High HP and a later phase surprise | The all-boss notes describe Xiao Shiqi as easier to read than some walls but thick enough to become an endurance fight; another row warns that the boss can return after the first bar. | Do not spend all potions or stamina as if one bar ends the fight. Treat early pulls as learning runs, not kill attempts. | Current phase-health behavior and English boss label need Global proof. | Route frame |
| P1 | Slow baseline strings | The dedicated source says phase-1 moves are slow enough to kite or visually parry, while the all-boss source calls out slow blade and fist rows. | Use the slow pace to study endpoints. Punish after the string ends, not after the first readable motion. | Exact move names and current parry windows need clip proof. | Practice row |
| P1 | Opening leap with a fixed follow-up | One all-boss source notes an opening leap that can be followed by another fixed hit. | Dodge or answer the leap, then wait for the follow-up before attacking. This is a greed check. | Follow-up timing and current animation variants need proof. | Greed check |
| P1 | Sweep leg into two slow fists | The all-boss source separates a sweep-leg starter from two slower fist hits afterward. | Treat the row as one sequence: handle the leg, handle both fists, then take damage time. | Exact cue names and hit count need current Global clips. | String row |
| P1 | Fire-rocket headbutt and two-stage gold charge | The dedicated source highlights a fire-rocket headbutt branch and a two-stage gold-charge answer; the author recommends moving away first rather than forcing a blind answer. | Back away to create a visible read, then answer the charge only when the cue is clear. Keep the source's perfect-parry wording as a test note, not a promise. | Gold cue wording, charge count, and any 100% parry claim need proof. | Gold hold |
| Tool context | Nameless Sword Q and tilde movement | The dedicated source uses Nameless Sword movement stages to move in and out while creating charged-attack or poke windows. | Use movement tools to control spacing, but do not make them mandatory until current English input names and skill behavior are confirmed. | Q, tilde, skill-stage names, and current weapon behavior need Global proof. | Input hold |
| P2 | Combo first hits become expensive to learn | The dedicated source says phase-2 learning cost is high and gives a simple rule: dodge the first hit of a combo, then parry follow-ups only if you can read them. | Make survival the first P2 goal. Dodge the starter, decide whether the next beat is readable, and interrupt only when your tool is ready. | Shift input, follow-up count, and exact interrupt timing need proof. | Dodge-first |
| P2 | Poison-blade or blade-state attacks | The all-boss source claims that blade attacks in this state should be dodged rather than parried. | Label this as a dodge row until current Global clips confirm whether the attacks truly cannot be parried. | Cannot-parry wording, state trigger, and move names need proof. | Cannot-parry hold |
| Low HP | Red-hot ground slam, fist, and charge pressure | One source separates red-hot ground slam plus fist from a charge route that may require dodge or parry-then-dodge handling. | Do not flatten this into one red cue. Track whether the row is slam-plus-fist or charge, then answer the second hit or displacement risk. | Low-HP trigger, red-hot wording, displacement behavior, and safe response need proof. | Low-HP hold |
| Recovery | Disarm skill or interrupt as breathing room | The dedicated source mentions using interrupt windows and a disarm skill when stamina is gone to create a moment to breathe. | Use this as recovery context. If the tool fails or the timing is wrong, reset to spacing instead of assuming the page promised a bailout. | Exact skill name, stamina interaction, and interrupt reliability need current proof. | Recovery context |
| Helper context | Yuan helper or NPC pressure during long windups | The all-boss sources mention a helper/NPC route where Xiao Shiqi's long windups can be punished or interrupted by support. | Record helper value as tolerance, not as the base route. The public page should still teach tells for players without that support state. | Helper name, availability, targeting, and current Bloodbath behavior need proof. | Support hold |
Risk labels
What the Xiao page should not overpromise.
Phase surprise
Source notes about returning after one bar or a later full-health phase need current Global confirmation before exact warnings become final.
100% parry wording
The source's perfect-parry confidence is useful as a test target, but public advice should not promise 100% without current clips.
Cannot-parry blade state
Poison-blade or blade-state dodge claims need proof of cue, state trigger, and current parry rules.
Input mappings
Shift, Q, tilde, Nameless Sword stages, interrupt tools, and disarm skills need exact Global-client names.
Helper reliability
NPC or Yuan helper behavior can depend on state, patch, positioning, and mode. Treat it as tolerance until tested.
Build drift
Weapon movement and charged-attack windows can drift with balance patches, so the page should teach the boss row before the tool route.
After-death checklist
Make the next pull test one failure.
Hit after the first slow cue
Wait for the fixed follow-up. Xiao Shiqi is slow, but several rows are not over after the first dodge.
Lost to gold charge
Back away first, create a cleaner read, then test whether your current route wants dodge, parry, or parry-then-dodge.
Phase 2 drained stamina
Use the dodge-first rule. Survive starters before trying to parry every follow-up.
Poison blade clipped you
Treat blade-state rows as dodge tests until a current clip proves a reliable parry answer.
Helper did not save the pull
Return to the cue rows. Support is a tolerance layer, not the route's foundation.
Source desk
Every Xiao row stays traceable.
小十七浴血難度打法教學Dedicated route source
Slow phase-1 learning, fire-rocket headbutt, gold-charge answer, Nameless Sword movement, phase-2 dodge-first rule, interrupt, and disarm recovery context.
Open source浴血難度各BOSS打法攻略All-boss cross-check
Adds slow-string details, follow-up cautions, poison-blade dodge claim, red-hot pressure, and phase-surprise warning.
Open source浴血難度各BOSS打法要點分享All-boss route context
Adds HP/endurance framing, phase-1 readability, and Yuan helper or NPC support context.
Open sourceBloodbath Boss Routes
Use this when comparing Xiao Shiqi against the broader Bloodbath boss desk and all-boss pressure rows.
Open threadBoss Mechanics Ledger
Use this when a Xiao row needs a clean tell, counter, wipe cause, and proof field.
Open threadBeginner Build Checklist
Use this only after the failure is clearly gear, Inner Ways, tuning, or resource investment instead of boss reading.
Open threadCheese and Skip Labels
Use this if helper, disarm, or terrain-like simplification turns into a shortcut claim that needs risk labeling.
Open threadXiao rule
A useful Xiao Shiqi page should reduce phase-2 panic. Teach the sequence first, label support and tool claims second, and keep perfect-answer language behind current proof.