Quickstart

Every Mic script goes onto a server the same way. This page is the part they all share; each script’s own Installation page adds only what is particular to it.

1. Download it from your Cfx.re portal

After buying on mic.tebex.io, the script appears in the Cfx.re portal under Granted Assets, on the Cfx.re account you used at checkout. Download it from there — that is also where every update will appear.

2. Put the folder in your resources

Unzip it into your resources folder. A bracketed folder such as resources/[mic]/ keeps things tidy and is started as a group. If the script comes with a props companion (Arcade Machines, Crypto Mining…), both folders go in.

3. Start it after what it depends on

In server.cfg, a script’s ensure line goes below the resources it leans on: oxmysql, your framework (es_extended, qb-core or qbx_core), your inventory and your target. Starting a script before its framework is the single most common reason for a red line in the console.

4. Database and items

Some scripts create their tables on their own, others ship a .sql file to import once. Scripts that use items ship their definitions and images in the resource, ready for ox_inventory, QBCore and ESX. The script’s Installation page says which applies and where the files are.

5. Read the config before you open

Every script has an open config.lua (and usually an open locales/ and bridge/ folder). The Customization page of each script lists every option and what it decides.

Two FiveM habits that save an hour

restart does not re-read fxmanifest.lua. After adding or updating files, run refresh in the server console first, then restart the resource — or simply restart the server.
Update the server artifacts. Escrowed resources and modern natives need a recent FXServer build; a server that is a year behind is where odd errors come from.

What “the bridge” is

Most scripts have a bridge/ folder. It holds every call the script makes to another resource — framework, inventory, target, notifications, phone, fuel, keys. It is left open on purpose: if your server uses something custom, you adapt one small file there instead of waiting for an update.