FiveM scripts setup guide
One guide for five licensed FiveM resources: Live Appearance, Car Meet, Sync Time and Weather, State Fuel and Daily Rewards. Each is sold licensed and bound to one server per key by default. This guide covers what each script does, then the one shared install and license pattern all of them use.
Live Appearance
Clothing and heritage editor
A clothing and heritage editor with live preview, built on ox_lib. Saved outfits persist per character in the database, and barber and clothing stores can charge configurable fees through clean exports.
Car Meet
Recurring car-meet events
A recurring car-meet event: a configurable meet zone with props and lighting, scheduled or admin-triggered, with server-validated attendance and a random, database-backed crowd-favorite pick at the end of every meet.
Sync Time and Weather
One authority for time and weather
One authority for time and weather, with every client kept in sync: smooth weather transitions, freeze and blackout commands, a forecast queue and a small admin API. 0.00ms idle, zero dependencies.
State Fuel
Statebag-driven fuel
A statebag-driven fuel system: jerry cans, electric vehicles, fuel stations and per-class consumption, with exports that drop in where ox_fuel sits. Fuel rides on entity statebags, so it survives across resources and stays in sync.
Daily Rewards
Daily login streaks and milestones
A daily login reward with streaks, plus milestone rewards for time played. Fully configurable reward tables (cash, items, roles), database-backed, with an in-game claim panel.
Install
Install any of these scripts
All five follow the same pattern. Extract the zip from your delivery page into your server's resources folder, then add an ensure line for it in server.cfg using the folder name from the zip.
-- server.cfg
ensure <resource-folder-name-from-the-zip>Each script validates its license on boot through the same license API. The first call from a server binds the activation, and each key is bound to one server by default.
License
Activate and move a key
To move a script to a new server, free the old activation first, then validate from the new one.
POST /api/license/validate { "key": "...", "product": "al-appearance", "fingerprint": "my-server-ip-or-cfx" } # moving servers: free the old slot, then validate from the new one POST /api/license/deactivate { "key": "...", "fingerprint": "old-server-fingerprint" }
Product SKUs: al-appearance, al-carmeet, al-world, al-fuel, al-rewards.