> ## Documentation Index
> Fetch the complete documentation index at: https://docs.vetrasuite.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Compatibility

> What Blueprints 1.1 needs on the server and on the administrator's game, which clients have been tested, and which cannot run the interface.

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

**Garry's Mod** `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.

**Outbound HTTPS** `from the server`

For activation, licence verification, and Remote Deploy while you use it. See
[Working offline](https://docs.vetrasuite.com/support/offline.md).

**File downloads to clients** `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:

| Adapter | Needs |
| - | - |
| DarkRP job spawns | DarkRP on **SQLite**. MySQL-backed job-spawn storage is not supported in 1.1. See [DarkRP](https://docs.vetrasuite.com/blueprints/darkrp.md) |
| PermaProps props | **MalboroDEV PermaProps**, Workshop item `220336312`. See [PermaProps](https://docs.vetrasuite.com/blueprints/permaprops.md) |

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

| Client | Engine | Tested |
| - | - | - |
| Windows, default branch | Chromium 86 | In game, with 1.1, including a clean client joining a dedicated server |
| Windows, x86-64 branch | Chromium 86 | In game, with 1.1 |
| macOS | Chromium 80 | In game, with 1.1 |

### Expected to work, not yet tested with 1.1

| Client | Engine | Why it is expected to work |
| - | - | - |
| Linux, x86-64 branch | Chromium 80 | The same engine version as macOS, which is tested. Not tested on Linux |

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

### Unsupported

| Client | Engine | What happens |
| - | - | - |
| Linux, default branch | Awesomium | Blueprints cannot draw its interface. It says so in chat, names the x86-64 branch, and opens nothing |
| Linux, dev branch | Awesomium | The same |

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.

> [!NOTE]
>
> 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](https://docs.vetrasuite.com/blueprints/updating.md).


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.