Lua · Fixes · Edits · Custom order
Bug Fixes & Script Edits
A focused pass on a script you already have — a bug, a config that will not stick, or a small feature change. The brief should include the resource, the problem, and any error output you have.
Starting at $39Final quote in a ticket
Packages
Clear packages for bug fixes & script edits.
Small fix or tweak
A contained bug fix or config-level change.
Starting at $39
Turnaround. About 2–4 days after we have the resource and the brief
Revisions. One revision round
- A written note of what is broken or what should change
- A fix or tweak on a resource you already have the rights to edit
- A short change note
- One revision round
Starting at. Final quote after we review your scope. Payment is collected with Stripe after you approve the quote — the pay button on this site is not open yet.
Feature add
A small feature added to an existing script you have the rights to edit.
Starting at $129
Turnaround. About 5–10 days after we have the resource and the brief
Revisions. One revision round
- A written scope for the feature
- The feature added to the existing resource
- A short change note
- One revision round
Starting at. Final quote after we review your scope. Payment is collected with Stripe after you approve the quote — the pay button on this site is not open yet.
What's included
In a typical bug fixes & script edits order
- A written note of the problem and the target resource
- A fix or edit limited to the agreed scope
- A short summary of what changed
- One follow-up pass if the same issue remains
Honest scope
Quoted before work starts
Fixes and focused edits to scripts you already run. The form below starts the brief. The official quote lands in a Discord ticket so nothing is assumed off a sample page.
Starting at. Final quote after we review your scope. Payment is collected with Stripe after you approve the quote — the pay button on this site is not open yet.
Example work
Before and after
Before / after


Sample before-and-after of a config typo — not a real crash log from a city, and not a client project.
How it works
Request, quote, deposit, build, review, delivery.
- 01
Request
Fill in the brief on this page and open a Discord ticket. The form copies the brief to your clipboard — nothing is stored on the site.
- 02
Quote
You get a written scope, a quote against the starting price, and a timeline before any work starts.
- 03
Deposit
A deposit is due after you approve the quote. Freelance deposits are still arranged in your Discord ticket — the pay button on freelance pages stays off, because quote amounts vary. Staff will send a Stripe payment request after the quote is approved.
- 04
Build
Work happens against the agreed scope. Progress updates land in your ticket.
- 05
Review
You review the work. The revision rounds in the package are included; extra rounds are quoted.
- 06
Delivery
Final files or setup are handed over after the agreed balance is paid.
FAQ
Before you send a brief.
Quote request
Request Bug Fixes & Script Edits
Tell us what you need. This form prepares a brief you can paste into a Discord ticket — files are not uploaded from the site. Attach references in the ticket. You get a scope and quote before any work starts.
Development
Related requests
Custom Scripts
New Lua and NUI resources for ESX or QBCore, or systems built for how your city plays.
Custom UIs & HUDs
HUDs, menus, phones, and screens styled to match your city.
Server Setups & Configs
A structured FiveM server setup or config pass, built from your plan.