Skip to content

Platform overview

Server discovery, resource downloads, and gameplay use separate connections.

Component Role
Game server Runs server scripts, manages connected players, and coordinates shared game state.
Client Runs inside GTA, executes client scripts, and exchanges game state with the server.
WebViews Render in-game interfaces and communicate with client scripts through the browser bridge.
Project launcher Selects a server and calls the client helper, displaying its progress and results.
Client helper Selects a compatible client, prepares its files and the server’s client resources, and starts the game.
Discovery API Resolves a join code into connection details, client compatibility information, and resource metadata.
Resource host Serves packaged client scripts, UI files, and assets over HTTP(S).
Voice service Routes voice traffic according to the channels and permissions configured by server scripts.

Resource hosting can use the game server’s built-in HTTP server or an external host. Voice can run inside the game server or in a separate voice process, on the same machine or another one.

Server scripts, databases, and private configuration stay outside the client resource package.

  1. The launcher passes the selected server’s join code to the helper.
  2. The helper resolves the server details, selects a compatible client release, and prepares the required client files and resource bundle.
  3. The helper starts GTA with the Revo client. The client connects to the game server. Voice uses a separate media connection when enabled.
  4. The game mode handles initialization, its UI, player spawning, etc.

The reserved dev join code uses the local game server’s discovery endpoint. Local discovery requires API registration to be disabled and needs no project credential. Client installation and updates still use the normal release downloads.