ObsidianOBSIDIANDEVELOPMENTS
Documentation

Install, license & update

Everything you need to get your Obsidian scripts running — protected, licensed, and update-safe. The same flow works for every product.

Installing a script

Five steps, the same for every Obsidian product. Each product page lists its exact resource name and any extra notes.
1

Download your files

Go to My Licenses in your account and hit Download latest on the product. You always get the newest build, stamped to your account.

2

Drop it into your server

Unzip the folder and place it in your server's resources directory. We recommend grouping ours in a folder like [obsidian].

3

Add your license key

Paste your key (from My Licenses) into your server.cfg. Every Obsidian resource reads the same convar:

set obsidian_license "OBS-XXXX-XXXX-XXXX-XXXX"
4

Ensure the resource

Add it to server.cfg after your framework and dependencies, then restart:

ensure obsidian_warden
5

First launch validates your license

On start, the resource checks your key with our license server. If it's valid, the protected code unlocks and runs. If the key is missing, wrong, revoked, or expired, the resource refuses to start and prints the reason in your console — nothing sensitive is ever exposed.

Your license key

One key per purchase, bound to the first server that activates it.
Where to find itYour account → My Licenses. Click Copy on any license card.
Server bindingA key locks to the first server that activates it. Switching servers? Hit Request reset on the license, or ask support.
One convar for everythingEvery Obsidian resource reads obsidian_license, so you set it once.
TermsLifetime licenses never expire. Subscription packages validate while the subscription is active.

Frameworks & dependencies

Each product page shows exactly which framework and resources it needs.

Most Obsidian scripts support ESX, QBCore, and QBox, and some are standalone. Use the framework filter on the store to find ones that match your city. Common dependencies like ox_lib, oxmysql, and ox_inventory are listed under Dependencies on each product page — ensure those load before the Obsidian resource in your server.cfg.

Updating

New builds ship from your dashboard — your key never changes.
Re-download from My Licenses and replace the folder. Your license key stays the same — no reconfiguration needed. We recommend backing up your config.lua first if you've customised it.

How your purchase is protected

So you know exactly what you're running — and why your files stay yours.
Server code stays sealedCore server files are encrypted and only unlock after your license checks out at runtime.
Client code is obfuscatedAnything sent to players is scrambled, so it can't be read, copied, or reused.
Every copy is watermarkedEach download carries a hidden fingerprint tied to your account.
Keys are per-server & revocableA key binds to the first server that activates it and can be revoked instantly.

FAQ

Where do I put my license key?

In your server.cfg: set obsidian_license "OBS-…". Every Obsidian resource reads that one convar.

Can I move a license to another server?

A license binds to the first server that activates it. Use Request reset on the license card in your account, or open a support message, and we'll reset the binding.

Does Obsidian Access include the anti-cheat?

No. Warden Anti-Cheat is a separate standalone subscription. View Warden →

I bought a script but it won't start.

Check the server console — the resource prints the exact reason (missing key, wrong key, load order). Make sure dependencies load before it. Still stuck? Contact support.

Still need a hand?

Our team is in Discord and your account inbox.
Join our Discord Open a ticket