QBCore Frameworkqbcore.netCommunity docs
On this page

Updated 2026-10-11 · 2 min read

qb-weathersync: synchronized weather and time

qb-weathersync manages shared weather, in-game time, weather transitions, time freezing and blackouts. This guide follows commit f7ae442.

Installation

Start qb-core before qb-weathersync. Remove or disable conflicting time/weather owners before enabling the resource. Confirm clients receive the current state after joining or restarting the resource.

Configuration

The real config.lua exposes:

KeyDefaultPurpose
Config.DynamicWeathertrueAutomatic transitions
Config.StartWeather'EXTRASUNNY'Initial weather
Config.BaseTime8Initial time
Config.TimeOffset0Time adjustment
Config.FreezeTimefalseWhether clock advances
Config.BlackoutfalseBlackout state
Config.BlackoutVehiclefalseBlackout behavior for vehicles
Config.NewWeatherTimer10Minutes between weather changes
Config.DisabledfalseDisable resource-controlled weather
Config.RealTimeSyncfalseReal-world time synchronization
Config.AvailableWeatherTypesWeather stringsAllowed weather values
Config.DynamicWeather = true
Config.StartWeather = 'EXTRASUNNY'
Config.NewWeatherTimer = 10
Config.RealTimeSync = false

Server controls

The server code registers API names such as setWeather, setTime, setBlackout, setTimeFreeze, setDynamicWeather and status helpers getWeatherState / getTime. The code also checks permissions before admin-triggered weather/time changes (admin or appropriate ACE/console authority).

Do not accept a client-chosen weather value/time as permission to change global server state. Integrations should use the supported server-side interface and their own authorization checks.

Troubleshooting

SymptomCheck
Weather changes but resetsA second weather owner, DynamicWeather and server restart defaults
Time never progressesFreezeTime or RealTimeSync
Players see different weatherResource startup, sync request event and client console
Blackout affects unexpected systemsBlackout and BlackoutVehicle
Admin command deniedQBCore permissions and ACE, not a client-side job label

Update checklist

  1. Pin installed upstream version and keep only one time/weather owner.
  2. Test state sync on first join, reconnect and resource restart.
  3. Test admin/unauthorized access to weather and time-changing paths.
  4. Verify time freeze, real-time sync and blackout independently.

Sources

Repository · Config · Server exports and commands

Found an issue in this guide?

Send the page URL, the affected example, and a source or reproduction to the site maintainer. For a server or resource problem, use the support guide.

On this page

Leonida RP server website built with RPWebsite
RPWebsite

Advertisement · RPWebsite

Want a website for your server?

Launch a site with live player status, rules, and a join button in minutes.

Build your website