How can we help?

Make sure your operating system meets the minimum requirements (Windows 10+, macOS 12+, or a current 64-bit Linux distribution). On Windows, allow the installer through SmartScreen if it appears. On macOS, you may need to right-click the installer and choose Open the first time.

If the installer still fails, send the log file (usually under ~/.packrelay/logs/) to support and we'll take a look.

Sync stalls are usually one of three things: a corrupt local game directory, a manifest whose signature can't be verified, or a transient network problem. The launcher will display a specific error code when this happens — include it when you contact us so we can route the issue correctly.

That message comes from 7DTD's Steam server browser, which discovers servers via an older Steam-based protocol called SteamNetworking. Most modern dedicated servers — including most PackRelay-listed ones — disable SteamNetworking because it complicates NAT traversal, and run the newer LiteNetLibprotocol instead. The Steam browser can't query a server that doesn't have SteamNetworking on, so it falls back to the generic “Could not retrieve server information” message that doesn't actually tell you anything useful.

Three ways to connect anyway:

• The PackRelay launcher — connects directly via LiteNetLib. Built for this exact problem.
• Direct “Connect to IP”— in 7DTD's Join Game menu, find the direct-connect option and use the server's connect address (shown on its page under /servers).
• The cross-platform server list (EOS-based, inside 7DTD) — works regardless of the SteamNetworking setting.

Server owners: if you'd rather your server be discoverable from the Steam browser, edit serverconfig.xml to either remove the ServerDisabledNetworkProtocols property or set its value to empty (value=""), then restart 7DTD. You'll trade some NAT-traversal complexity for that discoverability.

Create a server-owner account at /signup/server-owner. After confirming your email you'll be able to attach a running 7 Days to Die server, generate a signing key, and publish your first pack.

Almost always: the config file wasn't created. The mod ships with a packrelay-config.json.example template next to its ModInfo.xml, but heartbeats don't start until you copy that to packrelay-config.json (no .example suffix) and fill in your slug + API token. The mod logs a clear warning at startup when the file is missing but leaves the rest of your server running, so the silence is easy to miss.

Check that Mods/PackRelayServerTools/packrelay-config.json exists (not just the .example), that the slug matches what's on your My Servers page, and that the token is a real one from /account/tokens (starts with pr_). Restart 7DTD after saving the file — the first heartbeat lands within ~70 seconds and the indicator flips to Online.

No. The launcher synchronizes the modpack into the game directory but leaves your saves, world files, and screenshots alone. We treat anything outside the pack's manifest as off-limits.

From your account settings, choose Delete account. We will remove personal identifiers from active systems immediately. Some backup and abuse-prevention records are retained for a reasonable period as described in our Privacy Policy.