Other work / Live web application
From game rules to a build you can use
I connected search, comparison and calculators around one player question: what equipment will actually meet my targets?
Open the live productPublished planning application
Build Studio · calculators · reference data
4,140 entities · 14,511 relations in the reviewed September 2026 release
Product direction · UX/UI · AI-assisted build
The problem
The strongest-looking item can still produce an invalid build.
Class and weapon compatibility, nine equipment slots, rarity limits, affix targets, sockets, gems and talents all change what is legal. The same choices then affect damage, health and energy calculations.
My design goal: keep those choices connected. A player should be able to find a valid equipment set, apply it and continue calculating without rebuilding the same setup in separate tools.
One decision loop
The product keeps the question, constraints and result visible as the player moves through the build.
Select a class and compatible weapon.
Define affix targets and a rarity ceiling.
Inspect legal sets and their meaningful differences.
Fill all nine slots, then save or share the build.
Three product decisions
Each part of the interface answers a practical question while preserving the limits behind the answer.
Build Studio combines class, weapon, slots, gems, targets and rarity rules before it presents a candidate.
Product effect Results are inspectable equipment sets, rather than plausible suggestions that may break a rule.
The search works within a budget. Its language states when a minimum is established and when the result is simply the best candidate found for the selected rarity objective within that boundary.
Product effect The interface communicates useful certainty without claiming a global optimum it has not proved.
Equipment, affixes, gems, skills, talents, loot and mechanics remain linked through structured entities and relations.
Product effect Search and filters lead back to build choices; the database is part of the workflow, not a detached wiki.
A change that mattered
The first layout made every equipment detail equally prominent. Looking at the results together exposed the problem: the interface made comparison harder than it needed to be.
Before
All nine slots, gems and target details were expanded for every result. To compare three options, the reader had to scroll through repeated information.
After
I brought the key numbers and differences into compact summaries. Equipment details stay available in a disclosure, with an explicit action to apply the chosen result.
Calculators and discovery
Editable inputs, supported examples and explicit omissions help players compare setups without hiding assumptions.
Damage Lab shows its formula, loads a supported example and withholds unsupported outputs instead of guessing.
Open Damage Lab
Loot search covers all 1,156 rows in the reviewed September 2026 release and keeps each matching source record available for inspection.
Explore LootChecking the result
I checked the complete path from setting a target to applying a result on the published product. Local checks also followed the build through saving and reloading, with all nine equipment slots and the active target preserved.
The compact comparison is a concrete improvement to the interaction. It is not presented as a measured gain in player performance or adoption.
The calculators preserve the formulas shipped in the product. This case does not claim that those formulas were independently derived or canonically validated against the game.
My role and result
I set the product direction, workflows and UX/UI, then used AI and Codex for implementation and testing.
The work connected the existing relational data and calculation logic to a clearer planning loop. I refined comparison, calculator onboarding and responsive presentation, and prepared a repeatable published release.
What I took away: a complete answer can still be difficult to use. Choosing which detail to show first mattered as much as making the calculation available.
Result. Mistfall Atlas is live as a coherent application: players can research a mechanic, find legal equipment, apply a complete loadout and test supported calculations without losing the build context.
Game artwork, names and mechanics belong to Mistfall Hunter and its rights holders. Mistfall Atlas is an independent community tool.
Applications, product work & collaborations
Tell me what people need to decide, which rules shape the answer and where the current workflow breaks down.