Everything you need to run MAKCODE resources.

Use the same provider at checkout and in the dashboard so purchases, license keys, and downloads stay on one account.

• Discord — primary sign-in for the site and dashboard.
• CFX.re forum — optional where enabled; links your forum identity to the same account flow.

• Open dashboard

Checkout is handled by Tebex. When you complete payment, fulfilment runs automatically: your dashboard updates with the script, license information, and download access.

Keep your receipt email and order reference—support may ask for them if something does not appear right away.

• Add items to the cart from any product page, then review totals on the cart screen.
• Promo codes can be applied on the cart before checkout when a code-based promotion is active.
• Sitewide sales apply automatically when configured without a code.

• View cart
• Refund policy

The dashboard is your hub after purchase. From there you can download scripts, view license keys, track orders, and manage favorites.

• Purchases — order history and fulfilment status.
• Downloads — access packages you own.
• Licenses — keys or entitlement details per script.
• Favorites — saved products for later.
• Notifications — purchase fulfilment, review updates, and support replies.

• Go to dashboard

Every resource ships with an install guide in the download package. Typical steps: extract to your resources folder, add dependencies to server.cfg in the correct order, configure the shared config file, and restart the resource.

Always match the framework version noted on the product page (ESX, QBCore, OX, or standalone). Running the wrong bridge is the most common install issue we see.

• Read dependency and load-order requirements before starting the server.
• Use a staging environment to test before deploying to production.
• Check the product changelog when updating—major versions may need migration steps.

Product pages show compatibility badges (ESX, QBCore, Standalone, OX). Only buy resources that list your stack unless the description explicitly mentions a bridge you plan to use.

• ESX / QBCore — economy, jobs, and inventory integrations vary by script; follow the guide for your fork.
• OX — often used for inventory and target systems; confirm ox_lib / ox_inventory versions.
• Standalone — fewer framework hooks; you may need to wire events yourself.

Purchases include updates within the major version line described on the product page. Download the latest build from your dashboard when we publish a release.

Breaking changes are documented in the changelog on each product page and announced on Discord when relevant.

• Product changelogs on store pages

Active storewide or per-product sales are reflected on product and cart prices. Some promotions require a promo code at checkout; others apply automatically.

If a code does not work, confirm it is still active, spelled correctly, and entered on the cart page before payment.

• Apply a code on the cart

Most issues are resolved by verifying framework version, resource start order, and config values against the install guide.

• Purchase missing from dashboard — wait a few minutes, refresh, and confirm you signed in with the same account used at checkout.
• Script errors on start — check server console for missing dependencies or wrong framework bridge.
• Performance problems — reduce debug mode, review tick-heavy loops in config, and test with fewer players first.

• Contact support

For install help, bug reports, or billing questions, use our support page or Discord. Contact us before opening a payment dispute so we can fix fulfilment or technical issues first.

• Support center
• Terms & conditions
• Privacy policy