DEDUPED Hot AI repos, turned into use cases Get 5 a day

How to self-host the Intermission game server with Intermission

Use deploy.sh to build and run the stock Odamex server on your own droplet.

Remote script. deploy.sh builds and runs software on a remote droplet, so read the script and confirm its actions before you run it against any host.

Who it is forA developer or hobbyist who wants a private Doom server for their own group instead of the shared one.

The problemThe default plugin connects to a shared server, and some people want to run their own game host.

The outcomeA stock Odamex server built and running on a droplet, reachable by the game client for a group.

What you need first

  • Claude Code 2.1.287 or later
  • macOS 15 or later in Ghostty or kitty, or Windows 10 or 11 x64 in Rio
  • Internet access for the first-time game download (about 20 MB) and the UDP connection to the intermission server

Steps

  1. Read deploy.sh in the repo to see what it builds and runs before you execute it.
  2. Provision a droplet, the hosting setup the README names as the target.
  3. Copy the repo to the droplet and run ./deploy.sh from the repo root. (inferred, check the README)
  4. Confirm the server is running, then note its address for the game client.
  5. Check that the server is stock Odamex, as the README describes, before you connect players.

Prompt for your agent

Clone jarrodwatts/intermission, read deploy.sh, and summarize every command it runs before anything executes. Then run it on the <droplet-host> target only after I approve, and report whether the Odamex server process is running.

Caveat. The README gives no full setup steps for the droplet, so the exact commands beyond deploy.sh must be worked out from the script itself.

Share: X LinkedIn Hacker News Email Copy link

Disclaimer

Deduped lists open-source repositories that belong to other people. We do not own, maintain, audit, or vouch for any of them, and a repo appearing here is not an endorsement or a safety check. The use cases, steps, and prompts are written by AI and may be incomplete, outdated, or just wrong. Where a use case is marked "Seen in the wild", we link to public posts where someone described something similar, but we have not verified those posts and the use case itself is still our AI's own write-up. Use all of this at your own risk. Only run code, commands, or agents on systems and accounts you are authorized to use, and read the code and every command before you run it, especially anything that touches credentials, files, or the network. Nothing here is professional, security, legal, or financial advice. All trademarks and project names belong to their respective owners, and their use here does not imply affiliation. Content is provided as is, without warranties of any kind. Found a mistake, a safety problem, or something you want removed? Email [email protected] and we will look at it promptly. Full disclaimer page