Why do players see different weather in FiveM?

Each client runs its own weather unless a sync script sets it from the server. Install one weather/time sync resource.

How do I make a blackout?

Call SetArtificialLightsState(true) on every client, usually through your weather sync script’s blackout command.

Why does my weather keep changing back?

Two resources set weather. Keep one sync resource and disable weather features in the others, including admin menus.

FiveM Weather & Time Sync: Weather Types, Blackouts and Scripts

Out of the box each FiveM client runs its own clock and weather, so one player sees a sunny afternoon while the player next to them drives through a storm at midnight. A weather and time sync script makes the server the source of truth and pushes the same sky to everyone — and gives staff commands for events, blackouts and “always noon” servers.

Short answer: A sync script keeps the current weather and time on the server and sends them to clients, which apply them with natives such as SetWeatherTypeOverTime / SetOverrideWeather and NetworkOverrideClockTime. GTA V weather types include CLEAR, EXTRASUNNY, CLOUDS, OVERCAST, RAIN, CLEARING, THUNDER, SMOG, FOGGY, XMAS, SNOW, SNOWLIGHT, BLIZZARD, HALLOWEEN and NEUTRAL. Use one sync resource only.

#Why sync matters

Roleplay depends on shared reality: a chase at night, a storm that makes the roads slippery, a sunrise meeting. If each player sees different conditions, visibility and driving differ, and scenes stop making sense. Sync also stops the random client-side weather changes GTA V does on its own.

#GTA V weather types

Weather	Notes
`EXTRASUNNY`, `CLEAR`	Bright, the default for most servers
`CLOUDS`, `OVERCAST`, `SMOG`, `FOGGY`	Grey days and low visibility
`RAIN`, `THUNDER`, `CLEARING`	Wet roads, lightning, drying after rain
`SNOW`, `SNOWLIGHT`, `BLIZZARD`, `XMAS`	Winter; `XMAS` adds snow on the ground
`HALLOWEEN`	The Halloween event look
`NEUTRAL`	A flat, neutral setting

#The natives a sync script uses

client.lua — applying state from the server

RegisterNetEvent('weather:apply', function(weather, hour, minute)
    SetWeatherTypeOverTime(weather, 15.0)  -- blend over 15 seconds
    Wait(15000)
    ClearOverrideWeather()
    ClearWeatherTypePersist()
    SetWeatherTypePersist(weather)
    SetWeatherTypeNow(weather)
    SetWeatherTypeNowPersist(weather)

    NetworkOverrideClockTime(hour, minute, 0)
end)

Real sync scripts also re-apply the state periodically and on join, and blend smoothly between weathers. That is why using a maintained resource is usually better than writing your own.

#Features worth having

Blackout: SetArtificialLightsState(true) turns off city lights — great for events and power-outage roleplay.
Freeze time: keep a permanent time of day for screenshot or event servers.
Dynamic weather: random changes on a timer, avoiding snow in summer.
Staff commands: /weather, /time, /blackout behind ACE permissions.
Interior handling: some scripts force clear weather inside interiors.

#Avoiding conflicts

Many resources change weather on their own: frameworks, admin menus, vMenu’s time and weather options, event scripts. If weather flickers or snaps back, two of them are fighting. Pick one owner and disable weather features in the rest — vMenu, for example, has its own weather sync that should be turned off when another script handles it.

Synchronising weather and time on a FiveM server