Documentation
How to remove qb-weathersync, cd_easytime, vSync or Renewed-Weathersync before installing Zone Weather, and why the housing and interior scripts that depend on them keep working.
Zone Weather (qs-zoneweather) owns the sky and the clock. Every other weather or time script does the same job, and two of them running at once rewrite each other's sky and clock several times a second — the weather flickers between two values and the sun jumps. This page takes the old one out and explains why the scripts that depended on it keep working.
Resource | Usually found on | What to do |
|---|---|---|
|
QBCore and Qbox, installed by default. |
Remove. Zone Weather answers its events and takes its name, so scripts written for it keep working. |
| Any framework. | Remove. Zone Weather answers its events and exports and takes its name. |
| Any framework. | Remove. There is no bridge for these: a script that calls their events or exports by name needs pointing at Zone Weather's exports. |
Real-time clock scripts | Any framework. | Remove. Set |
Disaster and storm scripts | Any framework. | Remove anything that floods the map, spawns tornadoes or forces the weather — Zone Weather does each of those itself. |
Zone Weather declares
provide 'qb-weathersync'andprovide 'cd_easytime'. A resource that lists either one as a dependency starts normally with only Zone Weather installed.
Stop the server, or stop it from the server console:
stop qb-weathersync
# stop cd_easytime
# stop vSyncDelete — or comment out — the line that starts it:
# ensure qb-weathersync
# ensure cd_easytimeOn QBCore it usually starts with the whole [qb] folder through ensure [qb]. In that case the line stays: delete the qb-weathersync folder instead, or move it out of [qb].
Remove the old resource's folder from resources/. Keeping it on disk is harmless only if nothing starts it.
Follow Installation, then restart the server. The console should show Zone Weather's start-up lines and nothing from the old script.
Housing, interiors, jail, character creation and admin menus often talk to the weather sync — to pause it inside a building, to ask for the current time, or to set the weather from a menu. Zone Weather answers all of these under the old names:
Old script | What is answered |
|---|---|
qb-weathersync | Client: |
cd_easytime | Client: |
Pausing works the way it always did: a house that calls DisableSync or PauseSync stops Zone Weather applying the weather for that player — and, with cd_easytime's hour argument, holds their clock there — until it calls the matching resume.
The old scripts' chat commands, such as qb-weathersync's /time, /freezetime and /blackout, are not recreated. All of them live in the /weather control panel.
If another resource has to stay in charge of part of the job, hand it over from /weatherconfig instead of running both blind:
Situation | Setting |
|---|---|
Another resource owns the time | Time → Control the clock off. Zone Weather leaves the clock alone and keeps the weather. |
You really run qb-weathersync or cd_easytime alongside | Compatibility → switch off the matching bridge, so the two do not answer the same events. |
Another resource must own the weather | Blend → Take ownership of the sky off. The zone cross-fade stops being visible. |