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:
| Key | Default | Purpose |
|---|---|---|
Config.DynamicWeather | true | Automatic transitions |
Config.StartWeather | 'EXTRASUNNY' | Initial weather |
Config.BaseTime | 8 | Initial time |
Config.TimeOffset | 0 | Time adjustment |
Config.FreezeTime | false | Whether clock advances |
Config.Blackout | false | Blackout state |
Config.BlackoutVehicle | false | Blackout behavior for vehicles |
Config.NewWeatherTimer | 10 | Minutes between weather changes |
Config.Disabled | false | Disable resource-controlled weather |
Config.RealTimeSync | false | Real-world time synchronization |
Config.AvailableWeatherTypes | Weather strings | Allowed weather values |
Config.DynamicWeather = true
Config.StartWeather = 'EXTRASUNNY'
Config.NewWeatherTimer = 10
Config.RealTimeSync = falseServer 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
| Symptom | Check |
|---|---|
| Weather changes but resets | A second weather owner, DynamicWeather and server restart defaults |
| Time never progresses | FreezeTime or RealTimeSync |
| Players see different weather | Resource startup, sync request event and client console |
| Blackout affects unexpected systems | Blackout and BlackoutVehicle |
| Admin command denied | QBCore permissions and ACE, not a client-side job label |
Update checklist
- Pin installed upstream version and keep only one time/weather owner.
- Test state sync on first join, reconnect and resource restart.
- Test admin/unauthorized access to weather and time-changing paths.
- Verify time freeze, real-time sync and blackout independently.
Sources
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.
