Support

Start with an up-to-date FXServer running txAdmin, pick a framework (ESX, QBCore, or Qbox), and get familiar with how a server.cfg is structured. Our documentation lists the prerequisites for each product, and our Discord is there to help if you get stuck on the basics.

A framework provides the shared foundation of a roleplay server: player accounts, money, jobs, base inventory. If you inherited an existing server, look at the resources inside resources/[core], or ask its previous admin — most community scripts name their framework dependency directly.

Broadly: get the product (automatic delivery for escrowed scripts, or an archive to unzip), drop it into your resources folder, add ensure script-name to your server.cfg, then restart the server. Every KEOPS Studios product has its own documentation page with exact steps and any dependencies to install first.

Open the server console (or txAdmin's Console tab): the exact error is almost always shown there — a missing dependency, load order in server.cfg, or a resource name conflict. If the error doesn't mean much to you, paste it as-is in our Discord — it speeds up diagnosis a lot.

Escrow protects the source code: the script is delivered compiled and encrypted, tied to your Cfx server, with no access to the code itself. Open source lets you freely read and edit the files, but requires more discipline during updates so you don't overwrite your own changes. Each product page states which mode it uses.

Our products keep code and configuration (config.lua or equivalent) as separate as possible. Before any update, back up your current configuration, compare it against the new version to spot new options, then re-apply your custom settings.

Yes — that's the main thing to watch for indoors: two MLOs using the same map location, or poorly isolated identical prop hashes, can overlap visually. Our product pages list the exact location each MLO uses — check that no other installed module occupies the same spot before going live.

The in-game resmon command (or txAdmin's Performance tab) shows CPU time per resource, per tick. A well-optimized script typically stays under 0.01-0.05 ms at idle. Every one of our scripts is tested on our own showcase servers before release, specifically to catch this kind of issue early.

Most of our scripts rely on standard exports and can be adapted to a custom framework through a dedicated bridge. Each product page lists the officially supported frameworks — if your setup falls outside those, reach out before buying so we can confirm compatibility.

After payment via Tebex, delivery depends on how each module is configured: automatic delivery to the server linked to your Cfx account for escrowed scripts, or a download link for open-source modules. Details are listed on each product page.

The standard license covers one production server. Contact us for a multi-server or partner license.

Refunds follow Tebex's policy, available from your Tebex account at time of purchase.

Yes — beyond our catalog, KEOPS Studios also builds custom modules and adapts existing products to specific needs. Describe your project on our Discord and we'll quickly tell you if it's doable.