Vcore Framework Documentation
The official Vcore developer documentation structure is now live. Technical content will be populated after the current framework and optional add-ons have been fully audited.
Full developer docs are coming soon.
We are deliberately holding back API examples until the current Vcore framework source has been verified. This prevents outdated, guessed or QBCore-renamed APIs from being published as Vcore documentation.
Documentation structure
Getting Started
Installation, requirements and first-server setup.
Awaiting Vcore source audit →Core Object
Framework access and the public Vcore core object.
Awaiting Vcore source audit →Player Data
Player data structures, lifecycle and public fields.
Awaiting Vcore source audit →Shared Data
Shared framework registries and configuration data.
Awaiting Vcore source audit →Callbacks & Events
Client/server callbacks, events and lifecycle hooks.
Awaiting Vcore source audit →Client Function Reference
Verified client-side Vcore API reference.
Awaiting Vcore source audit →Server Function Reference
Verified server-side Vcore API reference.
Awaiting Vcore source audit →UI & NUI Reference
Framework UI, shared NUI and integration reference.
Awaiting Vcore source audit →Commands
Vcore command registration and built-in commands.
Awaiting Vcore source audit →Building a Vcore Resource
How to build resources cleanly against Vcore.
Awaiting Vcore source audit →Multicharacter Lifecycle
Character loading, selection and spawn lifecycle.
Awaiting Vcore source audit →Troubleshooting
Common Vcore development and integration issues.
Awaiting Vcore source audit →Base & Addons
The layout is ready now. Once the framework source is supplied, each section will be replaced with documentation verified against Vcore itself.