Props that don't break
- Props that don't break
- Module
- 19
- Deliverable
- A validated, collision-correct, draw-call-optimised prop with a live DUI screen
- Chapters
- 1
FiveM development, done for profit
Turn your FiveM skills into real income.
Sell scripts, vehicles and maps on Tebex, land paid commissions, and run a server that pays for itself. The complete playbook for script, vehicle, clothing and map developers, and server owners.
$30/month for everything. Log in with Discord, cancel any time.
- Modules
- 24
- Chapters
- 41
- Reading time
- ~5 h
- Price
- $30/mo
- Field-tested on
- 700 players
Paths to income
Four ways to get paid.
Every FiveM server needs scripts, cars and maps, and a lot of what is for sale breaks the moment real players arrive. Learn to build the kind that holds up, and you are the developer servers come back to and the owner players stay with.
Scripting developers
- Sell resources on Tebex to servers everywhere
- Take paid commissions for custom jobs and systems
- Charge more for code that is secure and fast
You'll learnLua, ESX and Qbox, ox_lib, NUI, security and performance.
Modules for scripting developersVehicle developers
- Sell optimized add-on car packs
- Take commissions for handling, liveries and sounds
- Ship packs that load fast, so servers keep buying
You'll learnvehicles.meta, handling, streaming budgets, Blender and Sollumz.
Modules for vehicle developersClothing developers
- Sell add-on clothing packs and job uniforms
- Take commissions for server-branded outfits
- Ship packs that don't shift drawable IDs or clash with others
You'll learnHow GTA clothing works, ymt files, drawable limits, Blender and Sollumz.
Modules for clothing developersMap developers
- Sell MLOs, props and map packs
- Win custom interior commissions from big servers
- Build maps that don't crash clients or tank FPS
You'll learnymaps, MLOs, CodeWalker, Blender and the field-tested prop and MLO rules.
Modules for map developersOwners
- Monetize through Tebex within the Cfx.re rules
- Spend less on paid scripts by building in-house
- Keep players and supporters with a server that stays fast at peak
You'll learnSetup, buying and installing scripts, administration, performance and anti-exploit.
Modules for owners
Fix it fast
Paste the exact error, not "it doesn't work".
The troubleshooting cheat-sheet maps every common console error to its cause and fix, so the bug that used to cost you an evening costs you five minutes.
Troubleshooting chapter- attempt to index a nil value (global 'ESX')Framework object not fetched
- Couldn't find resource mc_towingFolder name differs from ensure
- ECONNREFUSED 127.0.0.1:3306The MariaDB service isn't running
- No such export GetPlayer in qbx_coreqbx_core not started first
> Convert this ESX resource to Qbox. Keep event and export names, replace xPlayer.* with player.Functions.*
fxmanifest.lua, client.lua, server.lua
Ship faster
Ship in hours, not weeks.
A copy-ready prompt library for scripts, vehicles, weapons, clothing, maps and SQL. Let AI handle the boilerplate so more of your hours go into work you can sell.
The prompt libraryCurriculum
Bill of materials
No.TrackModulesChapters
00Set up your toolkitThe tools and the workflow, including how to work fast with AI.M03
01Stand up a serverLocal test server, ESX or Qbox, database and admin.M1-M58
02Write scripts that sellLua, events, NUI, frameworks, security and performance.M6-M86
03Build vehicles and assetsClothing, vehicles and weapons that are ready for release.M9-M113
04Build the worldMaps, MLOs, CodeWalker, Blender + Sollumz and Blender MCP.M12-M154
05Run it for realGame data, production hosting, prompt packs and a final project.M16-M186
06Advanced: field-tested rulesWhat breaks at 600+ players, and the rules that keep servers online.M19-M239
Advanced modules
The rules that keep a 700‑player server online.
Big servers pay for work that holds up under load. The advanced modules cover what silently goes wrong: files that validate and do nothing, props that crash the client, scripts that hold at 50 players and fall over at 600. Learn it once, charge for it every time.
Get accessMLOs that don't crash
- MLOs that don't crash
- Module
- 20
- Deliverable
- An MLO cut into a vanilla building with manifest, RoomIDs, portals and lint passing
- Chapters
- 1
Animated weapons
- Animated weapons
- Module
- 21
- Deliverable
- A UV-scroll animated weapon skin with validator and inventory icon
- Chapters
- 1
Server performance & downloads
- Client performance
- Resource loading and downloads
- Module
- 22
- Deliverable
- A client-script audit and a download-bloat audit of your own server, with fixes applied
- Chapters
- 2
Running at scale & anti-exploit
- Running at scale
- Exploit and economy lessons
- AI operating rules
- "Before you ship" checklists
- Module
- 23
- Deliverable
- Operator runbook, egress audit, exploit-class checklist, CLAUDE.md rules installed
- Chapters
- 4
Field rules
Each one cost a test cycle, a build or an outage.
- R01 / Props
Collision is a few boxes. Always set CompositeFlags1 and CompositeFlags2 on every bound, because empty means players walk straight through.
Module 19 / Chapter 1 - R02 / MLOs
Never DLC_ITYP_REQUEST an MLO's own ytyp. It crashes every client on join.
Module 20 / Chapter 1 - R03 / Animated weapons
Hashes are joaat and per weapon: one clip per shader, each with its own animation.
Module 21 / Chapter 1 - R04 / Exploits
Every money, item, job or claim event gets server-side timing, ownership, distance, rate limits and permissions. The server rolls all randomness.
Module 23 / Chapter 2 - R05 / Operations
Never ensure or restart heavy or hook-injecting resources with players online.
Module 23 / Chapter 1
Start
Build something worth selling.
One subscription, $30 a month. Log in with Discord, start Module 0 today, cancel any time.