NX CreativeNX CreativeDocs
Getting Started

Installation

Server prerequisites and the first-boot checklist shared across every NX Creative script.

Every NX Creative script assumes a baseline FiveM server with a supported framework and the ox ecosystem in place. Set this up once and individual scripts drop in without further fuss.

Prerequisites

FiveM server
Required

Latest recommended artifact. Linux or Windows.

MySQL / MariaDB
Required

Any recent MySQL 8 or MariaDB 10.6+ build.

txAdmin
Optional

Recommended for server management and recipe-based setup.

Framework

Pick one of the supported roleplay frameworks. See the Frameworks page for notes on each.

es_extended
Optional

ESX Legacy, the classic framework.

qb-core
Optional

QBCore, a modular alternative to ESX.

qbx_core
Optional

QBox, a modern QBCore fork by Overextended.

Base resources

These four are used by most NX Creative scripts. Install them once, keep them up to date, and most scripts will install without config changes.

ox_lib
Required

Shared utilities, UI primitives, callbacks.

ox_target
Required

Interaction and targeting layer.

ox_inventory
Required

Inventory system. Used by most item-based scripts.

oxmysql
Required

MySQL driver. Required by most scripts.

Install checklist

  1. Download. Grab the latest release .zip from your Tebex purchase.

  2. Unpack. Drop the folder into resources/[nx]/ or wherever you keep third-party resources.

  3. Import the SQL. Scripts with persisted state ship a SQL file in the resource folder. The file name is listed on each script's own installation page. Run it against the same database oxmysql points at.

  4. Edit config.lua. Per-script settings live here. Avoid editing shared.lua or server.lua unless the script's docs say otherwise.

  5. Add to server.cfg. Start the script after its dependencies:

    ensure ox_lib
    ensure ox_target
    ensure ox_inventory
    ensure oxmysql
    ensure nx_<script>
  6. Boot and verify. On first start, the framework bridge logs the detected framework to the server console. If the resource reaches the started state without errors, it is good to go.

Troubleshooting

When a script refuses to start, the cause is almost always one of:

  • A dependency is not running, or is the wrong version.
  • The SQL file was not imported, or was imported into the wrong database.
  • The license is not bound to this server in Tebex Keymaster.

If none of those apply, see Support.