How to Sell GTA Roleplay Scripts on Tebex

Selling a GTA roleplay script means turning a resource you built into a product server owners can buy, download, and run. On the FiveM/Cfx.re platform there is exactly one legal way to do this: Tebex. The entire pipeline is creator-friendly once you understand the three moving parts: your Cfx.re account (where you upload and encrypt the asset), your Tebex store (where the money and delivery happen), and the escrow grant system that ties a purchase to a buyer's server license key. This guide walks the full flow end to end so you can go from finished code to a live, purchasable package.

The three pieces you need before you sell anything

Before a single sale can happen, three accounts have to be connected and configured. First, a Cfx.re (FiveM) account with access to the Portal/Keymaster, where you create and encrypt your asset. Second, a Tebex creator account and store, which is the only sanctioned storefront and payment processor for FiveM content. Third, the link between them: when you build a Tebex package you point it at the specific asset you uploaded to your Cfx.re account, and Tebex talks to the Cfx.re Keymaster API to deliver the grant automatically when someone pays.

You do not need your own Stripe or PayPal merchant account to start. Tebex acts as the Merchant of Record, meaning it collects payment, handles VAT/sales tax, processes chargebacks, and pays you out from your wallet. Your job is to produce a clean, working, well-documented script and configure the store correctly.

• Cfx.re account + Portal access (to create the escrow asset)
• Tebex creator account set to the FiveM store type
• A finished, tested resource with a working config and docs
• Optional but recommended: a Discord for support and updates

Step 1: Create and encrypt your asset on Cfx.re

Log into the Cfx.re Portal and create a new asset, then upload your resource as a single zipped folder. The escrow system encrypts the files you choose so buyers can run the resource but cannot read or edit your core logic. Currently Lua 5.4 (your fxmanifest must set lua54 'yes'), plus YFT, YDD, and YDR stream files are supported for encryption; the maximum size for an escrowed asset is 1GB.

Crucially, you decide what stays open. Use the escrow_ignore directive in your fxmanifest.lua to leave configuration, README, and locale files fully editable while protecting everything else. A typical setup leaves config.lua and your locales open so buyers can adjust settings without ever seeing your protected source. When you later ship an update, you re-upload the asset through Created Assets in the Portal and existing buyers receive the new version.

• Set lua54 'yes' in fxmanifest.lua (required for escrow)
• Zip the resource folder and upload it as a Created Asset
• Add escrow_ignore for config and locale files
• Re-upload through the Portal to push updates to all buyers

Step 2: Build the Tebex package and connect the asset

In your Tebex control panel, create a new package. When Tebex asks what the buyer should receive, choose FiveM Asset and select the asset you just created from the dropdown. This binding is what makes delivery automatic: at checkout, Tebex calls the Keymaster API and writes a grant against the buyer's Cfx.re account so the resource will authenticate on their licensed server.

Fill in the listing like a real product page. Write a clear title, a description that lists framework compatibility (ESX, QBCore, QBox), dependencies, and a short feature list, and add screenshots or a preview video. Set your price and currency, and decide whether you want category bundles or single-script listings. A confusing or bare listing kills conversions more often than the price does.

Step 3: Launch, deliver, and support

Once the package is published, a buyer pays on your tebex.io store, the grant lands on their Cfx.re account automatically, and they download or pull the resource into their server. When they start it, the server's license key is checked against the account that owns the grant. That is the entire delivery loop, and it runs without you lifting a finger per sale.

What you do have to do is support the product: respond to install questions, fix bugs, and ship updates. Reviews and word of mouth in the FiveM community are the real growth engine, and they are won by responsive support, not by marketing copy. If you are still learning to build the scripts themselves, PlayDeck teaches the whole pipeline with an AI build workflow where you steer the design and the AI writes the Lua, then walks you through packaging it for Tebex the right way.