> For the complete documentation index, see [llms.txt](https://theobsidianstudio-1.gitbook.io/theobsidianstudio-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://theobsidianstudio-1.gitbook.io/theobsidianstudio-docs/assets/obs_adminmenu/dynamic-microclimates-and-zone-weather.md).

# DYNAMIC MICROCLIMATES & ZONE WEATHER

Break free from rigid, global weather synchronizations. The groundbreaking Microclimate engine allows you to engineer localized weather systems locked to specific physical coordinates on the map, creating unparalleled immersion for your roleplayers.

***

### 🌍 Engineering an Atmospheric Anomaly

1. Verify `Config.ZoneWeatherEnabled = true` is active within your configuration.
2. Navigate to the `Config.ZoneWeather` matrix.
3. Establish your atmospheric zones by defining the `x` and `y` vectors, the `radius` of the anomaly, and the targeted `weather` state.

```lua
{
    name    = 'Mount Chiliad Summit',
    x       = 502.0,
    y       = 5604.0,
    radius  = 1400.0,
    weather = 'BLIZZARD',
    enabled = true,
}
```

### 🔄 Seamless Edge Interpolation

When a player's physical coordinates intersect with the defined radius, their local client weather does not snap violently. Instead, the engine utilizes seamless edge interpolation to naturally transition their environment into the designated atmospheric state.

This architecture is perfect for establishing permanent, howling blizzards on mountain peaks, or perpetual, eerie fog within the swamplands. Administrators maintain supreme authority to manipulate, override, or delete these microclimates live via the **World Panel** inside the dashboard.


---

# 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://theobsidianstudio-1.gitbook.io/theobsidianstudio-docs/assets/obs_adminmenu/dynamic-microclimates-and-zone-weather.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.