Tools

Dragonhold Tools Hub

Practical checklists — extract smarter, host cleaner, and stop forgetting ports or loot calls.

Last updated:

Dragonhold Tools Hub — Checklists & Server Prep

Dragonhold punishes improvisation when pressure spikes. The AI Director escalates spawns, Hand of Fate modifiers flip run difficulty, and co-op parties wipe when nobody calls extraction. The tools hub collects lightweight, printable-style guides you can skim before launching Steam — not calculators or external apps, but structured markdown checklists that turn wiki knowledge into habits.

These pages complement narrative guides. Read How to Extract for philosophy; use Extract Checklist seconds before pushing a risky chest. Read Dedicated Server for hosting context; use Server Port Checklist when friends cannot connect despite a running process.

Extract Checklist walks through pre-departure, mid-run, and pre-extract verification: Hand of Fate review, inventory priorities, dragon stamina, co-op loot agreements, and abort signals. Copy the markdown checklists into your own notes if you stream or raid lead.

Server Port Checklist focuses on hosting hygiene: Steam dedicated server install, community-reported 7777/UDP game and 27015/UDP query forwards, Windows firewall rules, public IP verification, and LAN fallback options like VPN mesh tools when port forwarding fails.

Who should bookmark this hub

  • Solo riders who overstay Azarkeen and lose full bags.
  • Co-op shot-callers who need consistent extract vocabulary.
  • Hosts troubleshooting “works locally, friends timeout” issues.
  • Returning players after patches that reset bindings or server defaults.

Tools plus other wiki sections

Pair checklists with:

  • Loot Guide — know what belongs in your bag before using extract checks.
  • Co-op Guide — assign roles referenced in party sections of the extract checklist.
  • System Requirements — confirm hardware before hosting and playing on the same machine.
  • Updates — re-run checklists when patch notes mention networking or extraction rule changes.
  1. Extract Checklist — every rider benefits immediately.
  2. Server Port Checklist — hosts and aspiring hosts only.
  3. Getting Started — context if checklists feel abstract on day one.
  • Extraction — mechanics behind the checklist items.
  • Multiplayer — session rules and dedicated server guides.
  • Guides — deep walkthroughs when checklists expose knowledge gaps.

Tools do not replace skill — they reduce stupid losses. Use sibling pages below before your next Azarkeen departure or server invite.

How to use checklists in a live session

Treat tool pages as runbooks, not essays. Before launching Steam, open Extract Checklist on a second monitor or phone and tick only the lines that apply to your party size. Solo riders ignore co-op callouts; hosts ignore extract loot splits until friends join. After a wipe, re-run the mid-run section to identify whether Hand of Fate pressure, bag greed, or dragon stamina caused the loss — then jump into Risk vs Reward or Hand of Fate for the deeper mechanic explanation.

Hosts should keep Server Port Checklist beside router admin pages. Verify community-reported UDP ports against the actual Dragonhold dedicated server config on disk, then confirm Windows Firewall inbound rules before blaming Steam. When friends still time out, fall back to VPN mesh guidance linked from Dedicated Server rather than endlessly reinstalling the game.

Bookmark this hub next to Guides so every how-to article ends in a habit you can execute under pressure.

FAQ

Frequently Asked Questions

Quick answers tied to this page.

Are these Dragonhold tools separate programs?

No. They are markdown checklists on this wiki you can read or copy. Extract Checklist and Server Port Checklist are the main pages.

Which checklist should solo players use?

Start with Extract Checklist. Skip server pages unless you plan to host co-op.

Do port numbers come from Exis Games officially?

Community hosting docs commonly cite 7777/UDP and 27015/UDP. Server Port Checklist labels them community-reported — verify against your server config files.