sql/database.sql was not imported, or was imported into a different database from the one oxmysql connects to. Import it into the right one and restart. Until then nothing is saved: zones, settings, the weather and the clock all reset on every restart.

Read the server console: it prints the exact add_ace line that would let that player in. Nine times out of ten the line is in server.cfg but the server was not restarted, or the player is not in group.admin. On QBCore and Qbox use the ACE lines; only ESX groups are recognised on their own. Each panel has its own node, so having one does not open the other two.

Your framework starts after Zone Weather, and detection only sees what is already running. Move its ensure above ensure qs-zoneweather, or set Config.Framework by hand in config/config.lua.

The map tiles live in web/images/. If that folder is missing or half-copied the map has nothing to draw. Copy the whole resource again from the download and restart it. The same applies to a panel that opens as an empty page.

Another resource is setting the weather too — usually qb-weathersync, cd_easytime, vSync or Renewed-Weathersync, sometimes a housing or event script that forces its own sky. Remove it: Replacing Weather Scripts walks through it. If the flicker only happens while driving along a border, raise Border hold in Settings → Weather.

Stand in it and run /weatherinfo. If it says current zone: none, you are outside every zone and get the Outside every zone weather. The usual causes:

• The zone is switched off (Active in the creator).

• You are above its ceiling or below its floor — in an aircraft or a deep tunnel.

• Another zone overlaps it with a higher priority. /weatherzones lists every zone with its priority.

• A housing or interior script paused the sync — sync enabled: false in /weatherinfo. It resumes when that script releases it.

Either it is locked (the control panel shows it; unlock it, or it lets go on its own after the lock length), its cycle is empty so it stays on its default for good, or every entry in the cycle is a manual weather the server never draws.

Correct behaviour. A tsunami, a blood moon and the dark hour cannot run in a single zone. Accept the offer to apply it everywhere, use Set every zone to on the Overview tab, or call setAllZonesWeather from a script.

It is on its way. Disasters go through an emergency alert first: the sirens sound and the weather changes when the warning time runs out — two minutes by default. Setting another weather on that zone during the warning calls it off. To start disasters immediately, set Warning time to 0 in Settings → Emergency alerts.

Correct behaviour. Both are manual-only so they never strike a server at random. Start them from the control panel or an export.

It says why: the ID uses something other than letters, numbers and underscores or already exists, the zone has fewer than three points or more than the limit, or the server has reached its zone limit. Both limits are in Settings → Zones.

Real time is on in config/config.lua. Set Config.Time.realtime = false and restart to set the clock by hand again.

Check the Time tab of /weather: the clock may be frozen or its speed set to 0. If the time jumps between two values, another resource is also setting it — remove it, or turn off Control the clock so only that one does. A zone with its own clock keeps it regardless of the server clock.

A blood moon is running: it moves the clock to night and slows it down, then gives it back when it ends. Turn off Hold it at night in Settings → Blood Moon to leave the clock alone.

Lower Funnel quality to Low in Settings → Tornado, then Smoke density, and turn off Debris if needed. From far away the funnel is already drawn at half.

Lightning. During a supercell, a bolt that hits the ground throws everything around it and can blow up vehicles a few metres away. Tune it in Settings → Thunderbolt: lower Blast force, turn off Blow up vehicles, or turn off Blast wave entirely. Ordinary thunderstorms do not do this — their bolts only light the sky.

Its particle set has not loaded yet. It retries every few seconds and throws nothing until the funnel shows; /weatherinfo says so. If it never appears, put Particle set and Particle name in Settings → Tornado back to their defaults — an invented name draws nothing.

Turn off Swap the moon texture in Settings → Blood Moon. The native behind the red moon has crashed clients on some game builds; everything else about the blood moon keeps working without it.

Run /weatherinfo during it. If the modifier slot says NOT FOUND, the colour file did not load on that client — reconnecting fixes it. If it is found, check Timecycle modifier is still qsw_bloodmoon and Strength is not near zero.

Blackout hits vehicles is on in Settings → Blackout. Turn it off and headlights and emergency lights stay on while the city is dark.

A storm or an earthquake is running somewhere on the map, and storm outages are on. Turn off Outages in storms or Earthquake outages, or lengthen the gaps, in Settings → Blackout.

Check Settings → Emergency alerts: the alerts and the Siren are on, that disaster has its alert switched on, and the volume is not at 0. The siren only plays for players inside the affected zone — everyone else gets a short notice instead.

qs-smartphone has to be running, the player needs an active phone, and they must not have muted the Emergency Alert app on it. A disaster set with a warning time of 0 sends no phone notification, since there is nothing left to warn about.

