Crownhold Patch 1.0.1 (August 2026)
Launch-day stability: menu parallax off, loading freezes, and the decree skip timer.
Tobias Mikula posted two Steam news items on 17 August 2026, the same calendar day Crownhold released. Together they are the v1.0.1 family. This page translates both posts into player jobs. Date and price still live on Launch Notes. Later the same week: v1.0.2 (gold prestige, monuments) and endgame improvements (Admiralty, Dominion, catapults).
What Steam wrote (v.1.0.1)
The first 1.0.1 note is short:
- Adds a setting toggle to deactivate the parallax scrolling backgrounds in menus.
- Improve loading stability.
No new workplace. No new country. No siege sandbox. If your complaint was “the title screen slides and my fan spins,” this is the patch. Open settings, kill scrolling backgrounds, then keep playing. System requirements already said the GPU line is 512 MB — a moving menu is wasted fill rate.
What Steam wrote (v1.0.1 Hotfix)
The hotfix, still dated 17 August, named two bugs:
- Fixed loading screen freezes that already worked for players on the testing branch.
- Fixed stalling decree timer when skipping a decree choice.
That second line is why this wiki now has a decrees page. Skipping a law used to pause the clock and the session’s pacing. After the hotfix, skip is a real choice. Take cheap Loyal Decree click power if the keep is still the bottleneck; skip greedier laws when the expansion banner needs wood. Troubleshooting is the tick list if your client is behind.
The testing-branch sentence matters. Mikula shipped a freeze fix to testers first, then promoted it. If you froze on launch morning and then it stopped, you probably received this hotfix without noticing the version string.
What this patch does not do
It does not add armies. It does not retune wood. It does not rename prestige tiers. Hover-box hitboxes — the loudest UX complaint in long sessions — are not named here. Demo v0.8.3 already overhauled panels and stopped camera pans from forcing tooltips; that work is older. If your upgrade list still dies when the cursor leaves the keep, that is controls, not a missing 1.0.1 checkbox.
It also does not replace how to play. Stability patches are calendars. Guides are verbs. After you update, go back to peasants, scribes, and the harbor.
Who should care
- Anyone who sat on a black or spinning load after clicking Play.
- Anyone who skipped a decree and watched the game stop asking.
- Anyone whose menu parallax made a low-spec laptop or Deck unhappy.
- Reviewers writing “bugs at launch” on 17 August without checking Steam news the same evening.
If none of those are you, you can ignore the version string and keep the walkthrough open. Crownhold is still a short incremental. A loading patch should make the short session shorter, not become the session.
Wiki pages edited to match
Troubleshooting lists the freeze and timer first. Decrees explains skip versus accept. Controls notes the parallax toggle beside hover advice. System requirements points weak GPUs at the menu setting. The review should no longer talk as if launch freezes are the forever state.
Official text lives on Steam’s Crownhold announcements hub. This page does not replace it. If a later note supersedes 1.0.1, the Updates Hub will grow another child instead of silently rewriting this one.
Update through Steam. Then play. If the load still dies, verify files, disable scrolling backgrounds, and mail [email protected] with the build. Do not download a trainer because a timer stalled; that stall had a one-line official fix.
Frequently Asked Questions
Quick answers to the most common Crownhold questions.
Is 1.0.1 new content?
No. It is a stability and settings patch: parallax toggle, loading, and a decree-timer hotfix.
Do I need the hotfix as well as 1.0.1?
Steam listed both on 17 August. Let the client update. The hotfix is the freeze-plus-timer half.
Will this fix hover boxes?
Not named in 1.0.1. Use the controls page. Demo v0.8.3 already changed pan-and-tooltip behavior.