Update 17: combat and progression changed

Enemies were made more accurate and retuned to compensate. The patch also rebalanced the contribution of Armor skill and the attributes awarded per skill level. HP is no longer awarded simply for gaining a character level. An older build recommendation may therefore feel different even when its named perks still exist.

Armor damage reduction is capped at 85%. That is not an armor-rating target, and the note does not establish the rating formula, best equipment combination or a damage-per-second ranking. Test the encounter and displayed stats on your own build before committing to older assumptions.

Update 17 impact on this plan

CheckReview result
Combat changed?Yes: enemy accuracy and balance
Armor scaling changed?Yes: skill contribution and 85% DR cap
Progression changed?Yes: attributes and HP
Controls relevant?Yes: quick slots and weapon/spell switching
Exact formula known?No; this plan does not calculate DPS or effective health

Changed in Update 17

This page was compared with the official Update 17 announcement on September 25, 2026. The changes above are developer-reported; details requiring in-game testing remain explicitly unresolved.

Core priorities

  • 1. Lockpicking — primary identity.
  • 2. Pickpocket — supporting plan.
  • 3. Sneak — flex slot.

Verified perk seeds

These names appear in the official Update 15 record. They are decision prompts, not a copied or invented requirement tree.

  • Locksmith's Eye
  • Fence
  • Deep Pockets

Early, mid and late priorities

StagePriorityExit check
EarlyMake Lockpicking reliable before spreading points.The core action works in ordinary encounters without a fragile setup.
MidAdd Pickpocket to solve the clearest resource or survival problem.The supporting choice fixes a problem you can reproduce.
LateEvaluate Deep Pockets against its current in-game text.Requirements and tradeoffs have been checked in the live Update 17 menu.

Weapons, spells and armor

Use the current weapon or spell that directly trains Lockpicking; this guide does not invent a mandatory named item. Choose armor by the defense and resource pressure visible in your own save, then change one slot at a time.

For weapon-led play, record weapon family, current skill and the exact equipped bonus before comparing outcomes.

Practical play pattern

Start with the part of the thief identity you can use in every encounter. Add the supporting skill only after the first loop feels reliable, then keep the flex slot for the problem your current save actually has.

Because Early Access balance changes quickly, spend against current in-game text instead of an old screenshot or undated tier list.

Strengths and weaknesses

StrengthWeakness
A clear thief identity keeps early decisions focused.The path cannot guarantee performance against every enemy or difficulty.
Verified perk names make the next in-game checks easy to find.Patch notes do not publish complete prerequisites or measured output.
A flex skill can answer the current save's real problem.Spreading into too many systems can delay the core loop.

Co-op role

Bring a reliable thief loop rather than assuming a formal class role. Update 16 preserves supported guest character growth, while quests and quest items remain host-side.

Alternatives

  • Swap Pickpocket for Armor or Running when survival or positioning is the actual constraint.
  • Use the exploration path when access and gathering matter more than combat specialization.
  • Use the co-op support path when party visibility and repeatable utility matter more than solo pressure.

Update-sensitive notes

Update 15 is the perk baseline for this guide. Update 17 is the current site baseline; Update 17 changes controls, combat, armor, progression and alchemy. Recheck this page after any patch that changes perks, equipment, magic or character saves.

Before spending a perk point

  • Read the current requirement and rank text in game.
  • Check whether the perk changes a resource, weapon family or multiplayer behavior.
  • Make a manual save before using grantperk or removeperk.
  • Ownership, witness and disposition formulas remain outside the verified record.

Evidence boundary

Exact values, requirements and edge cases stay marked as unverified until they can be checked in the current build.