Creator Chronicles field guide
Creator Chronicles Dungeons Guide — Dungeons, Raids & Parties
Plan Creator Chronicles dungeons and raids after launch: 19 standard dungeons, 7 raids, party sizes, preparation, rewards, and verified data needs.
Last reviewed: September 13, 2026 · Official Steam sources linked
Dungeons are no longer just a confirmed demo activity. The full Creator Chronicles release describes 19 standard dungeons and 7 high-difficulty raids, making dungeon progression one of the strongest post-launch guide areas.
What is confirmed for launch
- The full version includes 19 standard dungeons.
- The full version adds 7 large-scale raids.
- Some raids use parties of 10, 12, or up to 15 members.
- Raids can include consecutive battles and multiple major encounters.
- Dungeons have monsters, major encounters, loot, and challenge conditions.
- Griffin Landing can support automated dungeon and raid expeditions.
- Tavern visitors may bring dungeon rumors and adventure clues.
This is enough to justify a dungeon database later, but individual dungeon pages should wait for verified names, requirements, monsters, rewards, and screenshots from the released build.
How to prepare for a dungeon
- Read the entrance requirement. Record the dungeon name, unlock condition, recommended level or party constraint, and any supplies.
- Check party size and roles. Early dungeons and raids may not use the same party size.
- Review equipment and abilities. Blacksmith and Magic School progression can affect combat readiness.
- Track mood and member state. Member condition matters if the game warns about death, leaving, or long-term consequences.
- Record the result. Note drops, first-clear rewards, quest changes, unlocked buildings, and any new rumor or clue.
Current dungeon-preparation changes
Recent post-launch updates make dungeon setup more version-sensitive than early demo notes. When checking a route, verify the current Party Presets screen, because presets can now be adjusted while switching the selected dungeon.
Supplies also need current-build confirmation. The "ALL" supply option should be treated as a party-composition helper, not a blind fill-everything command: class mix can change which food or elixirs are needed, and supply requirements can affect mood checks. For raids, record how the game displays recommended Combat Power before treating a party as ready.
Dungeon database fields to collect
| Field | Use |
|---|---|
| Dungeon or raid name | Supports URL and search intent |
| Unlock requirement | Answers "how to unlock" |
| Party size | Separates early dungeon, raid, auto-run, and PvP logic |
| Enemies and major encounters | Supports combat prep |
| Drops and resources | Connects dungeon to crafting and economy |
| First-clear reward | Helps progression decisions |
| Repeat reward | Helps farming routes |
| Build/date evidence | Prevents stale or demo-only advice |
Dungeons and raids are different tasks
Standard dungeon pages should answer route, unlock, enemies, drops, and first-clear questions. Raid pages should focus on larger party composition, consecutive fights, encounter sequence, supplies, and late-game preparation. Do not merge them into one generic "dungeon activity" article once verified raid data exists.
Dungeon questions
How many dungeons are in Creator Chronicles? The full release announcement describes 19 standard dungeons.
How many raids are in the full release? The launch announcement describes 7 ultra-challenging raids.
Can this page list every dungeon reward now? Not responsibly without verified in-game data. The next update should collect dungeon names, unlocks, monsters, major encounters, loot, and build date.
Where should I go after a dungeon? Return to guild, village, crafting, and quest screens. Dungeon results can affect recruitment, resources, building upgrades, equipment, or story progress.
For connected systems, use Guild System for party and member planning and Village Development for crafting, economy, and automated expeditions.
Source-linked evidence plan
Future dungeon entries should cite the source beside the claim. Steam or a developer announcement can support broad scope, such as the number of standard dungeons or raids. A released-build screenshot should support a dungeon name, unlock condition, party size, reward, or repeated-run result. A player note without a build date should remain a lead, not a published route.
The first batch of dungeon work should prioritize pages that players actually search for or encounter early. For each candidate, collect the entrance screen, first result screen, any quest update, and the next system it unlocks. That gives the page enough information to answer "how do I enter," "what should I prepare," and "what changes after clearing" without pretending to know every late-game value.