DOOMSDAY-SERVER(6)

👑 DOOMSDAY-SERVER(6) — the local legend herself 💖

okay bestie, sit DOWN because we're talking about doomsday-server, aka the Doomsday Engine multiplayer daemon. She's the quiet one at the party who's actually running everything. This is a LOCAL manual page, so you're getting the homegrown, unfiltered version. 🎀

---

✨ NAME ✨

doomsday-server — the Doomsday Engine multiplayer daemon, no cap 🫶

---

🌸 SYNOPSIS 🌸

doomsday-server [-stdout] [-port tcp-port] [-iwad dir] [-game mode] [-v]
[-file file ...]

not me having to warn you: the command line is NOT interpreted according to GNU conventions. everything after -- gets straight-up ignored. and @ can be used to specify a response file whose contents get added onto the command line. it's giving ✨chaotic but iconic✨

---

💅 OPTIONS 💅

• -file | -f — names one or more resource files (WAD, LMP, PK3) to load at startup. you can load more later at runtime with the load command, slay.
• -game | -g — sets the game to load after startup. check doomsday(6) for the full list of available games. for example:

-game doom1-ultimate

and listen: if -game is not specified and the server can't pick a game automatically? she quits. 💀 no game, no service, periodt.

• -iwad — specifies a directory where to look for IWAD files. Doomsday will search for IWADs from all known games and automatically load them when needed. note that you can also use the DOOMWADDIR environment variable or the paths configuration file to specify where the IWAD files live. options on options, we love a flexible queen. 💜
• -port — the TCP port that the server listens to for incoming connections.
• -stdout — prints all log entries to the standard output. if you don't use this, nothing is printed, so the server can vibe as a background process. 🤫
• -verbose | -v — print verbose log messages. specify it more than once for extra verbosity. she can be LOUDER, bestie. 📢

and in addition to all of these, doomsday-server supports many of the command line options of doomsday(6). so go read that one too. iykyk.

---

🦋 OPERATING A SERVER 🦋

Doomsday servers are, by default, silent daemon processes intended to be run in the background. like, genuinely silent. the way that she just sits there and works with zero drama? main character energy fr fr.

you need to use the Doomsday Shell to monitor their status and control them. that's your group chat with her, basically. 🫶

🔥 Firewall and NAT 🔥

Doomsday uses TCP network connections for multiplayer games. so if you host a game and you're behind a firewall or using NAT, you MUST make sure other computers are able to open TCP connections to your computer. that entails opening the appropriate incoming TCP ports on your firewall and/or configuring the NAT so the correct ports are routed to your computer. don't skip this part, i'm begging. 😭

additionally, UDP ports 13209-13224 are used for detecting servers running on the local network. so if you're having problems with autodetecting local servers, check that your firewall isn't blocking these UDP ports on either end. both ends!! yes both!!

a server opens one TCP port for listening to incoming connections. that port must be open for incoming TCP traffic in the firewall. the port number is configured with the console variable net-ip-port. by default, a server uses TCP port 13209. 📌

you can see status information about the network subsystem with the console command:

net info

vibe check your network, bestie. go do it. 🧚

---

⭐ SEE ALSO ⭐

doomsday(6), doomsday-shell-text(6)

---

💖 AUTHOR 💖

this documentation has been written by Jaakko Keränen <jaakko.keranen@iki.fi>. we stan a documenter. 👑

---

and that's the whole page, bestie!! shoutout to Debian and the date helmikuuta 4, 2021 for stamping this beauty, and to DOOMSDAY-SERVER(6) herself for being the most lowkey iconic daemon on your machine. go forth and host. 💅✨🌸🦋💜