Prince Jerian choices, endings and achievements tracker
Multiple endings and Steam achievements are confirmed features. Their requirements are not. This page shows exactly how evidence will be collected without filling the gaps with guesses.
Official evidence: Steam app 2936290 ↗. Tracker state: empty by design until the release build can be tested.
Spoiler and evidence policy
| Level | What a page may reveal | How it will be labeled |
|---|---|---|
| Level 0 | Interface help, confirmed mechanics and release facts | None |
| Level 1 | Broad political or personal consequence categories | Minor consequences |
| Level 2 | Named event outcomes or relationship changes | Story spoilers |
| Level 3 | Ending requirements, final outcomes and hidden checks | Major ending spoilers |
Search snippets and page introductions will remain spoiler-light. Any future route table will put the spoiler level before the outcome, not after it.
What consequence evidence exists now?
Official screenshots show choices beside disclosed effects on estates, Empire axes and personality values. Other screenshots present later narrative consequence reports. This confirms that decisions have visible follow-through, but it does not prove every hidden dependency or delayed outcome.

Ending tracker framework
The developer advertises multiple endings and replay value. The table below is intentionally empty of ending names and requirements until the final game is available.
| Tracker field | Current entry | Acceptance rule |
|---|---|---|
| Ending identifier | Awaiting launch verification | Name visible in the final game or credits |
| Required state | Awaiting launch verification | Reproduced route with recorded choices |
| Disqualifying state | Awaiting launch verification | Controlled comparison against a failed route |
| Build and date | Awaiting launch verification | Exact public build context recorded |
| Spoiler level | Level 3 | Warning displayed before requirements |
Achievement tracker framework
Steam currently lists achievement support, but this page does not claim an achievement list or unlock conditions before those are publicly visible and reproducible.
| Field | Current status | Evidence needed |
|---|---|---|
| Official name | Pending | Public Steam achievement record |
| Visible description | Pending | Official text, paraphrased where needed |
| Unlock condition | Pending | Direct unlock or independent reproduction |
| Missable status | Pending | Route comparison in release build |
When a route becomes publishable
- The final build must expose the event, ending or achievement.
- The claimed requirement must be reproduced or supported by a controlled comparison.
- The page must record the verification date and game build context.
- Uncertain dependencies must stay labeled as uncertain.
- A contradiction reopens the entry instead of being explained away.