Wyldheart Wiki - Systems: Hope, Death, Crafting and Progression

ProductPublic Demo AppID 4475270; Alpha and future base-game behavior labeled separately VersionDemo 0.7.2 checked 2026-10-10; exact costs and recipes require the live client PlatformWindows PC through Steam

Wyldheart links combat, travel, rest, equipment, and character growth into one survival loop. You leave safety with limited supplies and weapons, travel through hexes, explore rooms, collect materials, manage Hope and fatigue, then decide whether to push farther or return to a town or camp. The public demo demonstrates this loop, but exact heart counts, revival requirements, recipes, skill values, and progression caps are all fields that can change after Demo 0.7.2.

Public March Alpha previews give useful context: travel and night could affect Hope, camps supported cooking and rest, equipment could be repaired, and a character who exhausted Hope faced a more serious death state. Those reports came from an older build. Use them to understand what to watch, then use the current interface for the actual value and consequence.

System loop at a glance

DecisionCurrent player checkSafe response

TravelTime, Hope, party readiness, destination, possible encounterMove one hex, observe the change, and keep a route back.

Enter a dungeonHealing, light, weapon condition, spare equipment, online save stateRepair or redistribute supplies before crossing the entrance.

Spend a pointRepeated problem, branch requirement, confirmation text, respec uncertaintyBuy for a known need and leave room before an irreversible choice.

Craft or cookKnown recipe, ingredients, tool or station, party needMake a useful item instead of spending rare materials on an untested result.

Continue after defeatVisible Hope state, recovery option, distance to safety, party supportRecover before another risky fight when the consequence is unclear.

Treat Hope as an expedition budget

Hope is not the same as the ordinary health lost during one fight. Alpha hands-on reporting described a heart-based reserve that could fall after knockouts or dangerous travel, and a hopeless state that made another defeat much more serious. Do not hard-code the Alpha count or revival route into Demo 0.7.2. Read the live Hope display and any warning shown after defeat.

Before leaving Rivermere or a safe camp, decide how much risk you can absorb. A route with an unknown dungeon, night travel, and damaged equipment consumes more of that budget than a short known trip. If the display falls, identify the action that caused it before continuing. Several rapid hex moves make that diagnosis much harder.

The Hope and Death guide explains how to record the current rules without turning an older preview into a false demo mechanic.

Camp before the party becomes fragile

Developer interviews and hands-on reports show camp as a place to rest, cook, craft, and repair. The best camp decision happens before every system is empty. Stop when darkness, fatigue, low condition, missing supplies, or a long return route would make the next encounter disproportionately costly.

Check what the live camp interface actually permits. A portable action in Alpha may require another tool, skill, or location in the demo. If an option is unavailable, read the prerequisite instead of assuming a bug. Divide tasks in co-op so someone does not advance travel while another player is crafting or rearranging equipment.

Cooking is useful when the meal answers a planned challenge. Read the current effect and duration, then consume it before the relevant section rather than after the party is already failing. Do not publish a recipe or buff from memory unless the active build displays it.

Craft, repair, and commission with a purpose

The official game description confirms gathering materials, crafting items, cooking meals, and upgrading gear. A March developer interview says basic items can include practical supplies such as torches, bandages, and rope, with deeper work opening through skills or craftspeople. That outline helps players ask the right question, but exact demo recipes and costs need a current screen.

Separate four actions: making a consumable, cooking a meal, repairing an existing item, and obtaining or improving equipment through a specialist. Each has a different resource decision. Before spending, record the ingredient names, quantity, result, and version. Leave an unknown field blank when the UI has not shown it.

Weapon condition connects crafting to combat. A powerful item with poor condition may be less valuable than a reliable spare on a long route. Check durability at a safe stop and keep at least one functional answer for the range or damage role your party needs.

Progress by solving observed problems

Wyldheart’s classless branches include Adventuring, Survival, Dungeoneering, Weaponry, and the Oldways of Magic. Instead of spreading points evenly, identify what stopped progress. A stamina or travel problem suggests a different investigation from a locked route, unreliable weapon, or missing spell tool.

Read requirements and confirmation text. The current public material does not securely establish a free respec route for Demo 0.7.2. If reversal is uncertain, keep a reserve until you know whether a choice unlocks the result you expect. A flexible classless tree means paths can be mixed; it does not guarantee that every point can be moved without cost.

Compare progression in solo and co-op separately. The planned full game advertises group XP and catch-up systems, while demo FAQ information reports current limitations for an offline member. Do not use the future design promise as proof of how every demo session awards experience.

Make defeat information actionable

After a knockout, stop and read every message. Record health recovery, Hope change, lost items or condition, respawn location, and what the party can do. If the demo offers a recovery or revival route, capture the exact requirement and who performs it. One old Alpha article described town or scroll-based possibilities, but the current build must confirm them.

Do not test permanent consequences with a valued online save unless you accept the risk. A separate disposable demo campaign is safer for investigating a hopeless state. Remember that playing with online saving disabled creates a different limitation: the session is not persistent at all.

In co-op, decide whether to recover the affected character, retreat, or redistribute gear before another encounter. A rushed second defeat can turn a recoverable mistake into a lost expedition.

Keep an honest system record

For any rule, record the client, public version, date, platform, solo or party state, visible prerequisite, action, and result. Distinguish “the interface states” from “we observed once.” Repeat volatile mechanics before making a firm claim.

Do not transfer Closed Beta 0.5.x behavior to the demo. Do not treat a development CL in a hotfix title as a Steam BuildID or the base game’s semantic version. When Early Access begins, recheck Hope, defeat, revival, recipes, repair, skill trees, XP sharing, save behavior, and caps from the new client.