Choose one combat anchor
The official store confirms multiple weapon types and a fully featured spell-crafting system. Start by choosing the current in-game option you can use consistently, then judge supporting choices around that anchor.
Terms such as melee or mage are useful descriptions of intent, not proof of a fixed class system. The registered sources do not define mandatory classes or a best-in-slot path.
Original guide diagram
Build framework
Build Around a Job, Not a Tier List
Add support that solves a specific problem
Alchemy and spell crafting are confirmed systems, and official updates have adjusted both systems over time. Use them to support a concrete need visible in the live build rather than copying a launch-week template built around older behavior.
Change one element and retest. Stacking several unverified recommendations makes it impossible to tell which choice helped or whether a patch invalidated the combination.
Keep race outside the ranking until proven
Update 7 confirms Uruhan, more race-reactive dialogue and a way to change race. It does not provide the complete statistics needed to rank races for weapons, spells or co-op roles.
Choose race for the character and dialogue evidence currently visible. Treat any claimed racial optimization as unverified unless a current first-party description or reproducible live-build test supports it.
Retest after balance changes
- Use Update 8 plus Hotfix 10 as the current baseline.
- Read official changes touching perks, weapons and spells before revising a setup.
- Avoid damage values copied from an unknown build or difficulty context.
- Keep an earlier save when testing a major allocation or equipment change.
Useful frameworks, not a tier list
A weapon-led framework prioritizes reliable weapon use and only then adds magic or alchemy. A spell-led framework starts with current spell behavior and uses equipment or alchemy to cover situations the chosen spells do not answer. Both are planning methods, not claims about hidden scaling.