sql/database.sql was not imported, or was imported into a different database from the one oxmysql connects to. Import it into the right one and restart. Until then nothing is saved: zones, settings, the weather and the clock all reset on every restart.

Read the server console: it prints the exact add_ace line that would let that player in. Nine times out of ten the line is in server.cfg but the server was not restarted, or the player is not in group.admin. On QBCore and Qbox use the ACE lines; only ESX groups are recognised on their own. Each panel has its own node, so having one does not open the other two.

Your framework starts after Zone Weather, and detection only sees what is already running. Move its ensure above ensure qs-zoneweather, or set Config.Framework by hand in config/config.lua.

The map tiles live in web/images/. If that folder is missing or half-copied the map has nothing to draw. Copy the whole resource again from the download and restart it. The same applies to a panel that opens as an empty page.

Another resource is setting the weather too — usually qb-weathersync, cd_easytime, vSync or Renewed-Weathersync, sometimes a housing or event script that forces its own sky. Remove it: Replacing Weather Scripts walks through it. If the flicker only happens while driving along a border, raise Border hold in Settings → Weather.

Stand in it and run /weatherinfo. If it says current zone: none, you are outside every zone and get the Outside every zone weather. The usual causes:

• The zone is switched off (Active in the creator).

• You are above its ceiling or below its floor — in an aircraft or a deep tunnel.

• Another zone overlaps it with a higher priority. /weatherzones lists every zone with its priority.

• A housing or interior script paused the sync — sync enabled: false in /weatherinfo. It resumes when that script releases it.

Either it is locked (the control panel shows it; unlock it, or it lets go on its own after the lock length), its cycle is empty so it stays on its default for good, or every entry in the cycle is a manual weather the server never draws.

Correct behaviour. A tsunami, a blood moon and the dark hour cannot run in a single zone. Accept the offer to apply it everywhere, use Set every zone to on the Overview tab, or call setAllZonesWeather from a script.

It is on its way. Disasters go through an emergency alert first: the sirens sound and the weather changes when the warning time runs out — two minutes by default. Setting another weather on that zone during the warning calls it off. To start disasters immediately, set Warning time to 0 in Settings → Emergency alerts.

Correct behaviour. Both are manual-only so they never strike a server at random. Start them from the control panel or an export.

It says why: the ID uses something other than letters, numbers and underscores or already exists, the zone has fewer than three points or more than the limit, or the server has reached its zone limit. Both limits are in Settings → Zones.

Real time is on in config/config.lua. Set Config.Time.realtime = false and restart to set the clock by hand again.

Check the Time tab of /weather: the clock may be frozen or its speed set to 0. If the time jumps between two values, another resource is also setting it — remove it, or turn off Control the clock so only that one does. A zone with its own clock keeps it regardless of the server clock.

A blood moon is running: it moves the clock to night and slows it down, then gives it back when it ends. Turn off Hold it at night in Settings → Blood Moon to leave the clock alone.

Lower Funnel quality to Low in Settings → Tornado, then Smoke density, and turn off Debris if needed. From far away the funnel is already drawn at half.

Lightning. During a supercell, a bolt that hits the ground throws everything around it and can blow up vehicles a few metres away. Tune it in Settings → Thunderbolt: lower Blast force, turn off Blow up vehicles, or turn off Blast wave entirely. Ordinary thunderstorms do not do this — their bolts only light the sky.

Its particle set has not loaded yet. It retries every few seconds and throws nothing until the funnel shows; /weatherinfo says so. If it never appears, put Particle set and Particle name in Settings → Tornado back to their defaults — an invented name draws nothing.

Turn off Swap the moon texture in Settings → Blood Moon. The native behind the red moon has crashed clients on some game builds; everything else about the blood moon keeps working without it.

Run /weatherinfo during it. If the modifier slot says NOT FOUND, the colour file did not load on that client — reconnecting fixes it. If it is found, check Timecycle modifier is still qsw_bloodmoon and Strength is not near zero.

Blackout hits vehicles is on in Settings → Blackout. Turn it off and headlights and emergency lights stay on while the city is dark.

A storm or an earthquake is running somewhere on the map, and storm outages are on. Turn off Outages in storms or Earthquake outages, or lengthen the gaps, in Settings → Blackout.

Check Settings → Emergency alerts: the alerts and the Siren are on, that disaster has its alert switched on, and the volume is not at 0. The siren only plays for players inside the affected zone — everyone else gets a short notice instead.

qs-smartphone has to be running, the player needs an active phone, and they must not have muted the Emergency Alert app on it. A disaster set with a warning time of 0 sends no phone notification, since there is nothing left to warn about.