Bloodbath route notes

Bloodbath Gongsun Daye Route Notes

A forum-style Where Winds Meet Gongsun Daye desk that separates normal Bloodbath route notes from old-patch ranged-bait and corner-skip claims.

Gongsun DayeBloodbathRoute notesSkip risk

Maintained byHeavenskiss

Pinned Gongsun questions

This is a route thread, not a blind cheese repost.

The Gongsun sources are useful because they describe two different needs: learning the normal fight and testing shortcut behavior. The English page keeps those apart so a reader can practice the boss even if the old skip no longer works.

Before the pull

Keep the boss lesson and the shortcut test in different lanes.

A useful Gongsun page should answer a practical question after death: was the loss caused by palm timing, Shadowless Kick stamina, toad-mode greed, recovery timing, or an old shortcut that no longer behaves the same way?

Route rule

file note

Keep normal play first

The ordinary route gives the durable value: close-string recognition, stamina management, toad-mode branch reading, and recovery interrupts.

PalmKickToad

Route rule

file note

Stamina is the wall

Shadowless Kick is less about bravery and more about entering the row with enough stamina to dodge, turn, or answer the later kicks.

Full staminaBack awayDo not greed

Route rule

file note

Interrupts are test rows

The sources mention interrupting recovery, but the current Global timing, skill terms, and behavior need clips before becoming final advice.

RecoverySkill nameClip hold

Route rule

file note

Cheese stays labeled

Ranged-bait, command-read, and corner-position claims are useful leads, but they should stay visibly old-patch or low-detail until retested.

Old patchAI readRetest

Thread shape

Four Chinese posts become one English route ledger.

The page is arranged by reader need rather than source order: normal route first, risky skip rows second, then a proof queue for current Global behavior.

Search intent

The likely searcher uses Gongsun Daye, Grandpa Gongsun, Gongsun Da Ye, Bloodbath Gongsun, Shadowless Kick, toad mode, or skip/cheese terms after repeated deaths.

Lead with route notes and risk labels. Do not make the page only a translated cheese post.

Source shape

Two sources are practical normal-route notes; two sources are shortcut or low-detail behavior claims.

Split normal mechanics from skip claims so players can choose a route without confusing proof states.

Normal standards

The standard fight rows are palm combo, Shadowless Kick, three-punch-one-kick, toad jumps, blind/airwave, and wood-stake variants.

Turn each into a cue, practice answer, and proof-hold row.

Skip standards

The shortcut rows depend on ranged attacks during recovery, roughly measured spacing, Q-skill behavior, dodge-skill behavior, or a corner route.

Keep those rows in a visible hold state until current Global behavior is confirmed.

Proof queue

English boss names, skill mappings, AI command-read behavior, distance numbers, and old-patch dates all need verification.

Write as a route ledger with Global proof gaps, not a final current-client walkthrough.

Route ledger

Normal mechanics first, shortcut behavior last.

Each row is written as a fight note: cue, useful source read, practice answer, and what must stay on proof hold. That keeps the page usable without pretending every source detail is current.

