> For the complete documentation index, see [llms.txt](https://docs.candelacharts.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.candelacharts.com/toolkits/block-concepts-tm/visuals.md).

# Visuals

### Drawing Modes <a href="#user-content-drawing-modes" id="user-content-drawing-modes"></a>

You can change how each block is rendered by selecting from the following Drawing Modes:

1. **Basic Mode:** The standard display. It draws a clean, shaded rectangular box highlighting the entire block. Best for a straightforward, high-level view of key support and resistance levels.
2. **OTE Mode (Optimal Trade Entry):** Specifically targets and shades the "Optimal Trade Entry" area within the block. You can toggle the **Show OTE Box** setting to explicitly display the OTE zone box while this mode is active.
3. **Quadrants Mode:** Divides the block into four equal horizontal sections (0%, 25%, 50%, 75%, and 100%) for granular price action analysis.
4. **Profile Mode:** Displays a visual distribution profile alongside or inside the block, indicating where the most significant activity occurred during its formation.

### Additional Features <a href="#user-content-additional-features" id="user-content-additional-features"></a>

* **Consequent Encroachment (Mean Line):** The **Show Mean** setting allows you to draw a highly visible line at the exact 50% midpoint of the block, fully customizable in width and style.
* **Hide Overlap:** Automatically removes overlapping blocks from view to keep the chart pristine.
* **Advanced Styling & Labels:** Toggle borders, define line styles, and configure text labels (e.g., "+OB").
* **Extend:** Extend the blocks to the current candle to easily see where historical levels project into current price action.


---

# 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://docs.candelacharts.com/toolkits/block-concepts-tm/visuals.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.
