# Detail Level Toggles

Level: Intermediate

## Goal

Control how much information nodes show in the Graph Editor so authoring, debugging, and review each show the right amount of detail.

## When To Use This

Use detail level toggles when a graph is either too sparse to understand or too dense to scan. They are most useful while building Blackboard-driven nodes, reviewing a shared graph with a teammate, or debugging a path that depends on many values.

The toggles affect editor display. They do not change runtime behavior, Blackboard values, node execution, or saved graph logic.

## Prerequisites

* A graph is open in the Flow Graph editor.
* You understand the difference between graph structure, comments, and runtime data previews.
* Debug Context is set when you want summaries or values to resolve against a scene object.

## Where To Find It

The Graph Editor header includes detail toggles such as `Summary`, `Comment`, and `Value`. Project defaults can be configured in FlowCore Settings, but the editor toggles are the fastest way to change the current reading mode.

## Workflow

1. Start with `Summary` on.
   * Use Summary as the normal graph reading layer.
   * It shows compact information such as selected instruction behavior, key paths, or important node settings.
   * Leave it on when authoring or reviewing unless you are intentionally checking only the graph shape.
2. Turn `Value` on while binding data.
   * Use Value when you are choosing Literal, Blackboard, payload, or Target sources.
   * Keep it on while verifying scope, index, and key fields.
   * Pair it with Debug Context so Local and Scene Blackboard previews resolve against the intended process.
3. Use `Comment` for design intent.
   * Comments should explain why a branch exists, what a designer should preserve, or what a gameplay rule means.
   * Avoid using comments as a live runtime log. Comments become stale when they describe temporary state.
4. Switch modes for the task.
   * For first setup, use `Summary` on, `Value` on, and `Comment` optional.
   * For debugging, use all three toggles so you can see path, value, and design intent together.
   * For a walkthrough or review, use `Summary` and `Comment` on, then turn `Value` off if values distract from structure.
5. Save team defaults deliberately.
   * If the team prefers a default reading mode, configure it in FlowCore Settings.
   * Keep local temporary changes in the editor until the team agrees they should become defaults.

## What Changes

* `Summary` changes whether nodes show compact operational hints.
* `Comment` changes whether node comments are visible in the graph.
* `Value` changes whether editable value fields and previews are shown.
* The toggles affect editor density only.
* They do not enable, disable, reorder, or execute nodes.

## Verify the Result

Use the Hello World graph as a quick check:

1. Open the graph that reads Local Blackboard key `Say`.
2. Set Debug Context to the GameObject with `FlowCoreProcess`.
3. Turn `Summary` on and confirm the `Action` node shows useful path or instruction information.
4. Turn `Value` on and confirm the `Log String` value source can be inspected.
5. Turn `Value` off and confirm the graph becomes easier to scan without changing behavior in Play Mode.

## Common Mistakes

* Turning off `Summary` and then missing unresolved Blackboard path hints.
* Turning off `Value` while trying to confirm scope, index, or key binding.
* Writing comments that duplicate node labels instead of explaining intent.
* Treating a hidden value as disabled runtime logic.
* Saving a very sparse default that makes onboarding harder for new users.

## Related

* [Graph Editor UI](/flow-core-docs/documentation/editor-guide/graph-editor.md)
* [Debug Context](/flow-core-docs/documentation/editor-guide/debug-context.md)
* [Graph Debugging](/flow-core-docs/documentation/troubleshooting/graph-debugging.md)
* [FlowCore Settings](/flow-core-docs/documentation/reference/flow-core-settings.md)


---

# Agent Instructions: 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:

```
GET https://flow-core.gitbook.io/flow-core-docs/documentation/editor-guide/detail-level-toggles.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.