Core Keeper GuidesGuides, database, map tools, and update pages
Weapons entry

Scarlet Sword Route

Scarlet Sword Route: use the right page before the route turns messy.

Scarlet Sword Route is a practical Core Keeper database entry for players who need to decide where it fits, when to use it, and which deeper page should come next.

Database entries answer the first practical question. Once that answer is clear, the linked full page should take over.

Best linked page

Open Build Planner

WeaponsAug 2026weapons / database / route

Player problem

Use this when the first outer-biome weapon jump needs a clear ore and boss-timing check.

Where to use this

Use this entry after the name or system is clear, but before spending a full session on the wrong route.

What you need first

A known save stage, one current blocker, and enough inventory or base space to act on the next page.

Next click

Use this entry to decide where the next click should go.

Database fields

Use these fields like a quick lookup before opening the longer guide.

Weapons

Damage Type

Melee

Weapons

Best Stage

Outer biomes

Weapons

Best Boss

Current target boss

Weapons

Pairs With

Recovery food, armor tier, boss prep checker

Weapons

Mistakes

Swapping weapons after a wipe before checking arena, food, and reset path.

How to use this entry

Use this page to narrow the task, then move into one stronger route page.

Treat Scarlet as a stage decision, not just a bigger number.

  • Turning a named object or system into one useful next action.
  • Checking whether the page belongs to the current save stage.
  • Avoiding a broad search when a database handoff can narrow the route first.
Open Build PlannerBack to Weapons

Common mistakes

  • Opening several broad guides before naming the actual blocker.
  • Treating the entry as a definition instead of a route decision.
  • Skipping the linked next page after the database entry already narrowed the problem.

Visual cue

Scarlet Sword Route visual

Tags

weaponsdatabaseroute

Related entries

Open another entry only when the question actually changed.