> For the complete documentation index, see [llms.txt](https://docs.nm1scripts.in/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.nm1scripts.in/classy-series/advanced-scoreboard/full-configuration-guide/color-presets/seasonal-presets.md).

# Seasonal Presets

Below are **5 seasonal color themes**, each named and designed to match the mood of the season.\
All themes are **production-ready** and can be directly used in `Config.Colors`.

***

### 1. Winter Frost (Christmas / New Year)

Clean, icy tones with festive contrast. Works perfectly for Christmas and New Year events.

```lua
Config.Colors = {
    PrimaryBackground   = "#0A1220",
    SecondaryBackground = "#111B30",
    AccentColor         = "#7DD3FC",
    TextColor           = "#E0F2FE",
    HeaderColor         = "#BAE6FD",
    ButtonHover         = "#1B2A4A",
    SuccessColor        = "#A7F3D0",
    DangerColor         = "#F87171",
    BorderColor         = "#2A3B5E",
}
```

***

### 2. Autumn Ember (Halloween / Fall)

Dark, warm tones with an eerie atmosphere. Ideal for Halloween events.

```lua
Config.Colors = {
    PrimaryBackground   = "#120B08",
    SecondaryBackground = "#1F140E",
    AccentColor         = "#F97316",
    TextColor           = "#FFF7ED",
    HeaderColor         = "#FED7AA",
    ButtonHover         = "#2B1A12",
    SuccessColor        = "#FDBA74",
    DangerColor         = "#EF4444",
    BorderColor         = "#3A2418",
}
```

***

### 3. Spring Bloom (Fresh / Community Events)

Bright yet soft colors for seasonal resets, community events, or server launches.

```lua
Config.Colors = {
    PrimaryBackground   = "#0E1512",
    SecondaryBackground = "#16201A",
    AccentColor         = "#22C55E",
    TextColor           = "#ECFDF5",
    HeaderColor         = "#BBF7D0",
    ButtonHover         = "#1F2E25",
    SuccessColor        = "#4ADE80",
    DangerColor         = "#FB7185",
    BorderColor         = "#2F4F3E",
}
```

***

### 4. Summer Heat (High-Energy RP)

Vibrant and energetic. Perfect for action-heavy or crime-focused seasons.

```lua
Config.Colors = {
    PrimaryBackground   = "#140B0A",
    SecondaryBackground = "#221210",
    AccentColor         = "#FACC15",
    TextColor           = "#FEFCE8",
    HeaderColor         = "#FEF08A",
    ButtonHover         = "#2F1C18",
    SuccessColor        = "#FDE047",
    DangerColor         = "#EF4444",
    BorderColor         = "#3F2622",
}
```

***

### 5. Monsoon Night (Rainy / Dark RP)

Moody and cinematic, suited for serious or realism-focused servers.

```lua
Config.Colors = {
    PrimaryBackground   = "#0A0E14",
    SecondaryBackground = "#121926",
    AccentColor         = "#38BDF8",
    TextColor           = "#E5F3FF",
    HeaderColor         = "#BAE6FD",
    ButtonHover         = "#1B2436",
    SuccessColor        = "#60A5FA",
    DangerColor         = "#F87171",
    BorderColor         = "#2A3448",
}
```

***

####


---

# 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.nm1scripts.in/classy-series/advanced-scoreboard/full-configuration-guide/color-presets/seasonal-presets.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.