Skip to main content

Where

Open a ticket on the Vetra Blueprints product page on GmodStore. We aim to reply within 72 hours, and faster in practice.

What to include

Include these, or the first reply will just ask for them.
1

What you did, and what happened

Step by step, and what you expected instead.
2

The output of vetra_license_status

From the server console. It prints no secrets.
3

The output of vetra_blueprints_adapter report

If the question is about what Blueprints manages, a Version or an adapter. From the server console:
It carries no player, licence or network data.
4

Your console log

Or the relevant part of it, from the first [Vetra] line onward. Copied as text rather than as a screenshot where possible.If the problem is in the interface, the client console (press ~ in game) often has the useful half.
5

Your setup

Your Garry’s Mod version, the map, whether the server is DarkRP, Sandbox or something else, which addon folders you installed, and whether you renamed any of them.
If it involves a specific Version, group, migration or deployment, tell us its name or id. We do not need the data itself.

What never to send

Do not send licence identifiers, recovery codes, activation codes, API tokens, server passwords or RCON details. Not to us, and not to anyone else.We do not need them. vetra_license_status deliberately prints none of them, and it is enough to diagnose every licensing problem.

Before you open a ticket

Most problems have a named cause and a named fix:

Troubleshooting

The failures people actually hit, with what each one means.

FAQ

The questions asked before buying, answered honestly.

For adapter developers

If you are writing an adapter and something in the SDK is unclear, wrong, or missing, say so in a ticket. The SDK is a deliverable, and a gap in it is a bug. Read the compatibility checklist first: most adapter problems are one of the items on it.