Shooter

Quake II

Open a Quake II multiplayer browser client and check its controls, first-load resources and device notes.

Version Quake II multiplayer through FTEQWFTE QuakeWorld browser clientChecked

Start here

Open the game source

Opens the independently hosted multiplayer browser client in a new tab. Arcadle does not host the engine, server or game resources.

Open Quake II

Opens in a new tab. Arcadle checked the source on desktop; mobile play is listed separately when verified.

How to get started

  1. Open the project website and enter a player nickname.
  2. Select Play and leave the loading tab open until the engine and map are ready.
  3. Click the game to focus it. Use W A S D to move and the left mouse button to fire. If killed, use the source respawn flow.

Controls

Move
W A S D
Fire / respawn
Left mouse button
Pause or release mouse
Esc

If loading stops

  • Give the initial resource download time to finish before reloading.
  • If movement does not respond, click inside the game to focus it. Use Esc to release the pointer in first-person games.
  • Try an up-to-date desktop browser and check the source for an error. A reachable launch page does not guarantee its multiplayer server is available.

Before you start

Resources
The tested source displayed approximately 77.5 MB during first resource loading. This is an observed loader value, not a fixed download-size guarantee.
Account
The tested launch required a player nickname, not an account sign-in. Server rules may change.
Storage and saves
The source loads or caches game resources in the browser. Persistent scores, settings and saved games were not tested; do not assume progress transfers between sources or browsers.

Source and credits

Runtime: FTE QuakeWorld browser client · Technical source

Device notes

  • Desktop ChromeTested

    AI-operated source-origin review on macOS. Movement and firing were tested; a full match and persistent progress were not tested.

  • Phones and tabletsNot verified

    Not tested by Arcadle. Source UI claims, where present, are not device verification.