Use row 1 and the source trail to decide whether to continue, detour or delay it.
Avoid: Do not assume Cornifer works like another game's category.Hollow Knight · Wiki
Hollow Knight NPCs: understand vendor, quest and ending signals
Use this page when you need understand vendor, quest and ending signals instead of another generic Hollow Knight article.
Primary sections
Start with your problem
Players lose time in Hollow Knight when npcs advice is not tied to unlocks, route state, patch state and source evidence.
NPCs now has a source-backed checklist, entity table and decision flow focused on understand vendor, quest and ending signals.
Use row 2 and the source trail to decide whether to continue, detour or delay it.
Avoid: Do not assume Iselda works like another game's category.Use row 3 and the source trail to decide whether to continue, detour or delay it.
Avoid: Do not assume Sly works like another game's category.Use row 4 and the source trail to decide whether to continue, detour or delay it.
Avoid: Do not assume Seer works like another game's category.Problem solver
NPCs quick diagnosis
Pick the current player state, then use the table and sources before making route changes.
Cornifer is unclear
Cornifer needs a source-backed route check.
Use row 1 and the source trail to decide whether to continue, detour or delay it.
Do not: Do not assume Cornifer works like another game's category. Then compare with Iselda.Iselda is unclear
Iselda needs a source-backed route check.
Use row 2 and the source trail to decide whether to continue, detour or delay it.
Do not: Do not assume Iselda works like another game's category. Then compare with Sly.Sly is unclear
Sly needs a source-backed route check.
Use row 3 and the source trail to decide whether to continue, detour or delay it.
Do not: Do not assume Sly works like another game's category. Then compare with Seer.Seer is unclear
Seer needs a source-backed route check.
Use row 4 and the source trail to decide whether to continue, detour or delay it.
Do not: Do not assume Seer works like another game's category. Then compare with Nailsmith.Playable tools
Use this while planning your route
These tools turn the guide into a quick decision surface for boss attempts, builds, quests and backups.
Decision tool
NPCs state picker
Choose the state that matches your current Hollow Knight save.
Choose the current state to get the next action.
Video
Hollow Knight official media reference
Use official Steam and publisher media as the video/source anchor while page-specific clips are collected.
Open official Steam mediaStructured data
Real entries to check while playing
These tables turn the page into a working reference instead of a text-only article. Exact values should stay tied to the source trail and update date.
Database
NPCs source-backed facts
| Entry | Type | Where it matters | Player use | Risk | Next action | Verification | Sources |
|---|---|---|---|---|---|---|---|
| Cornifer | npc | NPCs / Hollow Knight | Use this npc entry when the player is trying to understand vendor, quest and ending signals. | Cornifer is risky when it is copied without checking route state, patch state or unlock state. | Open NPCs, verify Cornifer, then make one in-game change before comparing results. | source-backed fact high confidence 2026-05-12 | Hollow Knight Wiki: Grimm TroupeHollow Knight Wiki: IseldaHollow Knight Wiki: Dreamers |
| Iselda | npc | NPCs / Hollow Knight | Use this npc entry when the player is trying to understand vendor, quest and ending signals. | Iselda is risky when it is copied without checking route state, patch state or unlock state. | Open NPCs, verify Iselda, then make one in-game change before comparing results. | source-backed fact high confidence 2026-05-12 | Hollow Knight Wiki: IseldaHollow Knight Wiki: DreamersHollow Knight Wiki: Grimm Troupe |
| Sly | npc | NPCs / Hollow Knight | Use this npc entry when the player is trying to understand vendor, quest and ending signals. | Sly is risky when it is copied without checking route state, patch state or unlock state. | Open NPCs, verify Sly, then make one in-game change before comparing results. | source-backed fact high confidence 2026-05-12 | Hollow Knight Wiki: DreamersHollow Knight Wiki: Grimm TroupeHollow Knight Wiki: Iselda |
| Seer | npc | NPCs / Hollow Knight | Use this npc entry when the player is trying to understand vendor, quest and ending signals. | Seer is risky when it is copied without checking route state, patch state or unlock state. | Open NPCs, verify Seer, then make one in-game change before comparing results. | source-backed fact high confidence 2026-05-12 | Hollow Knight Wiki: Grimm TroupeHollow Knight Wiki: IseldaHollow Knight Wiki: Dreamers |
| Nailsmith | npc | NPCs / Hollow Knight | Use this npc entry when the player is trying to understand vendor, quest and ending signals. | Nailsmith is risky when it is copied without checking route state, patch state or unlock state. | Open NPCs, verify Nailsmith, then make one in-game change before comparing results. | source-backed fact high confidence 2026-05-12 | Hollow Knight Wiki: IseldaHollow Knight Wiki: DreamersHollow Knight Wiki: Grimm Troupe |
| Grimm Troupe | npc | NPCs / Hollow Knight | Use this npc entry when the player is trying to understand vendor, quest and ending signals. | Grimm Troupe is risky when it is copied without checking route state, patch state or unlock state. | Open NPCs, verify Grimm Troupe, then make one in-game change before comparing results. | source-backed fact high confidence 2026-05-12 | Hollow Knight Wiki: DreamersHollow Knight Wiki: Grimm TroupeHollow Knight Wiki: Iselda |
| Dreamers | npc | NPCs / Hollow Knight | Use this npc entry when the player is trying to understand vendor, quest and ending signals. | Dreamers is risky when it is copied without checking route state, patch state or unlock state. | Open NPCs, verify Dreamers, then make one in-game change before comparing results. | source-backed fact high confidence 2026-05-12 | Hollow Knight Wiki: Grimm TroupeHollow Knight Wiki: IseldaHollow Knight Wiki: Dreamers |
Database
NPCs decision checks
| Entry | Stage | Decision | Action | Avoid | Next | Verification | Sources |
|---|---|---|---|---|---|---|---|
| Cornifer | 1. NPCs decision | Treat Cornifer as the current checkpoint for understand vendor, quest and ending signals. | Check the linked source trail, then record whether Cornifer is unlocked, skipped or blocked in the save. | Do not force Cornifer into another game's framework or publish it without source-backed context. | Move to Iselda after this checkpoint is resolved. | source-backed fact high confidence 2026-05-12 | Hollow Knight Wiki: Grimm TroupeHollow Knight Wiki: IseldaHollow Knight Wiki: Dreamers |
| Iselda | 2. NPCs decision | Treat Iselda as the current checkpoint for understand vendor, quest and ending signals. | Check the linked source trail, then record whether Iselda is unlocked, skipped or blocked in the save. | Do not force Iselda into another game's framework or publish it without source-backed context. | Move to Sly after this checkpoint is resolved. | source-backed fact high confidence 2026-05-12 | Hollow Knight Wiki: IseldaHollow Knight Wiki: DreamersHollow Knight Wiki: Grimm Troupe |
| Sly | 3. NPCs decision | Treat Sly as the current checkpoint for understand vendor, quest and ending signals. | Check the linked source trail, then record whether Sly is unlocked, skipped or blocked in the save. | Do not force Sly into another game's framework or publish it without source-backed context. | Move to Seer after this checkpoint is resolved. | source-backed fact high confidence 2026-05-12 | Hollow Knight Wiki: DreamersHollow Knight Wiki: Grimm TroupeHollow Knight Wiki: Iselda |
| Seer | 4. NPCs decision | Treat Seer as the current checkpoint for understand vendor, quest and ending signals. | Check the linked source trail, then record whether Seer is unlocked, skipped or blocked in the save. | Do not force Seer into another game's framework or publish it without source-backed context. | Move to Nailsmith after this checkpoint is resolved. | source-backed fact high confidence 2026-05-12 | Hollow Knight Wiki: Grimm TroupeHollow Knight Wiki: IseldaHollow Knight Wiki: Dreamers |
| Nailsmith | 5. NPCs decision | Treat Nailsmith as the current checkpoint for understand vendor, quest and ending signals. | Check the linked source trail, then record whether Nailsmith is unlocked, skipped or blocked in the save. | Do not force Nailsmith into another game's framework or publish it without source-backed context. | Move to Grimm Troupe after this checkpoint is resolved. | source-backed fact high confidence 2026-05-12 | Hollow Knight Wiki: IseldaHollow Knight Wiki: DreamersHollow Knight Wiki: Grimm Troupe |
| Grimm Troupe | 6. NPCs decision | Treat Grimm Troupe as the current checkpoint for understand vendor, quest and ending signals. | Check the linked source trail, then record whether Grimm Troupe is unlocked, skipped or blocked in the save. | Do not force Grimm Troupe into another game's framework or publish it without source-backed context. | Move to Dreamers after this checkpoint is resolved. | source-backed fact high confidence 2026-05-12 | Hollow Knight Wiki: DreamersHollow Knight Wiki: Grimm TroupeHollow Knight Wiki: Iselda |
| Dreamers | 7. NPCs decision | Treat Dreamers as the current checkpoint for understand vendor, quest and ending signals. | Check the linked source trail, then record whether Dreamers is unlocked, skipped or blocked in the save. | Do not force Dreamers into another game's framework or publish it without source-backed context. | Move to Cornifer after this checkpoint is resolved. | source-backed fact high confidence 2026-05-12 | Hollow Knight Wiki: Grimm TroupeHollow Knight Wiki: IseldaHollow Knight Wiki: Dreamers |
Player problem
Players lose time in Hollow Knight when npcs advice is not tied to unlocks, route state, patch state and source evidence.
NPCs now has a source-backed checklist, entity table and decision flow focused on understand vendor, quest and ending signals.
NPCs starts with the current blocker
The page is built around understand vendor, quest and ending signals, so the player can act before reading every row.
- Identify which of the first three entries matches the save.
- Check whether the source trail confirms the route.
- Do one change, then return to the table if the blocker remains.
What to verify before changing the route
Hollow Knight routes can break when unlocks, DLC, patches or mods are assumed instead of verified.
- Confirm Cornifer is available.
- Compare Iselda with the current player goal.
- Mark Sly as done, blocked or skipped.
How this page should be expanded next
The current standard is source-backed and useful, but future updates should add screenshots, route clips and deeper per-entry notes.
- Add one image for each high-volume player problem.
- Attach update notes when a patch changes NPCs.
- Keep unsafe or cheat-like instructions out of the page.
NPCs player decision table
| Current problem | Use this entry | Next action |
|---|---|---|
| Hollow Knight player is stuck on Cornifer | NPCs row 1: verify Cornifer against the source trail | Record whether Cornifer is done, blocked or not relevant before moving on |
| Hollow Knight player is stuck on Iselda | NPCs row 2: verify Iselda against the source trail | Record whether Iselda is done, blocked or not relevant before moving on |
| Hollow Knight player is stuck on Sly | NPCs row 3: verify Sly against the source trail | Record whether Sly is done, blocked or not relevant before moving on |
| Hollow Knight player is stuck on Seer | NPCs row 4: verify Seer against the source trail | Record whether Seer is done, blocked or not relevant before moving on |
Action checklist
Do this in order
- Open the NPCs source trail before changing the save.
- Mark the relevant Hollow Knight entry from the structured table.
- Check whether patches, DLC or mods change this route.
- Make one in-game change, then test it for one session.
- Update the page if a source contradicts the current row.
FAQ
Common questions
Is this npcs page beginner-safe?
Yes. It starts with practical route checks and keeps spoiler-heavy details in named rows.
Why are sources shown on every page?
Players need to verify patch-sensitive facts instead of trusting stale summary text.
What should be added next?
More screenshots, short route clips and deeper per-entry notes for the highest-volume problems.
Sources