Module B8 · Ship, sell & maintain

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):
Artifact build (sv_enforceGameBuild):
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 dependencies (ox_lib, oxmysql, and your framework). If it only breaks with a third paid script loaded, that is a conflict (out of scope), not your bug.

Paid script support workflow

The workflow

Use a fixed intake template

Reproduce before you promise a fix

Triage by cause

Fix, version, and release

Keep reading the full lesson