> For the complete documentation index, see [llms.txt](https://help.craftsmanplus.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.craftsmanplus.com/play/catalogue/catalogue-editor/header-cells/condition-columns.md).

# Condition Columns

Condition columns define what variable a row of content is associated with\
Once you link a catalogue to a project, they describe the *context* or *rules* that determine which row of the catalogue is active at runtime.

#### **Supported Conditions:**

<details>

<summary><strong>Language</strong></summary>

* `English`
* `French`
* `Arabic`
* *For a full list of supported language codes, click* [*here*](https://docs.aws.amazon.com/translate/latest/dg/what-is-languages.html)

</details>

<details>

<summary><strong>Device</strong></summary>

* **System**
  * `IOS`
  * `MacOS`
  * `Android`
  * `Windows`
* **Platform**
  * `Mobile`
  * `Tablet`
  * `Desktop`
  * `Wearable`
  * `TV`

</details>

<details>

<summary><strong>Time</strong></summary>

* **Hours**
  * `Custom Value (e.g. 12:13-14:22)`
  * `Preset times:`
    * `'Morning' = 06:00–11:59`
    * `‘Afternoon’ = 12:00–17:59`
    * `'Evening' = 18:00–23:59`
    * `‘Night’ = 00:00–05:59`
* **Months**
  * `January`
  * `February`
  * `March`
  * `Etc`

</details>

<details>

<summary><strong>Location</strong></summary>

* **Region**
  * `North America`
  * `Europe`
  * `Marketing Regions:`
    * `ME`
    * `EMEA`
    * `MENA`
    * `APAC`
    * `LATAM`
    * `AMER`
  * `Etc.`
* **Country**
  * `United States`
  * `France`
  * `Etc.`
* **State**
  * `California`
  * `Alabama`
  * `Etc.`
* **City**
  * `Atlanta`
  * `London`
  * `Etc.`
* *For a full list of supported locations, click* [*here.*](https://github.com/dr5hn/countries-states-cities-database/tree/master)

</details>

<details>

<summary><strong>Weather</strong></summary>

* **Celsius**
  * `Custom Value (e.g.`` ``4-10)`
  * `Preset Weather:`
    * `'Very Cold' = <0°C`
    * `‘Cold’ = 0 – 10°C`
    * `'Cool' = 11 – 20°C`
    * `‘Hot’ = 21 – 30°C`
    * `'Very Hot' = >30°C`
* **Fahrenheit**
  * `Custom Value (e.g.`` ``67``-71)`
  * `Preset Weather:`
    * `'Very Cold' = <32°F`
    * `‘Cold’ = 32 – 50°F`
    * `'Cool' = 51 – 68°F`
    * `‘Hot’ = 69 – 86°F`
    * `'Very Hot' = >86°F`
* **Category**
  * `Sunny`
  * `Cloudy`
  * `Windy`
  * `Rain`
  * `Snow`

</details>

Each row in the catalogue combines one or more condition values to define a **variant scenario**.\
When a playable runs, you determine which condition columns are used to then be checked against the user’s environment.


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://help.craftsmanplus.com/play/catalogue/catalogue-editor/header-cells/condition-columns.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.