RowCueSource readPractice noteProof holdStatus
SetupApproach, land a short hit string, then back outOne normal-route source frames the baseline as getting close for a couple of hits, then dodging back before Gongsun's close pressure starts.Use the first pulls to learn how far you can stand without triggering panic trades. If you get clipped while attacking, shorten the punish instead of adding more damage.Exact safe distance and current English boss label need Global screenshots or clips.Normal route
Close stringPalm combo with a long-tracking starter and a red-light enderThe normal notes say the first palm tracks farther than expected, while the final red-light hit is the clean answer point.Do not treat the first palm as the real punish window. Watch for the ender, answer the red cue, then spend a small punish.Move name, exact deflect wording, and current tracking distance need proof.Cue row
Close stringThree punches into one kickThe alternate normal source calls this a required response row and emphasizes the final red-flash moment.Practice it as a short memory drill: do not mash early, and do not move into output until the last cue has resolved.Exact hit count and deflect moment should stay source-labeled until Global clips confirm the animation.Timing hold
Shadowless KickLong kick chain after close pressureBoth normal sources treat the kick chain as the stamina check. One route favors back-dodge and running around; the other notes selective answers to later kicks.Enter the row with stamina. Back out early, turn with side dodges when needed, and preserve enough stamina for the final beats instead of trying to punish mid-chain.Exact kick numbers, dodge direction, and current English move name need Global proof.Stamina row
Toad modeTriple jumping toadThe source warning is simple: greedy attacks before the jump row is solved cause avoidable hits, and camera angle can make the first hit hard to read.Stop attacking when the branch starts. Use the row as a camera and rhythm drill, then punish only after the chain is over.Exact camera behavior and current hit count need clip proof.Branch row
Toad modeBlind or airwave into leap pressureThe normal notes describe a visible phantom or airwave-style branch that leads into a dodge check, but the timing language is source-only.React to the visible tell, not to a memorized second count. If the branch blinds or staggers you, reset space before taking damage time.Do not publish exact seconds, blind duration, or cannot-deflect wording until current Global clips exist.Proof hold
Toad modeWood-stake branch with red and yellow/gold cuesThe sources mention red and yellow or gold cue variants. The safe source recommendation is to dodge the row; red may have a deflect answer but is reaction-heavy.Use dodge as the public-safe practice answer for now. Keep any red-cue deflect route as an advanced test row.Cue color, dodge timing, and red-cue deflect reliability need Global proof.Color cue
RecoveryGongsun regains posture or blue bar through a recovery animationMultiple source notes mention interrupting recovery. The skip source ties that interrupt to ranged input during the recovery window before the hand drops.Record the animation and test whether your verified skill interrupts it now. If it fails, return to the normal palm/kick/toad route.Current interrupt timing, skill mappings, and posture or blue-bar behavior need proof.Test row
Skip claimRanged-bait loop around recovery and dodge behaviorThe old shortcut source says ranged attacks can force Gongsun Daye into dodging and can interrupt recovery before the hand-drop effect resolves.Treat this as a retest target, not the main guide. If you publish a clip later, include patch date, distance, input, and failure cases.The source says later fix status was unknown. AI behavior, distance, and current-client input terms must be retested.Old-patch hold
Pair sourceGongsun Deng corner route and Daye skill-read claimThe paired shortcut source is compact: it mentions a corner route for Gongsun Deng and a Nameless Sword dodge-skill idea for Gongsun Daye.Keep it as a lead for the skip-label workflow. Do not merge it into the standard Daye route until position, behavior, and skill labels are proved.Needs arena position screenshots, current AI behavior proof, and exact Global skill names.Low-detail hold

Risk labels

What this page should not overpromise.

Old-patch shortcut

The ranged-bait source says the later fix state was unknown. That is enough reason to keep the route visible but not recommended.

AI read language

Claims that the boss reads or does not read a command can change silently. They need current clips with input and patch date.

Distance numbers

Source values such as 1-2m or 3m are useful testing notes, not final safe-distance instructions.

Skill mapping

Q skill, dodge skill, Nameless Sword, and other input terms need exact Global-client names before guide wording is finalized.

No-damage framing

A route that can loop the boss is still not a public no-damage promise unless failure states and current behavior are documented.

Gongsun Deng corner

Corner-position routes belong in skip labels until current arena collision, boss leash, and behavior are captured.

After-death checklist

Use the next pull to test one thing.

Died to palms

Stop punishing early. Watch the long-tracking starter and save your clean answer for the red-light ender.

Died to Shadowless Kick

Enter with full stamina, dodge out earlier, and practice survival for the whole chain before trying to counter.

Died in toad mode

Pause output as soon as the branch starts. Identify whether it was triple jump, blind/airwave, or wood-stake cues.

Recovery reset the boss

Treat interrupt as a test. If your current skill does not stop the recovery, return to normal route practice.

Skip loop failed

Record distance, input, boss animation, and patch date. Do not keep forcing a shortcut that may be fixed.

Source desk

Every Gongsun row stays traceable.

Bloodbath Boss Routes

Use this when comparing Gongsun Daye against the broader Bloodbath boss desk and all-boss pressure rows.

Open thread

Cheese and Skip Labels

Use this before turning ranged-bait, corner, no-damage, or old-patch behavior into public instructions.

Open thread

Boss Mechanics Ledger

Use this when a Gongsun row needs a clean tell, counter, wipe cause, and proof field.

Open thread

Beginner Build Checklist

Use this only after the failure is clearly gear, Inner Ways, tuning, or resource investment instead of boss reading.

Open thread

Gongsun rule

A good Gongsun page should still help after a cheese route is patched. Keep the normal fight readable, then label shortcut behavior as a retest target.

Back to Boss Notebook