Use row 1 and the source trail to decide whether to continue, detour or delay it.
Avoid: Do not assume Dreamers works like another game's category.Hollow Knight · Wiki
Hollow Knight Lore Entries: separate optional lore from progression blockers
Use this page when you need separate optional lore from progression blockers instead of another generic Hollow Knight article.
Primary sections
Start with your problem
Players lose time in Hollow Knight when lore entries advice is not tied to unlocks, route state, patch state and source evidence.
Lore Entries now has a source-backed checklist, entity table and decision flow focused on separate optional lore from progression blockers.
Use row 2 and the source trail to decide whether to continue, detour or delay it.
Avoid: Do not assume Kingdom history 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 Void clues 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 Grimm Troupe lore works like another game's category.Problem solver
Lore Entries quick diagnosis
Pick the current player state, then use the table and sources before making route changes.
Dreamers is unclear
Dreamers 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 Dreamers works like another game's category. Then compare with Kingdom history.Kingdom history is unclear
Kingdom history 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 Kingdom history works like another game's category. Then compare with Void clues.Void clues is unclear
Void clues 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 Void clues works like another game's category. Then compare with Grimm Troupe lore.Grimm Troupe lore is unclear
Grimm Troupe lore 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 Grimm Troupe lore works like another game's category. Then compare with Godhome lore.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
Lore Entries 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
Lore Entries source-backed facts
| Entry | Type | Where it matters | Player use | Risk | Next action | Verification | Sources |
|---|---|---|---|---|---|---|---|
| Dreamers | lore | Lore Entries / Hollow Knight | Use this lore entry when the player is trying to separate optional lore from progression blockers. | Dreamers is risky when it is copied without checking route state, patch state or unlock state. | Open Lore Entries, verify Dreamers, then make one in-game change before comparing results. | source-backed fact high confidence 2026-05-12 | Hollow Knight Wiki: DreamersHollow Knight Wiki: EndingsHollow Knight Wiki: Areas |
| Kingdom history | lore | Lore Entries / Hollow Knight | Use this lore entry when the player is trying to separate optional lore from progression blockers. | Kingdom history is risky when it is copied without checking route state, patch state or unlock state. | Open Lore Entries, verify Kingdom history, then make one in-game change before comparing results. | source-backed fact high confidence 2026-05-12 | Hollow Knight Wiki: EndingsHollow Knight Wiki: AreasHollow Knight Wiki: Dreamers |
| Void clues | lore | Lore Entries / Hollow Knight | Use this lore entry when the player is trying to separate optional lore from progression blockers. | Void clues is risky when it is copied without checking route state, patch state or unlock state. | Open Lore Entries, verify Void clues, then make one in-game change before comparing results. | source-backed fact high confidence 2026-05-12 | Hollow Knight Wiki: AreasHollow Knight Wiki: DreamersHollow Knight Wiki: Endings |
| Grimm Troupe lore | lore | Lore Entries / Hollow Knight | Use this lore entry when the player is trying to separate optional lore from progression blockers. | Grimm Troupe lore is risky when it is copied without checking route state, patch state or unlock state. | Open Lore Entries, verify Grimm Troupe lore, then make one in-game change before comparing results. | source-backed fact high confidence 2026-05-12 | Hollow Knight Wiki: DreamersHollow Knight Wiki: EndingsHollow Knight Wiki: Areas |
| Godhome lore | lore | Lore Entries / Hollow Knight | Use this lore entry when the player is trying to separate optional lore from progression blockers. | Godhome lore is risky when it is copied without checking route state, patch state or unlock state. | Open Lore Entries, verify Godhome lore, then make one in-game change before comparing results. | source-backed fact high confidence 2026-05-12 | Hollow Knight Wiki: EndingsHollow Knight Wiki: AreasHollow Knight Wiki: Dreamers |
| Hunter notes | lore | Lore Entries / Hollow Knight | Use this lore entry when the player is trying to separate optional lore from progression blockers. | Hunter notes is risky when it is copied without checking route state, patch state or unlock state. | Open Lore Entries, verify Hunter notes, then make one in-game change before comparing results. | source-backed fact high confidence 2026-05-12 | Hollow Knight Wiki: AreasHollow Knight Wiki: DreamersHollow Knight Wiki: Endings |
| tablet rooms | lore | Lore Entries / Hollow Knight | Use this lore entry when the player is trying to separate optional lore from progression blockers. | tablet rooms is risky when it is copied without checking route state, patch state or unlock state. | Open Lore Entries, verify tablet rooms, then make one in-game change before comparing results. | source-backed fact high confidence 2026-05-12 | Hollow Knight Wiki: DreamersHollow Knight Wiki: EndingsHollow Knight Wiki: Areas |
Database
Lore Entries decision checks
| Entry | Stage | Decision | Action | Avoid | Next | Verification | Sources |
|---|---|---|---|---|---|---|---|
| Dreamers | 1. Lore Entries decision | Treat Dreamers as the current checkpoint for separate optional lore from progression blockers. | 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 Kingdom history after this checkpoint is resolved. | source-backed fact high confidence 2026-05-12 | Hollow Knight Wiki: DreamersHollow Knight Wiki: EndingsHollow Knight Wiki: Areas |
| Kingdom history | 2. Lore Entries decision | Treat Kingdom history as the current checkpoint for separate optional lore from progression blockers. | Check the linked source trail, then record whether Kingdom history is unlocked, skipped or blocked in the save. | Do not force Kingdom history into another game's framework or publish it without source-backed context. | Move to Void clues after this checkpoint is resolved. | source-backed fact high confidence 2026-05-12 | Hollow Knight Wiki: EndingsHollow Knight Wiki: AreasHollow Knight Wiki: Dreamers |
| Void clues | 3. Lore Entries decision | Treat Void clues as the current checkpoint for separate optional lore from progression blockers. | Check the linked source trail, then record whether Void clues is unlocked, skipped or blocked in the save. | Do not force Void clues into another game's framework or publish it without source-backed context. | Move to Grimm Troupe lore after this checkpoint is resolved. | source-backed fact high confidence 2026-05-12 | Hollow Knight Wiki: AreasHollow Knight Wiki: DreamersHollow Knight Wiki: Endings |
| Grimm Troupe lore | 4. Lore Entries decision | Treat Grimm Troupe lore as the current checkpoint for separate optional lore from progression blockers. | Check the linked source trail, then record whether Grimm Troupe lore is unlocked, skipped or blocked in the save. | Do not force Grimm Troupe lore into another game's framework or publish it without source-backed context. | Move to Godhome lore after this checkpoint is resolved. | source-backed fact high confidence 2026-05-12 | Hollow Knight Wiki: DreamersHollow Knight Wiki: EndingsHollow Knight Wiki: Areas |
| Godhome lore | 5. Lore Entries decision | Treat Godhome lore as the current checkpoint for separate optional lore from progression blockers. | Check the linked source trail, then record whether Godhome lore is unlocked, skipped or blocked in the save. | Do not force Godhome lore into another game's framework or publish it without source-backed context. | Move to Hunter notes after this checkpoint is resolved. | source-backed fact high confidence 2026-05-12 | Hollow Knight Wiki: EndingsHollow Knight Wiki: AreasHollow Knight Wiki: Dreamers |
| Hunter notes | 6. Lore Entries decision | Treat Hunter notes as the current checkpoint for separate optional lore from progression blockers. | Check the linked source trail, then record whether Hunter notes is unlocked, skipped or blocked in the save. | Do not force Hunter notes into another game's framework or publish it without source-backed context. | Move to tablet rooms after this checkpoint is resolved. | source-backed fact high confidence 2026-05-12 | Hollow Knight Wiki: AreasHollow Knight Wiki: DreamersHollow Knight Wiki: Endings |
| tablet rooms | 7. Lore Entries decision | Treat tablet rooms as the current checkpoint for separate optional lore from progression blockers. | Check the linked source trail, then record whether tablet rooms is unlocked, skipped or blocked in the save. | Do not force tablet rooms 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: EndingsHollow Knight Wiki: Areas |
Player problem
Players lose time in Hollow Knight when lore entries advice is not tied to unlocks, route state, patch state and source evidence.
Lore Entries now has a source-backed checklist, entity table and decision flow focused on separate optional lore from progression blockers.
Lore Entries starts with the current blocker
The page is built around separate optional lore from progression blockers, 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 Dreamers is available.
- Compare Kingdom history with the current player goal.
- Mark Void clues 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 Lore Entries.
- Keep unsafe or cheat-like instructions out of the page.
Lore Entries player decision table
| Current problem | Use this entry | Next action |
|---|---|---|
| Hollow Knight player is stuck on Dreamers | Lore Entries row 1: verify Dreamers against the source trail | Record whether Dreamers is done, blocked or not relevant before moving on |
| Hollow Knight player is stuck on Kingdom history | Lore Entries row 2: verify Kingdom history against the source trail | Record whether Kingdom history is done, blocked or not relevant before moving on |
| Hollow Knight player is stuck on Void clues | Lore Entries row 3: verify Void clues against the source trail | Record whether Void clues is done, blocked or not relevant before moving on |
| Hollow Knight player is stuck on Grimm Troupe lore | Lore Entries row 4: verify Grimm Troupe lore against the source trail | Record whether Grimm Troupe lore is done, blocked or not relevant before moving on |
Action checklist
Do this in order
- Open the Lore Entries 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 lore entries 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