Wyldheart’s public demo supports solo play or online co-op for a party of up to four. Friends can drop in and out, and the October 9 hotfix made the host’s join code visible in the Lobby or Roster. That code is how a party finds the current session; it is not a redemption code, beta key, or reward.
The demo launched under heavy server demand. Its saved progress normally depends on online services, and the official offline option is explicitly no-save. The future base game advertises cloud-shared campaigns, group XP, scaling difficulty, and PC cross-platform play, but those goals must not be used to promise that every demo case already works the same way.
Multiplayer status matrix
Host a session from the correct build
Every player should update the public demo before creating the party. The host opens or creates the intended campaign, waits until the lobby state is ready, then reads the join code in the Lobby or Roster. Hotfix 0.7.2 CL39302 specifically repaired its visibility, so if the field is absent, confirm the demo version before changing accounts, firewall rules, or files.
Share the code privately. A screenshot of the lobby can expose it, so crop or cover the code when asking publicly for help. Name the demo version, region, approximate time, and error instead. Never post account credentials or ask someone to sign into Steam on your behalf.
Pick a short first objective. Leaving The Slurper’s Den or reaching Rivermere is easier to coordinate than promising a complete dungeon tour. Confirm that every player can move, interact, see the party, and access the intended campaign before advancing.
Join without losing the campaign context
Enter the host’s current code through the matching demo lobby flow. If it fails, ask the host to read a fresh code after confirming the lobby is open. Verify that both clients show the same version and that Steam is online. A stale code after the host recreates a campaign may no longer describe the active lobby.
After joining, wait for the host to explain the current location and objective. Inspect your character, equipment, Hope, and supplies. Do not trigger a map move or conversation while another player is loading or in a menu. Drop-in support reduces scheduling friction, but it does not remove the need to synchronize at a transition.
The Co-op Guide provides a compact host/join checklist and recovery order.
Protect progress during server trouble
Open the official status page first when logins or campaign loading fail for many people. CL39317 improved login and reconnect reliability and prepared more server capacity, but a released hotfix does not guarantee that the service is always healthy.
The Online Save checkbox can be used to play offline when connectivity blocks a solo session, but the official notice states that offline saves are not supported in this demo. Disabling saving means the run disappears when you exit. It is not a safe workaround for a long co-op campaign and does not turn online progress into a local file.
If persistence matters, keep online saving enabled and wait for service recovery. Restart Steam and the demo, verify files, and retest one change at a time. Do not delete unknown save data or copy a path from an unrelated game.
Coordinate party roles without fixed classes
Wyldheart is classless. Instead of assigning roles from ancestry or background labels, state what the current equipment can do. Decide who leads room inspection, who answers distant threats, who watches the rear, and who carries critical supplies. Change those jobs when the party finds a better tool or someone wants to learn another system.
Call landmarks rather than “left” and “right” in variable dungeon rooms. Say “the wall switch beside the gate” or “the rope near the injured character.” Before traveling a hex, confirm everyone has closed menus and understands the destination. After a defeat, stabilize the room and decide on recovery together.
Trade and loot should follow immediate need. A strong ranged item may do more for the party member covering distant targets than for the player who picked it up first. Keep a functional backup available when durability becomes a concern.
Understand shared XP and absent players
The base-game vision includes group XP, cloud-shared saves, catch-up, and a party continuing while someone is offline. March previews discuss those features as part of the planned campaign structure. The demo FAQ and launch behavior can apply narrower rules, including limits on what an offline member receives.
Treat the demo as its own implementation. Before progressing without someone, test a low-cost action and compare the returning player’s state. Record whether they were disconnected, deliberately offline, or simply absent from the active party. Do not promise automatic credit for objectives or XP without a current reproducible result.
Demo saves will not transfer to the full game. Shared progress inside the demo does not change that boundary.
Keep crossplay claims narrow
Steam’s base-game page lists Cross-Platform Multiplayer, and developer interviews describe Early Access on Steam and Epic with crossplay as the plan. That supports a future PC scope. It does not confirm console crossplay, cross-save, or the exact interoperability of the public Steam demo.
Do not use the Steam feature badge alone as a troubleshooting instruction for an Epic friend. Wait for an official client list and test both active versions. Console releases were discussed as future plans, not current demo platforms.
Report a co-op problem usefully
Include Demo AppID 4475270, version 0.7.2, UTC time, host region, party size, online-save state, action that failed, visible error, and whether reconnecting worked. Say whether solo login also failed. This helps separate a service incident from one lobby or client.
Remove join codes, account names, and private messages from screenshots. Read Updates and the official status notice before repeating destructive local fixes.
Sources checked October 10, 2026
Recommended guides
Choose the guide that matches what you want to do next.
Wyldheart Co-op Guide
Host or join a four-player Wyldheart demo session, find the current join code, coordinate the opening, and avoid offline save loss.
MultiplayerWyldheart Crossplay Status
Separate Wyldheart's Steam cross-platform feature label and PC launch plans from unconfirmed Demo, Steam–Epic, and console crossplay claims.
MultiplayerWyldheart Shared Progression Guide
Understand who receives experience in Wyldheart demo co-op, what offline members miss, how saves work, and how to keep a party aligned.
All Multiplayer guides
3 focused guides with steps, checks, and current caveats.
Wyldheart Co-op Guide
Host or join a four-player Wyldheart demo session, find the current join code, coordinate the opening, and avoid offline save loss.
Oct 10, 2026Wyldheart Crossplay Status
Separate Wyldheart's Steam cross-platform feature label and PC launch plans from unconfirmed Demo, Steam–Epic, and console crossplay claims.
Oct 10, 2026Wyldheart Shared Progression Guide
Understand who receives experience in Wyldheart demo co-op, what offline members miss, how saves work, and how to keep a party aligned.