Building a Daggerheart Summoner: What the Vestige Binder and Totemist Got Right
Three Old-School Mechanics That Could Shape Daggerheart’s Summoner
Daggerheart, the TTRPG from Darrington Press built on a Hope/Fear dice system rather than a d20, has been running open playtests — and a Summoner class is exactly the kind of design problem where older D&D subsystems have something real to offer. The combination of the 2nd Edition Shaman, the 3.5e Binder, and the Incarnum Totemist isn’t random nostalgia. Each class solved a different piece of the summoner puzzle, and looking at them together points toward a coherent structure for what a Daggerheart Summoner could become.
What each legacy class actually did
The 3.5e Binder, introduced in Tome of Magic, let players bind vestiges — echoes of beings too strange or powerful for conventional summoning — and gain their abilities for the day. The core loop was slow: you bound at the start of a session, locking your power set early. What made it memorable was the influence mechanic. Vestiges tugged at your behavior, and resisting that pull was its own resource management game running in parallel with whatever you were fighting.
The Totemist from Magic of Incarnum worked differently. Soulmelds were shaped and then slotted into chakra binds for stronger effects. You could reshape on a rest, but mid-combat you were committed. Less commanding creatures, more wearing their essence. Very different fiction from a traditional summoner, but deeply flavorful and surprisingly tactical.
The 2e Shaman sat closer to a divine caster who brokered deals with spirits. The mechanics were lighter on interlocking resource pools and heavier on fictional positioning: spirits had relationships, moods, and demands that shaped play at the table as much as any stat block did.
The essence-upgrade idea is the real departure
What the design concept describes — spending essence at summon-time to unlock upgrades like better natural armor or enhanced attacks — is a significant departure from all three source systems. None of them let you dynamically tune a summoned creature on the fly this way. It’s closest in spirit to Pathfinder 1e’s Eidolon evolution system, or to how a Pact of the Chain warlock in 5e customizes their familiar, but with a point-buy customization layer applied fresh each time you summon.
This is the most interesting piece of the design. A power-point pool for daily abilities (borrowed from 2e and 3e psionics), combined with at-will and encounter-based powers, means the summoner has three distinct resource levers: which creature you summon, how much essence you spent at summon-time, and how many power points remain for the day. That’s a lot of in-combat decisions. In a game like Daggerheart, where the Hope/Fear economy already generates moment-to-moment pressure, a third resource layer needs careful calibration to avoid decision fatigue at the table.
How Daggerheart’s Hope/Fear system changes the math
Daggerheart runs on 2d12 — one die generating Hope, one generating Fear. Spending Hope for effects while handing the GM Fear to work with creates a push-pull tension central to how the game feels. A summoner with its own internal resource pool needs to connect to that Hope/Fear loop somehow. Run it as a separate economy and the class sits outside the game’s core pressure rather than amplifying it.
One natural approach: tie essence regeneration to Hope results. When your summoned creature contributes to a Hope die outcome, recover an essence point. When it generates Fear, the GM gains something meaningful. This keeps the summoner inside Daggerheart’s core mechanic rather than running beside it.
The reset question matters more than it seems
Short-rest resets versus long-rest resets is probably the single most consequential design decision for this class. Short-rest resets encourage aggressive, frequent summoning — spend freely because you’ll recover. Long-rest resets push toward hoarding: players save essence for the encounter that really matters and feel punished every time they misjudge which one that is.
Daggerheart’s resting mechanics aren’t identical to D&D’s, so a Summoner playtest would need to define what recharge looks like in that system’s terms. The at-will / encounter / daily power structure maps reasonably onto Daggerheart’s existing action types — but the “three uses until end of encounter” framing carries a strong 4th Edition flavor that may need translation for Daggerheart’s scene-based structure.
What early playtesting will probably reveal
New class playtests almost always stress-test the floor first. Can a new player pick this up and feel useful before mastering the resource system? A Summoner with three interlocking pools is a high-ceiling, high-complexity design by any standard. Darrington Press has shown in Daggerheart’s base design a clear preference for mechanical elegance over subsystem proliferation.
The playtest will likely push toward identifying which of the three resource layers — summon choice, essence upgrades, or the power-point pool — can be simplified or collapsed without losing the core fantasy. That narrowing process is where the class either becomes a joy to run or a homework assignment you dread opening.