GET YOUR BEARINGS
Plan your next Bloodstained: Curse of the Moon 2 session
Our independent guide expands on Bloodstained: Curse of the Moon 2 by offering focused observations on narrative flow, character variety, co‑op dynamics and Steam integrations. Use the exercises below to compare documented elements and refine your approach without relying on undocumented shortcuts.
01 / THE GUIDE
Narrative Flow
Play the opening scenario, then the second, noting how Zangetsu’s vendetta against demons progresses. Compare pacing, dialogue cues and visual changes to understand the story’s incremental development.
- Observe how each scenario introduces new enemy designs that echo the demonic theme.
- Compare the visual palette of this sequel with the original to notice aesthetic refinements.
02 / THE GUIDE
Hero Ability Contrast
Select Zangetsu for one level and Dominique for the next. Record observable differences in attack range, movement speed and any stage interactions that appear unique to each hero.
- Swap heroes between scenarios to discover each character’s unique moves.
- Note which pairings feel complementary for later two‑player sessions.
03 / THE GUIDE
Co‑op Role Balance
Team up with a partner, each choosing a contrasting hero (e.g., melee‑focused vs. ranged). Observe how their abilities combine to overcome a challenging enemy pattern or platforming segment.
- Coordinate character choices with your teammate to balance offense and defense.
- Try both shared and split screen to see which view best suits your teamwork.
04 / THE GUIDE
Achievement Mapping
List all Steam achievements, then match each to an in‑game event or milestone you encounter. This helps prioritize which stages or actions to target for a complete achievement set.
- Review the achievement list early to set personal milestones.
- Use Remote Play Together if a second controller is unavailable.
05 / THE GUIDE
Controller Compatibility Check
Connect a supported controller and play a short segment, noting any actions that do not respond. Replay the same segment using the default input method to gauge the extent of controller coverage.
- Test a compatible controller at the start of a session to identify mapped actions.
- If a function feels unmapped, switch to the default input method for that action.
