# TP / SL / Trailing Type

**1. Classic – Broker-Managed Stops**

Your TP, SL, and Trailing SL are sent directly to your broker.\
**Pros:** Visible to broker, quick execution. Executed even if the EA is offline or your terminal is disconnected.\
**Cons:** Vulnerable to broker-side manipulation (e.g., stop hunting).\
\
**2. Virtual – EA-Managed Stops (Default)**

Stops are managed **internally** by the EA and hidden from the broker.\
**Pros:** Increased privacy, protection from stop hunting and manipulation.\
**Cons:** Requires EA to stay online and connected. If your terminal crashes or disconnects, your SL/TP won’t trigger until you reconnect.

{% hint style="success" %}

* Use **Virtual** if you're concerned about broker behavior or want extra control.
* Use **Classic** if you're running the EA on a **unreliable VPS**, and want added protection during potential EA interruptions.
* Always **test both options on a demo account** to understand the trade-off between visibility and reliability.
  {% endhint %}

🧠 *Virtual stops = stealth mode. Classic stops = always visible. Choose based on your trading environment and trust in your broker.*


---

# 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://smartchoise.gitbook.io/smartchoise-manual/options/general-and-utility/tp-sl-trailing-type.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.