Troubleshooting

Run env:doctor in the server console first. It reports your persistence, conflicts (including vMenu), store/automation status, and current state - and answers most of the questions below. (There is no framework line on purpose: admin access is a plain ACE, so there is no framework detection to report.)

Symptoms and fixes

Symptom	Fix
Two weathers / day-night flicker	Another sync script is fighting (vMenu, or qb-weathersync / cd_easytime / vSync). Keep one - stop the other. Disable vMenu sync (see Installation).
Time or weather wrong, or will not change	Check Config.ControlTime / Config.ControlWeather are true. Confirm no second script.
"Access denied" opening /environment or on commands	You are not in the ACE. On your own server, add yourself: add_principal identifier.fivem:YOUR_ID group.admin. Pasted in the console it works immediately but is lost on restart - put it in server.cfg to make it permanent. The server console always has access.
Store event / env:store did nothing	Test without your store first: run env:store storm_event 5 test in the server console. If the sky changes, the resource works and the problem is your Tebex delivery or package-to-preset mapping. Run env:doctor and read the store/automation line.
Time resets after restart	Config.Persist must be true (default). It saves via FiveM KVP.
New players see the wrong sky for a moment	They sync on join automatically; if it persists, you have a competing script.
Weather "snaps" instead of blending	That is a competing script; dzr-environment always blends (WeatherTransitionSeconds).
One player's sky looks wrong	Have them run /env:resync - it re-pulls and re-applies the live sky for that player only.

Support boundary

The write exports (SetTime, SetWeather, and friends) are meant for trusted server-side scripts. Never wire one straight to a raw client event without your own permission check.

SuppressSync is a client-side visual pause (for cinematics and character select) - it does not stop server authority.

If something looks off, run env:doctor first; it answers most setup questions. Still stuck? Reach us on the DZR Discord with the env:doctor output.