> For the complete documentation index, see [llms.txt](https://docs.sonoransoftware.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.sonoransoftware.com/store/sonoran-station-displays/in-game-clock.md).

# In-game Clock and Weather

The header uses the local client's GTA/FiveM world clock, not the computer clock, server time, or Sonoran CAD time.

## Time

```lua
Config.TimeFormat = 12
Config.ShowClockSeconds = false
```

`TimeFormat` accepts `12` or `24`. Twelve-hour output converts midnight and noon to `12` and adds `AM` or `PM`. Twenty-four-hour output is zero-padded. `ShowClockSeconds` adds seconds when enabled.

The client checks the GTA clock at 250 or 500 millisecond intervals and sends an update only when the formatted value changes. Different clients can briefly show different values if another resource changes time locally rather than synchronizing it server-wide.

Administrative webhooks, persistence metadata, and audit logs use real-world UTC where documented. They do not reuse this in-game clock.

## Weather

```lua
Config.Weather = {
    enabled = true,
    temperatureUnit = "F",
    updateInterval = 2000
}
```

The weather label follows GTA's current weather type. Temperature is an estimate chosen for that game-weather condition; it is not real-world meteorology or a weather API. `temperatureUnit` accepts `F` or `C`.

Disable `Weather.enabled` to remove the weather indicator. Lower update intervals add client polling without making the underlying GTA weather more accurate.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.sonoransoftware.com/store/sonoran-station-displays/in-game-clock.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.