riftscript
Browse scripts Watch on YouTube
How it works

From checkout to your server.

No license keys to paste, no phone-home, no piracy theatre. Tebex handles payment, Cfx escrow handles delivery and licensing. Here is the whole flow.

Step 01

Buy on our site

Pay in an embedded popup right here on riftscript.com. Tebex processes the card - you are never redirected to a third-party storefront.

Step 02

Cfx grants the asset

On a completed purchase, the script is granted automatically to the Cfx account you checked out with - encrypted and attached, no keys to copy.

Step 03

Locked to your server

It appears in your Portal granted assets, escrow-locked to your server license key. Add it to your resources and you are live.

!The one thing to get right: check out with the same FiveM account you use in the Cfx Portal. The grant attaches to the account that paid - if they differ, the script cannot be delivered. This is the single most common first-time hiccup.

Before you buy

What you need

Have these ready and setup takes a couple of minutes.

A Cfx (FiveM) account

The same one you use in the Cfx Portal. This is the account the script gets granted to.

Your server license key

Escrow locks each asset to your server key. Find it in your txAdmin or server.cfg.

The listed dependencies

Usually oxmysql and ox_lib, plus your framework (QBCore, QBox, or ESX). Each script lists its own.

Questions

Good to know

Do I need a Tebex account to buy?
No. You check out right here on our site - Tebex only processes the payment in the background. The one account that matters is your Cfx (FiveM) account, because that is where the script gets granted.
My purchase went through but the script is not in my Portal. Why?
Almost always this means checkout used a different FiveM account than the one signed into your Cfx Portal. The two must match. Contact support with your order email and Cfx account and we will sort it out.
Is the source code open?
Cfx escrow encrypts Lua and model files to protect the work. Configuration, locale, and documentation are fully open and editable, and UI layers stay readable where escrow allows. You get a drop-in resource you can configure, not a black box.
Which frameworks are supported?
QBCore, QBox, and ESX through the rift_core bridge, per script. Each product lists the frameworks it supports on its page.
Do I get updates?
Yes. Updates are re-granted to your Cfx account automatically - pull the latest from your Portal whenever a new version ships.
What is your refund policy?
These are escrow-locked digital goods, so we cannot offer no-questions refunds. If something does not work as described, reach out - we would much rather fix it or make it right.

Ready when you are.

Browse the catalog and add your first script. Delivery is instant and automatic.

Browse scripts