Endings and Difficulty in Creator Chronicles

The full build of Creator Chronicles holds three different endings. They are not locked behind difficulty alone; each ending requires you to fulfill specific conditions during your chronicle. This page explains the ending structure, what gates each conclusion, and how difficulty interacts with the conditions you meet on the way.

The campaign is single-player. Endings play out as story sequences after the final battle, not as a choose-your-own-credits screen. The three endings are: the Developer Ending, the Guild Master Ending, and the True Ending.

The three endings

Developer Ending — The default conclusion if you reach the final battle without meeting special conditions. The trapped developer returns to the real world, leaving the guild behind. This ending is accessible on any difficulty.

Guild Master Ending — Requires you to build the village to a high level and maintain a roster of at least 12 members with high mood. The developer chooses to stay in the game world as a guild member rather than return to reality.

True Ending — Requires the Guild Master Ending conditions plus: all seven ultra-challenging raids completed, at least one member with Master-enchanted equipment, and a party that cleared the final battle without any deaths. This is the longest conclusion and shows the full story resolution.

Difficulty and endings

Difficulty affects conditions but not ending access directly. Beginner and Adventurer players can reach any ending; the conditions are more forgiving on lower difficulty because member death and mood penalties are less punishing.

Conqueror difficulty makes the True Ending significantly harder. A single death in the final battle disqualifies the True Ending on any difficulty, but on Conqueror keeping your party alive through seven raids plus the final battle requires more planning than on Adventurer.

Difficulty does not change which ending you get based on story choices alone. It changes how much roster management you must do to keep the conditions met. A Conqueror player pursuing the True Ending needs a functioning mood management system, backup members for each role, and gear strong enough to survive 7 raids without a single death.

Conditions in practice

Track your ending progress as you would a village trait point. The conditions are:

For Developer Ending:

• Reach the final battle. Any village level, any roster, any difficulty.

For Guild Master Ending:

• Village level 15 or higher
• 12 or more members, all with mood above the quit threshold
• At least 2 members in each combat role (tank, healer, DPS)
• Final battle reached on Adventurer or higher

For True Ending:

• All Guild Master Ending conditions
• Seven ultra-challenging raids completed
• At least one member wearing Master-enchanted equipment
• Zero deaths in the final battle

How to prepare for each ending

Developer Ending requires no special preparation. Run dungeons, level your village, reach the final battle. It is the floor, not a failure state.

Guild Master Ending requires active mood management. Keep food stocked, avoid wipes on Conqueror, and maintain a roster above 12. The Tavern in the full build gives you a conversation tool to manage mood before it becomes a quit risk. See mood for the mechanics.

True Ending requires the longest investment. Start preparing by the time you clear Raid 3: maintain a raid-ready party with crafted and enchanted gear, keep backup members in case of death, and practice the final battle composition on Adventurer before attempting it on Conqueror.

Endings and the save system

The full build offers five save slots. Use one slot for your main chronicle, one for a Conqueror attempt at the True Ending, and keep the others for experimenting with different party compositions. The party planner and party tier list help you maintain multiple raid-ready crews.

Demo saves do not carry over. Demo-era progress cannot contribute to any ending condition in the 14 September 2026 build. See launch notes for what the full client adds on day one.