# Vetra

> Documentation for the Vetra suite of Garry's Mod addons. Vetra Blueprints versions, migrates and deploys a server's managed setup, and the Adapter SDK lets any addon take part.

- [Vetra Blueprints](https://docs.vetrasuite.com/index.md): Build. Version. Migrate. Deploy. Version, migrate and deploy your Garry's Mod server setup.
- [Overview](https://docs.vetrasuite.com/blueprints/overview.md): What Vetra Blueprints is, what it is authoritative over, and the model behind every screen in it.
- [Installation](https://docs.vetrasuite.com/blueprints/installation.md): Download from GmodStore, copy two folders into garrysmod/addons/, restart. There is nothing to configure.
- [Opening Blueprints](https://docs.vetrasuite.com/blueprints/opening.md): Type !vblueprints in chat. The console command still works, and the server decides who is allowed in.
- [Quick start](https://docs.vetrasuite.com/blueprints/quickstart.md): Capture a Version, change the world, read the diff, and put it back. Roughly ten minutes on a test server.
- [Core concepts](https://docs.vetrasuite.com/blueprints/concepts.md): Versions, objects, identity, adapters, groups and plans: the six ideas every screen in Blueprints is built on.
- [Versions, history and diff](https://docs.vetrasuite.com/blueprints/versions.md): Capture an immutable record of the managed world, browse the history, and compare any two Versions object by object.
- [Groups, anchors and pivots](https://docs.vetrasuite.com/blueprints/groups.md): A market stall is one thing you built, not forty props. Groups let you treat it that way.
- [Migration Assistant](https://docs.vetrasuite.com/blueprints/migration.md): Rebuild a group captured on one map onto another, with a ghost preview in the world before anything is created.
- [Restore and rollback](https://docs.vetrasuite.com/blueprints/restore.md): Return the managed world toward an earlier Version. The full plan is shown first, a recovery Version is written before anything destructive, and a failed restore rolls back and verifies the rollback.
- [Export and import](https://docs.vetrasuite.com/blueprints/packages.md): A Version in a file. Move a build between servers over FTP or your control panel, with nothing sent to Vetra.
- [DEV to PROD](https://docs.vetrasuite.com/blueprints/deploy.md): Build on a development server, deploy to production. The production server always decides what happens to its own world.
- [Remote Deploy](https://docs.vetrasuite.com/blueprints/remote-deploy.md): Hand a Version from your development server to your production server through Vetra, without touching FTP. Optional, and never the only route.
- [Supported objects and integrations](https://docs.vetrasuite.com/blueprints/supported-objects.md): Exactly what the four shipped adapters manage, what each of them can do, and what each of them will not do.
- [DarkRP job spawns](https://docs.vetrasuite.com/blueprints/darkrp.md): Blueprints versions DarkRP job-spawn positions on SQLite-backed servers. What it manages, what it will not, and the MySQL limitation.
- [MalboroDEV PermaProps](https://docs.vetrasuite.com/blueprints/permaprops.md): Blueprints versions the props MalboroDEV PermaProps has saved, through the saved record rather than the prop in the world, so a change survives a restart.
- [Updating](https://docs.vetrasuite.com/blueprints/updating.md): Replace two folders and restart. Your data lives elsewhere and is not touched.
- [Uninstalling](https://docs.vetrasuite.com/blueprints/uninstalling.md): Delete two folders. Your data stays until you delete it, and your exported packages are plain files you keep.
- [Adapter SDK](https://docs.vetrasuite.com/sdk/overview.md): Blueprints versions, migrates and restores a Garry's Mod server's setup. An adapter is the piece that teaches it one domain.
- [Quickstart](https://docs.vetrasuite.com/sdk/quickstart.md): A complete, registered, capturable adapter in one server file, then the seven decisions behind it.
- [Adapter anatomy](https://docs.vetrasuite.com/sdk/anatomy.md): Every field and every function on an adapter descriptor: required, optional, or capability-dependent.
- [Registry and lifecycle](https://docs.vetrasuite.com/sdk/registry.md): Register from one hook, once, after the map loads. Load order does not matter, and the window closes.
- [Identity](https://docs.vetrasuite.com/sdk/identity.md): The one field most likely to be wrong, and the one whose consequences are worst.
- [Capabilities](https://docs.vetrasuite.com/sdk/capabilities.md): A capability is not a function that looks roughly right. It is a promise about a result, for every object your adapter produces.
- [Capture and records](https://docs.vetrasuite.com/sdk/records.md): What Collect must return, field by field, and why what you get back is a different shape.
- [Diff semantics](https://docs.vetrasuite.com/sdk/diff.md): How your records become added, changed and removed, and why an unstable field makes a diff useless.
- [Transform](https://docs.vetrasuite.com/sdk/transform.md): Moving and reorienting an existing object. Position and orientation only, deliberately.
- [Materialize](https://docs.vetrasuite.com/sdk/materialize.md): Rebuild one of your records, report what it became, and be able to undo that. Three functions, and the third is the point.
- [Properties](https://docs.vetrasuite.com/sdk/properties.md): Conform an existing object to a record you captured. The only values you may write are ones you can also read back.
- [Removal and ownership](https://docs.vetrasuite.com/sdk/removal.md): Genuinely destructive, and the contract says so. What your adapter must guarantee before Blueprints will destroy anything.
- [Migration and deployment](https://docs.vetrasuite.com/sdk/migration.md): What your adapter is responsible for when a record captured somewhere else is rebuilt here.
- [Persistence integrations](https://docs.vetrasuite.com/sdk/persistence.md): When the object is a record and the thing in the world is only a projection of it. The hardest adapter shape, and the one most third-party addons actually have.
- [Data versions and missing adapters](https://docs.vetrasuite.com/sdk/compatibility.md): Two numbers on your descriptor doing two different jobs, and the guarantee that historical records never silently disappear.
- [Error handling](https://docs.vetrasuite.com/sdk/errors.md): Refuse in phase 1, fail cleanly in phase 2, and never lose data quietly.
- [Testing your adapter](https://docs.vetrasuite.com/sdk/testing.md): Run the contract from the console, then the checks no runner can do for you.
- [The example adapter](https://docs.vetrasuite.com/sdk/example-adapter.md): A complete adapter with all five capabilities, shipped with Blueprints, taken apart section by section.
- [Compatibility checklist](https://docs.vetrasuite.com/sdk/checklist.md): The things that go wrong, in rough order of how much damage they do. Read this before you ship.
- [API reference](https://docs.vetrasuite.com/sdk/api-reference.md): Every function a third-party adapter is expected to use, with its exact signature, realm and return shape.
- [Licensing and servers](https://docs.vetrasuite.com/support/licensing.md): Three servers per purchase, automatic activation, and what every licence state means.
- [Working offline](https://docs.vetrasuite.com/support/offline.md): Blueprints keeps working for up to 14 days with no connection at all. Only Remote Deploy needs the service while you use it.
- [Moving or replacing a server](https://docs.vetrasuite.com/support/moving-a-server.md): Moving a server keeps its files and needs nothing. Rebuilding one from scratch needs a recovery code, and does not consume another slot.
- [Where your work is stored](https://docs.vetrasuite.com/support/data.md): Everything Blueprints builds lives on your own server. The one exception is Remote Deploy, and it is always your choice.
- [Troubleshooting](https://docs.vetrasuite.com/support/troubleshooting.md): The failures people actually hit, what each one means, and what to do about it.
- [FAQ](https://docs.vetrasuite.com/support/faq.md): The questions asked before buying and during the first week, answered honestly.
- [Getting support](https://docs.vetrasuite.com/support/getting-support.md): Open a ticket on the product page. Here is what to include so the first reply is an answer rather than a request for more information.
- [Service availability](https://docs.vetrasuite.com/support/availability.md): What happens to your installation if Vetra is ever discontinued. The commitment, stated plainly.