Skip to main content
Blueprints runs on the server. The only part that depends on the player’s own game is the interface, and only administrators open it.

The server

July 2021 update or newer
required
A dedicated or listen server you control the files of. The server needs no browser, so its operating system does not matter.
from the server
For activation, licence verification, and Remote Deploy while you use it. See Working offline.
as for any addon
The interface draws with the IBM Plex fonts that vetra-framework sends to connecting clients, through the normal server download or your FastDL. If a client is missing one, vetra_blueprints_status lists which.
Gamemode does not matter. Two adapters depend on another addon: Where the addon is not installed, its adapter is listed as Not installed and everything else works normally.

The administrator’s game

The interface is drawn by the browser Garry’s Mod embeds, and needs its Chromium engine. Which engine a game has depends on the operating system and the Steam beta branch (Steam, right-click Garry’s Mod, Properties, Betas).

Tested working

Expected to work, not yet tested with 1.1

The interface is built for Chromium 80, the oldest engine Garry’s Mod ships, and every build is checked mechanically for anything newer.

Unsupported

On Linux, switch the administrator’s own game to the x86-64 branch. Nothing else changes: the server, your players and every console command work the same on every branch, because nothing but the interface needs the browser.
Garry’s Mod decides which browser a client has, not Blueprints. Blueprints never refuses a client by its branch or version number: the interface checks, when it starts, whether the browser can run it, and says so if it cannot.

Players

Players install nothing and never see the interface. A player’s operating system, branch or browser has no effect on anything Blueprints does.

Upgrading from 1.0

1.1 reads everything 1.0 wrote, and going back to 1.0 is possible. See Updating.