Porting Quake to Three.js with Claude Code: Workflow and Limitations

Project Overview
A developer successfully ported Quake's source code to JavaScript and Three.js using Claude Code. The result is a web-based version of the classic first-person shooter game.
Key Details from the Source
The developer described this as "quite a lot of prompting work" but found a good workflow for porting projects like this. The working implementation is available at https://mrdoob.github.io/three-quake/ with source code on GitHub at https://github.com/mrdoob/three-quake.
During the porting process, Claude struggled specifically with porting the multiplayer server code (QuakeWorld) to Deno+WebTransport. The developer noted that "Codex figured it out somehow," suggesting that different AI coding assistants may have varying capabilities for specific technical challenges.
The developer recommends others try similar porting projects, indicating that despite the challenges, the approach yielded useful results and workflow insights.
Technical Context
Porting a complex C-based game engine like Quake to JavaScript and Three.js involves translating low-level graphics, physics, and networking code to web technologies. Three.js is a popular JavaScript 3D library that runs in browsers using WebGL. Deno is a JavaScript/TypeScript runtime alternative to Node.js, and WebTransport is a modern web API for low-latency, bidirectional communication.
📖 Read the full source: r/ClaudeAI
👀 See Also

Building a Steam Game in 10 Days Using Claude Code: Technical Challenges and Workflow
A developer built and released a game on Steam in 10 days using Claude Code without writing any code personally, but encountered significant challenges with logic design and debugging AI-generated code.

AI TDD Pipeline: How Bad Instructions Created 3,400 Tests and What Fixed It
A developer built a multi-agent TDD pipeline with Claude Code where different agents handle testing, coding, and review. The initial instruction 'write tests for everything' resulted in 3,400 tests with only 44% valid, leading to 'coverage theater' where tests didn't catch real bugs.

Autonomous OpenClaw Agent Runs 24-Hour Cold Outreach with API Keys
A developer gave an OpenClaw agent full read/write access to run cold outreach for 24 hours without human intervention. The setup used OpenClaw for autonomous reasoning, Zapier MCP for integrations, Brave Search API for research, and Gemini/OpenRouter for heavy context.

OpenClaw User Details Setup Challenges and Abandonment After Mac Switch
A developer switching from Windows to macOS encountered significant hurdles installing and configuring OpenClaw, including environment setup, channel configuration issues with Telegram and iMessage, and unexpected costs from AI model APIs. Despite getting basic functionality working, practical use cases like automated news briefing and multi-bot coordination in Feishu proved unreliable, leading to project abandonment.