> For the complete documentation index, see [llms.txt](https://stylizededge-devs.gitbook.io/aqs-doc/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://stylizededge-devs.gitbook.io/aqs-doc/building-menus/coherence-hints.md).

# Coherence Hints

Some settings have real consequences for other settings — turning off Lumen GI without also turning off Virtual Shadow Maps might leave you paying for an expensive shadow technique with little benefit, for example.

AQS deliberately does **not** try to auto-toggle related fields for you. A rule engine that silently flips other settings inevitably gets some combination wrong, and worse, takes away a choice the player or developer made on purpose. Instead, AQS gives you one clean way to communicate the tradeoff and let the player decide.

## How It Works

On any field's entry in `Overrides` (or a `VirtualSettings` entry), set **CoherenceHint**:

```
FieldName: bLumenGI
CoherenceHint: "Disabling this without also disabling Virtual Shadow Maps
                may hurt performance with little visual benefit."
```

At bake time, this is appended to the field's tooltip under a clearly separated "Note:" line. The player hovering or controller-focusing that row sees:

```
Enables fully dynamic, realistic lighting that reacts to changes
in the scene.

Note: Disabling this without also disabling Virtual Shadow Maps
may hurt performance with little visual benefit.
```

## What This Doesn't Do

* It never changes another row's value automatically
* It never disables or grays out another row
* It has zero runtime logic — it's baked text, nothing more

This is intentional. The dev who actually understands their game's specific tradeoffs writes the guidance once; the player reads it and decides with full context. That's a more honest interaction than a system quietly overriding their choice.

## Works on Virtual Rows Too

`FAQSVirtualCVarSetting` has the same `CoherenceHint` field, so a Ray Tracing setting can carry the same kind of guidance as any named field.


---

# 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://stylizededge-devs.gitbook.io/aqs-doc/building-menus/coherence-hints.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.