RTCW Browser Port

rtcw.pieter.com runs Return to Castle Wolfenstein multiplayer in the browser using the real iortcw engine compiled to WebAssembly, proving that full legacy game experiences can now be shipped as inspectable web products rather than toy demos. Source: rtcw.pieter.com, 2026-06-30

Routing Summary

Use the RTCW browser port as a browser-game ambition and implementation reference, not as a generic WebAssembly dependency. When a project involves game preservation, native-engine browser ports, multiplayer loops, cache-heavy assets, or engine lineage research, inspect this page before assuming the work must be rebuilt from scratch.

What It Proves

The useful lesson is not nostalgia. The useful lesson is that a web game can carry a heavy native-engine lineage and still feel like a product surface: first load downloads about 380 MB of cached game data, the browser page includes controls and caveats, and the hosted experience adds a daily match loop and leaderboard-like social frame. Source: rtcw.pieter.com, 2026-06-30

Kevin's browser game projects such as Princeton Tower Defense, PawPointClicker, and PortfolioMon Showdown should treat this as an existence proof for ambition. A serious browser game can be a persisted artifact with assets, cache strategy, multiplayer or event cadence, and community surface. It does not have to present itself as a disposable demo.

Engine Lineage Signal

The bookmark image is a Quake engine genealogy chart. That matters because RTCW is part of a larger engine family rather than an isolated one-off: Quake, GLQuake, QuakeWorld, Quake II, Quake III, id Tech, Source, Call of Duty, Titanfall, Apex, and RTCW all sit in the same historical family tree. Source: X/@levelsio visual artifact, 2026-06-24

For agents, this changes the research route. When porting, emulating, or rebuilding a game-like artifact, inspect the engine lineage and surviving open-source forks before assuming the product needs a from-scratch implementation.

Versioning

There is no public package version for the hosted rtcw.pieter.com service. The versionable sources are the engine and browser-port repositories:

Do not cite the hosted page as a stable implementation version. Cite the page for product behavior and the repositories for code authority.

---

Timeline

• 2026-06-30 | Deep-reviewed Kevin's bookmark, inspected the local visual artifact, verified rtcw.pieter.com, iortcw, and Wwasm, and promoted the browser port into a focused tool/reference page. Source: X/@levelsio, 2026-06-24; rtcw.pieter.com; GitHub API
• 2026-06-24 | Pieter Levels shared the RTCW browser port with a Quake-engine genealogy visual. Source: X/@levelsio, https://x.com/levelsio/status/2069850990317289923