Before You Begin#
Requirement | Status | Download |
|---|---|---|
| Required | |
|
Documentation
Everything you need to get Quasar Zone Weather running: two dependencies, one SQL import, and three panels.
Requirement | Status | Download |
|---|---|---|
| Required | |
|
Required |
MySQL database | Required | Nothing works until the schema is imported |
Framework | Optional | ESX, QB — also runs standalone |
The database is not optional here. Zones, settings and the saved weather all live there. There is no
data/*.jsonany more, which is what makes updating safe.
Quasar Zone Weather is linked to your CFX Portal account.
Sign in to the CFX Portal using the same account used during checkout, then open Granted Assets and locate Zone Weather in your asset library. Download the latest version and extract the archive.
After extracting the download, you should have the following folder:
qs-zoneweatherNever rename the resource folder. It must remain qs-zoneweather, otherwise the exports and the bridges other scripts call will not resolve.
Move the qs-zoneweather folder into your server’s resources directory. Although the resource can be placed anywhere inside the folder, keeping Quasar resources organized inside their own directory is recommended.
A typical installation looks like this:
resources/
└── [quasar]/
└── qs-zoneweather/Then add it to your server.cfg:
ensure oxmysql
ensure ox_lib
# Framework
ensure es_extended
# ensure qb-core
ensure qs-zoneweatherThe loading order matters. Always start oxmysql and ox_lib before qs-zoneweather.
Open your preferred database manager (such as phpMyAdmin, HeidiSQL, DBeaver, or Navicat), select your server’s database, and execute sql/database.sql.
:warning: Nothing works until you do. Zones, settings and the saved weather all live in the database.
The file also ships two example zones. Delete them in the creator once you have drawn your own.
Add these to your server.cfg:
add_ace group.admin command.weather allow # live control panel
add_ace group.admin command.weatherconfig allow # settings panel
add_ace group.admin command.weathercreator allow # zone creatorOn ESX and QB you can grant access with a framework group instead — set Permission mode to Framework groups in /weatherconfig and list them there.
After completing the installation, restart your FiveM server.
Join your server with an administrator account and run:
/weathercreatorIf the zone creator opens, Quasar Zone Weather has been installed correctly. Draw your first zone, set its cycle, and delete the two examples.
The Three Panels
Command | What it does |
|---|---|
| Live control. Force a weather on one zone or all of them, lock it, reroll it, move the clock, cut the power |
| Draw zones on the GTA map, or walk the border and capture each point in world |
| Every value the resource reads, editable in game and saved to the database |
config/config.lua holds only what has to be known before the server starts: the debug switch and which framework you run.
Everything else moved into /weatherconfig, so an update never wipes your tuning — including renaming the commands themselves.
These paths are all in escrow_ignore, so an update never touches them:
Path | What it holds |
|---|---|
| The two pre-start values |
| Every text, in fourteen languages |
| The framework adapters — add your own next to |
| Your own code, loaded before the resource’s own files |
| The schema |
client/custom/hud.lua is where you hook your HUD so it hides while a panel is open.
The resource answers the events and exports that cd_easytime and qb-weathersync scripts expect, and provides both names — so scripts written against either keep working with no changes.
Both bridges can be switched off in /weatherconfig if you actually run one of them alongside this.