KCD2 rewards preparation more than animation canceling. Henry starts competent but not heroic, so an early build should cover defence, stamina, and one reliable weapon rather than a little of everything.
Deliverance II — A Reliable Early Build and Save Policy
Verified field fixThe shortest safe order for this issue:
- Prioritise the basic combat perks before spreading skill points across every tree.
- Use Saviour Schnapps deliberately and keep a manual backup before story branches.
- Tune the crosshair and camera sensitivity before training with Bernard.
Build a baseline, not a meme
Take the defensive and stamina perks that keep Henry alive through a long fight. Choose one weapon family and practise its master strike timing. A second weapon is a tool, not a stat sink. Keep armour weight in a range that still allows a useful dodge.
$game = Join-Path $env:USERPROFILE "Saved Games/kingdomcome2"
$backup = Join-Path $env:USERPROFILE "Desktop/KCD2-save-backup"
Copy-Item $game $backup -Recurse -Force
Get-ChildItem $backup/saves -File | Sort-Object LastWriteTime -Descending | Select-Object -First 5 Save deliberately
The save system is part of the build. Before a story branch, a difficult ambush, or a long trek, make a manual backup of the local save folder. Saviour Schnapps is a resource; treating every fight as a restart is not a strategy.
Field notes before you change the build
A Kingdom Come: Deliverance II build is a testable plan, not a screenshot of someone else’s final character. State the patch, the encounter, and the resource budget the plan assumes. If those change, the build is a new hypothesis.
Practise the same encounter and change one ability, item, or upgrade tier. A route or build that only works with perfect execution is not a reliable recommendation, especially in a CryEngine game with variable enemy behaviour.
- Do not spread upgrades across every tree before the core loop is stable.
- Do not copy a build without checking its patch version and resource costs.
- Do not judge a change from one lucky encounter or a highlight clip.
Check it before you keep it
Train one weapon and one defensive response before the next story fight
0 / 5 completeBuild for repeatability
Write down the assumptions, test the same scenario, and keep the version that produces fewer panic decisions. That is the build you can actually use.
The line to keep
A good Henry is alive, fed, and able to finish a fight. Build toward that before chasing a perfect endgame stat sheet.
Did this fix work on Patch 1.5.2 — combat and save fixes?
One click. No account. Your vote is stored in this browser and de-duplicated per file.
Verified against 1.5.2 — combat and save fixes. Votes are local-only telemetry.
Kingdom Come: Deliverance II: bench questions
2 answersShould I spread perks across all weapon types?
How often should I back up a save?
Walkthrough & Builds
This field file was tested against the patch context above. If a launcher update changed your menu labels, include the exact build number in a report to the desk.
Kingdom Come: Deliverance II: CTD, DXGI_ERROR_DEVICE_HUNG & Black-Screen Launch Fixes
Stabilise Kingdom Come: Deliverance II on PC: diagnose crash-to-desktop loops, DXGI device-hung resets, black-screen starts, and anti-cheat or DLL launch blocks on CryEngine.
Kingdom Come: Deliverance II: Shader Stutter, Frame Pacing & CryEngine Config Tuning
A measured stutter-hunting routine for Kingdom Come: Deliverance II: shader compilation warm-up, frame-pacing limits, upscaler presets, and the exact CryEngine settings file to edit.
Kingdom Come: Deliverance II: Safe Mod Install, Load Order & Post-Patch Conflict Recovery
Install mods on Kingdom Come: Deliverance II without breaking the build: framework order, script conflicts after a patch, and a clean rollback path that keeps your saves intact.