Boss mechanics note

Shadow Puppeteer Mechanics Note

A forum-style mechanics note for Shadow Puppeteer: which rows ask for parry, which rows ask for dodge or retreat, what phase two adds, and what still needs Global proof.

Shadow PuppeteerParry splitPhase twoProof holds

Maintained byHeavenskiss

Pinned boss read

This is a parry split problem, not a build ranking.

Public-use stance

Shadow Puppeteer becomes readable when the source rows are separated by answer type. Normal jump and combo pressure can train parry rhythm; the glowing spear jump is a dodge-first warning; phase two adds shadows, spikes, uppercut pressure, and a tornado retreat call. Weapon comfort belongs in a separate context box.

Mechanic marker

file note

Read before output

This source row is strongest as a tell/counter page. The boss punishes players who treat every flash as the same answer.

TellCounterFailure

Mechanic marker

file note

Dodge the glow row

The detailed source calls the high jump with glowing spear a no-parry row. Keep it as a dodge-first practice cue until clipped on Global.

GlowDodgeProof hold

Mechanic marker

file note

Do not ignore shadows

Phase two begins with shadow summons and ground spikes. The page should not collapse that into vague 'hit boss harder' advice.

SummonsSpikesReset

Mechanic marker

file note

Retreat from tornado

When the boss raises both hands for the tornado-style pressure, the public-safe action is to leave the boss, not greed damage.

Hands upRetreatNo greed

Move ledger

Write the boss as cue, answer, and failure state.

Phase one

Jump smash

Stable cue
Source read
The detailed source describes a leap into a floor smash and frames it as one of the easier rows to answer.
Public use
Practice the landing cue. Treat it as a parry-or-dodge row rather than a damage window.
Failure
Greeding before the landing turns a simple cue into a knockdown or posture loss.
Phase one

High jump with glowing spear

Dodge row
Source read
The detailed source says the spear glows while the boss is airborne and that this row should not be parried.
Public use
Call it a dodge-first row. Watch the weapon, dodge on the flash, then reset instead of trying to parry through it.
Failure
Treating it like the normal jump smash is the likely death pattern.
Phase one

Close combo string

Parry row
Source read
The detailed source says repeated parries during the string can drive down the boss's toughness or posture bar quickly.
Public use
Practice the string as a rhythm row. The point is not button mashing; it is staying ready until the boss stops.
Failure
Early output before the string ends breaks the rhythm and delays the execution window.
Phase two opener

Two shadow summons and ground spikes

Add row
Source read
The detailed source says phase two starts with two shadows, then spikes appear under the shadows' feet.
Public use
Mark the opener as add control plus spike awareness. Clear the immediate chaos before tunneling the boss.
Failure
Standing on the spike lane or fighting both summons and boss pressure at once creates avoidable damage.
Phase two

Uppercut into thrust

Timing hold
Source read
The detailed source describes an uppercut followed by a thrust, with weapon glow before the dodge moment. It also says a precise parry can work.
Public use
For public advice, teach the visible sequence first: uppercut, watch the weapon, answer the thrust. Put exact parry timing behind proof.
Failure
Trying to fully parry the whole sequence without timing proof is a bad first-learning route.
Phase two

Boss down / execution recovery

Output row
Source read
The detailed source says an execution after a phase-two knockdown gives a longer stagger or recovery window.
Public use
Treat the downed state as the real output window. Spend damage here instead of forcing unsafe hits during unread strings.
Failure
Missing the execution or arriving empty on resources makes the fight feel longer than it needs to be.
Phase two

Tornado-style pressure

Retreat row
Source read
The detailed source says the boss raises both hands before a tornado attack with high damage and toughness damage.
Public use
Call retreat immediately when the hands rise. This is not the row to test greed or short-range trading.
Failure
Staying near the boss can burn health and posture together.

Response split

Do not answer every flash with the same input.

Parry-friendly

Normal jump smash, close combo string, some phase-two thrust pressure if timing is proven.

Use this only as a practice grouping. The final Global move names and timing windows need clips.

Dodge-first

High jump with glowing spear, weapon-flash row, tornado retreat.

This is the safer public row because the source explicitly separates at least one glowing-spear move from parry advice.

Control first

Phase-two shadow summons and ground spikes.

The player problem is not a parry input; it is target priority and floor awareness.

Phase two

Phase two is an add-control and spacing check before it is a duel.

Clear the screen before you chase damage.

The second phase starts with shadows and floor pressure. If the player keeps staring at the main boss, the failure feels random; if the row is treated as add control plus floor read, the fight becomes much easier to practice.

Mark shadows as a priority task, not background noise.
Leave spike lanes before committing to a punish window.
Save real output for knockdown or execution recovery.
Call tornado retreat as soon as the hands rise.

Source boundary

Use weapon notes as context, not as the whole answer.

Detailed guide

Useful: Good structure: phase one, phase two, jump smash, glowing spear, combo string, shadows, spikes, uppercut/thrust, execution window, tornado retreat.

Hold: Final English boss name, final move names, current toughness/posture wording, dodge timing, and exact parry reliability.

Player notes

Useful: Good caution: weapon feel matters, shield/guard-counter routes may make mistakes easier, and dual-blade dodge rhythm is a different learning path.

Hold: Weapon names, shield behavior, fire-paper item name, pull-distance cheese, and whether the phase-two simplification is current on Global.

Proof holds

What stays behind screenshots and clips.

Keep the page useful without pretending it is final.

The public page can teach the move families now. It should not publish exact timings, final English terms, weapon rankings, or shortcut routes until the Global client confirms them.

  • Final Global name for 皮影師 and whether Shadow Puppeteer is the live English label.
  • Current English wording for toughness, posture, execution, parry, dodge, and any phase-two summon labels.
  • Clips for glowing-spear cannot-parry behavior, phase-two uppercut/thrust parry timing, and tornado hitbox range.
  • Screenshots for phase-two shadow summons, ground spikes, boss-down execution prompt, and move cue colors.
  • Retest any weapon-specific shield, dual-blade, fire-paper, or pull-distance route before it becomes public recommendation.
Boss Mechanics Ledger

Source routing and proof rules for boss, dungeon, and raid rows.

Boss Notebook

Main board for Bloodbath, dungeon, raid, field boss, and skip-routing pages.

Beginner Build Checklist

Use only after the fight problem is clearly build comfort or resource setup.

Cheese and Skip Labels

Use if pull-distance or shortcut advice starts to look patch-sensitive.

Next drafting step

Promote only after the Global move names are clipped.

Once clips exist, this can become a final Shadow Puppeteer guide with current move names, exact cue screenshots, and weapon-specific comfort notes. Until then, the useful asset is the source-bound mechanics split: parry rows, dodge rows, add control, and retreat calls.