Skip to main content

Build as projection

Why an attribute allocation is a persona a player projects onto the game, and what "no dead points" actually requires of a stat system

Ask a player why they put points into faith instead of strength and the honest answer is rarely a DPS calculation. It’s closer to: this is who I am in this world. A Souls-like’s attribute system is legible enough — few enough numbers, visible enough thresholds — that the allocation itself becomes readable as a character choice, the way a tabletop character sheet is a character choice before it’s ever a combat statistic.

That only works if the system genuinely has “no dead points” — every stat has to buy something a build can actually be built around, not just a diminishing-returns tax on players who didn’t read a wiki. A stat that’s strictly worse than another in every build isn’t a persona option, it’s a trap the system pretends is a choice. The test this course keeps returning to applies here too: a build that fails because the player misjudged a genuine trade-off is a legible failure; a build that fails because one attribute was quietly worse in every configuration is the arbitrary case wearing a character sheet.

An alternative build — Sekiro’s pure-prosthetic-tool run, a faith-only caster who never swings a melee weapon — is the sharpest test of this, because it commits to a persona a min-maxed build wouldn’t and accepts a real, nameable cost for it. The pitch for a build like that isn’t “this is secretly optimal”; it’s “this is who you’d be if you played this way,” and a system that can support that pitch honestly is doing more work than its damage-per-second numbers suggest.