vns-core
vns-core is the shared compatibility layer that every current VNS script is built on. It is a free, fully open-source resource, and it stays open source even when the script using it is the encrypted variant.
Instead of every script carrying its own framework, inventory and target code, all of that lives in vns-core. A VNS script only calls vns-core's functions, and vns-core translates each call to whatever your server actually runs.
What it handles
| Category | Supported |
|---|---|
| Frameworks | QBCore, QBox, ESX |
| Inventories | ox_inventory, qb-inventory, qs-inventory, origen_inventory, codem-inventory, tgiann-inventory, core_inventory, ESX's built-in inventory |
| Targeting | ox_target, qb-target, qtarget |
| Notifications | Your framework's own notifications, or ox_lib |
| Also | Money, usable items, stashes, jobs, vehicle ownership, player identity and names, progress bars, the shared admin permission |
Everything is auto-detected. On start, vns-core checks which supported resources are running and picks the matching adapters by itself. You only touch its config if you want to force a specific choice.
How it is delivered
- vns-core is a separate download in your Keymaster/cfx Portal. It is not included in any script's zip.
- It updates independently: a script update never requires a new vns-core download unless the script's changelog says so, and a vns-core update never requires re-downloading your scripts.
- Scripts no longer have framework, inventory, target or notification
settings in their own config. If you need to force one of these, you do it
once in
vns-core/config.lua.
Why it matters for you
- One install, every script. Set vns-core up once and every VNS script works with your framework, inventory and target system.
- Custom framework or inventory? Because vns-core is open source, you (or your developer) can add support for a custom system in one file. See Custom frameworks & inventories. Every VNS script picks it up automatically; you never need to edit the scripts themselves.
- Encrypted scripts stay adaptable. The protected part of an encrypted VNS script contains no framework code, so nothing framework-related is hidden from you.
- For developers. Every function is exported and documented in the Exports reference, so your own resources can use it too.
Note
Keep exactly one copy of vns-core on the server, even if you own several VNS scripts, and keep it up to date. Newer script versions are built against the newest vns-core.