Skip to main content

Configuration

All config files live in configs/ and are not escrowed - edit freely.

config.lua

Season

Framework & Inventory

Auto-detection picks the first running resource. Set explicitly if you have both installed.

XP & Tiers

Theme

Passive XP

Players earn XP automatically for being online and active.
The daily play time counter (dailyPlaySecs) only increments when XP is actually awarded - it does not tick while the player is AFK or has hit the daily cap.

Discord Webhook

Premium Purchase


quests.lua

Tier Names

Quest Definition Fields

Categories

Quests belong to one of three categories, which determine their reset period:

Job-Restricted Quests

Add a job field to any quest in any category. The job name must match Player.PlayerData.job.name exactly (e.g. 'police', 'mechanic', 'ambulance').
The UI shows a blue job badge (e.g. Police) inline next to the category tag. Progress is silently rejected server-side if the player is on the wrong job.

tiers.lua

Defines rewards for each tier on the Free and Premium tracks.
Reward type fields: All rewards also need label (UI display name) and rarity ('common' / 'rare' / 'epic' / 'legendary'). Only Config.Season.max_tiers entries are read; extras are ignored.

quests_handler.lua (client-side)

Detects in-game events on the client and calls:
The server validates and caps the amount. Use standard FiveM client natives here.

quests_handler_sv.lua (server-side)

Use the export from another resource:
For job quests, trigger the export from your job resource when the relevant action occurs. Job validation is automatic.