How to Host a Dragonhold Server

Dragonhold supports online co-op alongside full solo play. When friends want repeatable Azarkeen runs without relying on ad-hoc join codes alone, a dedicated server gives you control over uptime, save persistence, and session rules. Exis Games ships Steam PC Early Access builds with dedicated server tooling evolving across updates — this guide explains hosting concepts, preparation, and troubleshooting so your group spends time dragon-riding instead of debugging ports.

Dedicated server vs peer hosting

Understand what you are setting up:

• Listen / peer host — one player’s game acts as the session host. Fast to start, but performance drops when the host has weak upload or exits unexpectedly.
• Dedicated server — a separate process (often on a PC, VPS, or spare machine) runs the world simulation 24/7 or during scheduled play. Better for recurring groups and consistent extract sessions.

For long-term co-op campaigns chasing Anchor Stones together, dedicated is worth the setup cost. Casual weekend groups may peer host until commitment solidifies.

Deep reference: Dedicated Server on this wiki.

Prerequisites before first launch

1. Steam ownership — every player needs Dragonhold (App 1510330); server host needs install rights for dedicated server files when Exis distributes them via SteamCMD or in-game tools.
2. Hardware headroom — CPU for AI Director spawns, RAM for player count, SSD for save IO.
3. Network — stable upload, preferably wired Ethernet on host machine.
4. Firewall access — ability to forward ports or configure Windows Defender exceptions.
5. Checklists — print Server Port Checklist before go-live.

Review System Requirements for baseline specs; hosting adds overhead above solo play.

Step-by-step hosting workflow

1. Install server files

Follow the latest Exis Games instructions in patch notes or Steam “Dedicated Server” depot when available. Early Access may require SteamCMD app ID matching the main game or a separate server branch — always pull from official channels, not third-party repacks.

2. Configure server.cfg (or equivalent)

Typical settings include:

• Server name — visible in browser lists.
• Password — optional for private groups.
• Max players — Dragonhold co-op slots per update; do not exceed official limits.
• Save path — explicit folder for hub/campaign persistence.
• Tick rate / performance flags — if exposed, favor stability over experimental throughput during Early Access.

Document your config in version control so patches do not silently reset values.

3. Open and forward ports

Port requirements change by build — verify against Server Port Checklist after every major update. Common pattern:

• Game port — UDP/TCP per Exis documentation.
• Query port — for server browser visibility if supported.

On home routers, forward to the hosting machine’s LAN IP. Double-NAT (router + ISP CGNAT) blocks inbound joins; friends may need VPN or relay solutions.

4. Launch and verify locally

Start the server process, connect from the same LAN client first, then external friend. Confirm:

• Hub island loads for host save.
• Azarkeen departure syncs for all riders.
• Extraction returns party to hub with loot intact.
• Disconnect/rejoin preserves state reasonably for Early Access standards.

5. Share join details securely

Send IP, port, and password through private channels. Rotate password if streaming publicly.

Session rules for co-op extraction

Servers fail socially before they fail technically. Establish:

• Loot rules — need/greed, quest item priority, crafting mat splits.
• Extract calls — unanimous vs majority; tiebreaker for critical Anchors.
• AFK policy — idle riders trigger Director spikes that wipe groups.
• Progression expectations — castle progress remains per-player on personal islands; clarify that co-op accelerates mission completion, not shared hub saves.

Align with Co-op Guide and How to Extract.

Performance and stability tips

• Host off the gaming PC when possible — running client + server on one box invites stutter during dragon combat.
• Limit graphics on headless hosts — if a GUI launches, minimize GPU load.
• Scheduled restarts — clear memory leaks common in Early Access dedicated builds.
• Backup saves — copy hub progress before patches; store outside auto-update folders.
• Watch AI Director load — large co-op groups increase spawn counts; see Risk vs Reward.

Troubleshooting common issues

Symptom	Likely cause	Fix
Friends timeout	Port forwarding / firewall	Re-run port checklist, allow exe in Defender
Desynced bosses	Latency or packet loss	Host nearer geographically; wired uplink
Missing saves after patch	Save path changed	Restore backup; read Updates
Invisible server	Query port blocked	Open query port; confirm server registration
Crash on extract	Version mismatch	Ensure all clients same build as server

If issues persist, test peer hosting to isolate network vs dedicated binary bugs before reporting to Exis.

When not to host

Skip dedicated hosting if your group plays monthly, has unstable upload, or cannot maintain patches. Peer host or solo with How to Play Solo instead — Dragonhold does not require servers for the full experience.

Hosting is a service to your community. Document configs, backup saves, and read patch notes — your dragon-riders will extract more reliably because of it.