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

How to study or rebuild the Odamex changes for the mod with Intermission

Apply engine/odamex.patch to the named Odamex commit to see or reproduce the headless engine changes.

Who it is forA C++ or game engine developer who wants to learn how the mod runs Odamex without a window.

The problemThe mod changes Odamex to render frames into shared memory or a temp file, and the changes are only described in the README.

The outcomeA local Odamex tree at the matching commit with the Intermission patch applied, ready for reading or building.

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 engine/odamex-commit to get the Odamex commit the patch was made against.
  2. Clone Odamex and check out that commit with git checkout <commit>. (inferred, check the README)
  3. Apply the patch from engine/odamex.patch with git apply engine/odamex.patch. (inferred, check the README)
  4. Review the diff and note the shared memory or temp file frame output path.
  5. Keep the GPL-2.0 license of Odamex in mind for any derived code.

Prompt for your agent

Clone jarrodwatts/intermission and Odamex, check out the commit listed in engine/odamex-commit, apply engine/odamex.patch, and report whether the patch applies cleanly. Summarize where frames are written and verify the GPL-2.0 note applies to the engine changes.

Caveat. The README does not give the Odamex clone URL or build steps, so the commands above are inferred from the patch and commit files.

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