Skip to main content
TRACK B·SELL AND SUPPORT·Verified June 2026 · Lua 5.4 · ox_lib 3.x
Learning with an AI assistant?
Copies this lesson plus 2026 ground rules (no lua54 'yes', Cfx.re Portal, correct callback signatures) as a ready-to-paste mentor prompt.

Paid script support workflow

Selling a script means signing up for support, and unmanaged support eats your time and your reviews. A workflow fixes that: a fixed intake template, a triage rule, and a written support boundary so buyers know what they get. This is the difference between a side income and a second unpaid job.

You'll build
A repeatable support process for a script you sell: issue intake, reproduction templates, versioning, and a clear support boundary.
Time
~25 minutes.
You need
A script you ship (or plan to), and a place buyers can reach you.
You'll learn
Intake template -> clean-server reproduction -> triage -> fix, version, and release -> the support scope and response time you commit to
BEFORE YOU START

The workflow

Use a fixed intake template

Every report arrives with the info you need to act.

Require buyers to fill the same fields. No template, no triage.

code
Script version:
Framework + version (ESX Legacy / Qbox / QBCore):
FXServer artifact/build (in the FXServer console window, or the txAdmin Live Console, type `version` and copy the line it prints):
GTA game build (a separate content version, set by `sv_enforceGameBuild` in server.cfg, e.g. 3258; leave blank if not set):
What you did:
What you expected:
What happened (exact console error):

Reproduce before you promise a fix

You know whether it is your bug or their setup.

Reproduce on a clean test server with only your script plus its declared dependencies. If another resource is required to reproduce, classify it as an integration conflict. It is only out of scope if your published compatibility/support terms say so; a conflict with an integration you claim to support is still your responsibility.

Triage by cause

Each ticket gets the right response, fast.

Sort tickets: your bug (fix and release), install/config (point to docs), conflict (out of scope, suggest direction), feature request (backlog, not support). Most tickets are config, not bugs.

Fix, version, and release

The fix ships with a version bump and a note.

Fix on a branch, bump the version (semver), write a one-line changelog, and release. Reply to the ticket with the version that contains the fix so the buyer knows exactly what to update to.

Keep reading the full lesson

Sign in to start, then unlock every step of this lesson and the full FiveM School with a membership.

Still ahead in this lesson
  • How it works
  • Common mistakes
  • What you can do now
Sign in with Discord Browse the school

The remainder of Paid script support workflow is available to FiveM School members.

PREVIOUS
Tebex compliance and refunds