FAQ
Common questions about installing, configuring and licensing TrapNexus.
Do I need to configure the framework or inventory?
No. Both are detected at start, and the console prints what was found. A standard QBCore or ESX Legacy install needs no configuration for detection to work.
Do I need OneSync?
Yes, and it is not optional. Sale validation uses server-side entity natives, which do not function without it.
Why is every item the same quality?
Per-item quality needs an inventory that stores metadata. The native ESX inventory does not, so quality falls back to a flat value. See Inventory integration.
Can I edit the configuration?
Yes. Configuration, the database schema, the item packs and the documentation are left readable and editable. The client and server Lua are encrypted through escrow.
Note that for products, recipes, zones and suppliers, config.lua is a seed used on first
start only — after that the database is authoritative and those are edited in game. See
Configuration.
How many servers does one purchase cover?
Up to three that you personally own and operate, so a development or staging server does not need a second purchase.
Do I need Discord?
No. Discord is where support and community happen, and it is optional. The resource neither requires nor contacts it, and nothing about installing or running it depends on being in the server.
Can I add my own drugs and recipes?
Yes. Products and recipes are data, created and edited in the administration console. Recipes take any number of ingredients and produce any number of outputs. You will also need to add the corresponding items to your inventory's own item definitions.
Does it work alongside another drug script?
Nothing prevents it, but two economies running in parallel usually means players farm whichever one pays better, and neither is balanced against the other. If you are migrating, run them side by side only briefly.
Will my tuning survive an upgrade?
Yes. Definitions in the database are not overwritten by a new version's seed values, and settings added by a release arrive at their defaults without disturbing existing ones. See Upgrading.
What does the alpha label mean?
The loop is complete and has been tested end to end on live servers, but it is early software: expect bugs, expect formats to change between versions, and treat the roadmap as intentions rather than commitments. Known limitations are published in full on the product page.
Can I get a refund?
Refunds are handled through the store that processed your payment, alongside the published support and refund policy. If something does not work as described, raise it first — most refund requests turn out to be a problem that can be fixed.
