Update log
Full The End of History update
The complete published notes, normalized for clean reading and source attribution.
Extracted changes
- Performance
- Gameplay
- Fixes
- UI and audio
- Events
- Maps
Thank you for always playing End of History.
We had planned to deliver this letter in February — thank you for your patience, and we sincerely apologize for the delay.
As announced in the Update Roadmap on January 30, we will be delivering monthly developer letters starting in February.
This being the first issue, we will look back on the roughly two and a half months since the Early Access launch (December 10, 2025), and share our current efforts and future plans.
1.Recap of Improvements Delivered in Updates So Far
Based on your feedback, we have made the following improvements over the past two and a half months.
◆ Ensuring Stability (Addressing Crashes and Progression Blockers)
We received many stability-related reports immediately after the Early Access launch. Being able to "play stably through to the end" was our top priority, and we addressed the following issues first:
Crashes caused by the same character existing multiple times in the world
Crashes caused by diplomatic data corruption
Crashes occurring at the end of siege battles and defensive battles
Screen blackout and loss of control after combat under special conditions
Progression blocker when the protagonist dies in sandbox mode
We are continuing to investigate and fix issues in this category.
◆ Improvements to the Liege Command System
"Liege commands from vassals fail immediately," "they are issued repeatedly every day," and "impossible liege commands come from the suzerain" — these were among the most common pieces of feedback after the Early Access launch.
The liege command system in this game is designed as part of a world where NPCs live with their own will, just like the player. However, we also recognize that the intent behind this design has not been communicated well, and that it has become a source of frustration in many cases.
Key measures taken so far:
Adjustment of liege command issuance frequency and logic
Improved so that when a liege command is overwritten at the suzerain's discretion, merit points and favorability are granted based on the progress already achieved
Identified and fixed multiple causes of the bug where liege commands would fail repeatedly every day
Fixed a bug where troop training liege commands were issued with a target value exceeding the experience cap
Adjusted so that when a vassal proposes a declaration of war and is refused, they cannot propose it again for 60 days
Adjusted the maximum impression value decrease when refusing a proposal
Added a feature to display related stats for each action when issuing or receiving a liege command
It has been found that the repeating liege command failure bug is caused by multiple overlapping factors, and we are continuing to investigate and fix the remaining causes.
◆ UI / UX Improvements
UI-related feedback was consistently among the most common we received.
Key features implemented and improved:
Added conversation log viewing feature
Comprehensive Esc key behavior overhaul (consistent behavior appropriate to each situation, such as closing panels, canceling choices, and opening the save screen)
Hold Ctrl to fast-forward conversations
Event notification log feature (allows you to check what happened later)
Family tree UI implementation (check family and descendant relationships at a glance)
Notable persons filter on the map (separate display of manually marked persons and those automatically marked as close friends, etc.)
Changed world collapse level notification UI (notification frequency setting also moved to options)
Improved UI when receiving proposals from vassals (related stats displayed for each action)
Added food purchase shortcut button to granary and trading post
Adjusted display order of quest bookmarks (resolved overlap
Source
