Return to Castle Wolfenstein in browser

Game files

No own-file request on checked landing page

Controls

Controls not confirmed

Account

No sign-in in checked entry

Mobile gameplay

Not tested

Full session

Not tested

HTTP link check

HTTP 200; 0 redirects (2026-10-15)

Basis: limited desktop entry observation. Observations: Oct 15, 2026. Conditions organized: October 15, 2026.

The landing page showed player-name and Play controls without sign-in or own-file upload, plus a roughly 380 MB source warning. Play was not pressed; later prompts, gameplay controls and a session are unknown.

Project type: Browser port

The original RTCW entry explicitly credits iortcw compiled to WebAssembly and Wwasm. Only entry requirements were checked; no scene or full session was verified.

Classification organized October 15, 2026 from the recorded source and check notes; not a new gameplay test.

This Return to Castle Wolfenstein browser guide covers rtcw.pieter.com's original entry page. Our observation stopped at its requirements, player-name form and author credits. We did not press Play or complete the large initial transfer described there. That narrower check is useful when deciding whether to start, but it must not be confused with the scene checks recorded on the separate Quake II and Quake III pages.

The page describes an unofficial multiplayer project and credits iortcw and Wwasm. This is not a console-emulator listing, a publisher endorsement or a hosted copy on Tab Game Guide. We reviewed the source on October 15, 2026, and published this guide the same day. The adaptation's first release date was not established; our observation date and a reference-list date are not substitutes for that missing fact.

Guide published 2026-10-15. Source reviewed 2026-10-15. Author release-page publication: Not established. The landing page did not establish the first publication date of this browser build.

Game files

The landing page warns of an approximately 380 MB first load and describes later caching. We did not start that transfer, measure its size, inspect its contents or test whether the cache survives another visit. No user-supplied-file selector appeared on the checked landing page, but this does not rule out requirements in an unvisited later step. The practical distinction is between the source's proposed download and files a visitor supplies. Neither path should be interpreted as this directory providing game data, a launcher or a rights-cleared asset package.

Controls

The visible entry offered a player-name field and Play button. We inspected those interface elements but did not launch a scene or establish keyboard, mouse, controller or touch gameplay. Seeing a first-person game name does not tell us which bindings this browser adaptation uses. Its gameplay-control filter therefore remains unknown. Read the current original instructions before making assumptions about movement or input capture, and do not transfer a confirmed menu key from our Quake II check to this different client.

Account

The landing page was visible without signing in and did not ask us for an email, password, payment or existing game account. Because we did not press Play, this is explicitly an entry-page observation; later access and server requirements were not inspected. A player-name field alone cannot establish the behavior of a persistent identity, reserved slot or statistics account. We did not create a profile, accept a subscription, enable the notification button or contact any of the players named by the source.

Mobile gameplay

The source recommends desktop Chrome. We did not compare browsers, test a mobile device or verify a complete Chrome gameplay session. A recommendation on an author's page is different from our own compatibility test. In particular, a phone displaying the entry form does not establish that it can handle the stated data transfer, render a scene or provide usable first-person controls. Touch input, screen rotation, controller pairing, storage behavior and sustained mobile performance all remain unverified for this entry.

Full session

No playable scene was reached during this check because we stopped before Play. We therefore did not verify server access, map loading, team selection, movement, combat, scoring, saving, completion or reconnect behavior. The source displayed multiplayer-related text and live-looking status information, but that was not a session we tested. The image on this page is a capture of the entry and download warning, deliberately labelled as requirements evidence rather than a gameplay screenshot. A round or campaign should not be inferred from a static landing screen.

HTTP link check

An independent request to rtcw.pieter.com's root URL returned HTTP 200 with no redirect on October 15, 2026. It confirms the particular landing URL responded at the time of that request. It does not verify the stated 380 MB resource set, a game server, an actual round or continued availability. We keep that transport result separate from the browser requirements review. If you later continue into Play, use the exact current error or loading state rather than treating this historical root response as a guarantee about the rest of the project.

Read the source's size and desktop recommendation before starting, especially on a metered connection. The approximately 380 MB value is the project's stated first-load amount, not our independently measured cost, and later network activity could differ. The author also describes caching; we did not test persistence or recovery and do not recommend clearing browser data as a generic repair. A source review can honestly document these decisions without claiming that the download or game worked. This directory's bookmark stores only a project identifier, not game files, client settings or a recoverable RTCW session.