Wyldheart’s public demo shares earned experience with party members who are currently online. It does not presently hold that experience for an offline member to collect later. The developers want asynchronous catch-up behavior in the future, but parties should organize Demo 0.7.2 around the current online-only rule.
Know who is present before earning progress
Confirm that every intended player has joined the session and appears in the party before completing the activity. The demo supports solo play or groups of up to four. Use the current join code, share it privately, and regenerate it when troubleshooting or when an old code should no longer circulate.
Do not assume that membership in a friend group, campaign plan, or earlier session is enough. The official answer ties shared experience to being online with the party. If a player is absent, treat the session as progress they did not receive unless the current game explicitly shows otherwise.
Keep a regular party close without grinding blindly
Agree which sessions are progression sessions and which are experiments. If the group wants similar experience, reserve major goals for times when everyone is connected. When someone is absent, the remaining players can learn controls, test a weapon or skill setup, or explore with the explicit understanding that current shared experience will not be banked for the missing person.
At the next reunion, compare current skills and equipment rather than assuming identical characters. Classless progression allows different jobs, so perfect numerical matching is not required. What matters is that the group knows who can perform each role and whether an absent member lacks access needed for the planned route.
Avoid carrying exact catch-up formulas from the Beta into the Demo. The official FAQ describes the present rule and a desired future change but does not publish a current asynchronous reward calculation. “Planned” is not the same as “implemented.”
Separate experience, saves, and character availability
Experience sharing is one system. Saving is another. The demo can be played offline, but it does not save in offline mode. A player who appears to lose progress after an offline session has not demonstrated a shared-XP fault. Establish connection state before diagnosing party rewards.
Hope is another separate layer. Each character starts with five Hope. A character at zero Hope becomes unavailable until revived at the House of Memories in Whisperwood Forest using reagents. Being online does not automatically erase that consequence. A synchronized party can still lose access to one character if it ignores recovery planning.
Finally, the demo save itself is standalone and not planned to transfer to Early Access or the full game. Current group coordination is valuable practice, but it should not be sold as permanent launch progression.
Sources checked for shared progression
The online-only shared-experience rule, future asynchronous intention, four-player party size, offline saving limitation, no-transfer answer, and Hope recovery system come from the official Wyldheart Demo FAQs. Join-code fixes are checked against the team’s Demo 0.7.2 hotfix notes. The official Steam listing provides the wider co-op campaign intent, which is kept distinct from current Demo behavior.
Session-start checklist
- Everyone launches the public Demo client rather than the separate Beta.
- Steam is online for any session whose save matters.
- The host generates a current join code and sends it through a private channel.
- Every intended member appears in the party before the group completes objectives.
- The party states whether equal progression is a goal for this session.
- Members compare current jobs, skills, equipment, and Hope before choosing a dungeon.
- After the session, each person confirms their own saved state.
That routine cannot create the future asynchronous system, but it prevents the group from building plans around experience the current demo never promised to an offline member.