Stop-loss

A stop in a signal is required, and there must be exactly one. Without a stop line the signal is not recognized, and on the subscribers' side a futures signal without a stop is skipped by default — so the stop always has to be written.

Keywords

At the start of a line, case does not matter: sl, sl targets, stop, stop loss, stop-loss, stop targets, стоп. Стоп-лосс: and Стоп лосс: work too. After the word comes a colon, a space or a hyphen: Stop: 82900, SL 82900, SL - 82900.

Two ways to set the stop

Way	Example	How it is calculated
By price	Stop: 82900	Exactly as written
By a whole percentage	SL: 3%	From the average entry price, in the right direction automatically: below for LONG, above for SHORT

Right and wrong

Right	Wrong	Why
Stop: 82900	Stop: 82900 and below SL: 83000	Several stops are not supported
SL: 3%	SL: 0.5%	The percentage must be whole; for tight stops write a price
SL: 2%	SL: 0%	The percentage must be greater than zero
Stop: 82900	Stop: 82900 (-1.2%), Stop: 82900-83000	No percentages, brackets or ranges next to the stop price
Stop: 82900 Not financial advice	Stop: 82900 Risk 1:3	A line without digits is skipped, but a line with a number becomes a second stop

For LONG the stop must be below all entry prices, for SHORT — above. A stop between the entry prices, or on the same side as the targets, is an error with an explanation.

Example with a calculation

A signal with an entry zone and a percentage stop:

#BTCUSDT
Leverage: 10x
Entry: 85000
84200
TP: 87000
SL: 3%

Average entry price: (85000 + 84200) / 2 = 84600. The targets are above the entry, so this is a LONG and the stop goes below: 84600 − 3% = 84600 − 2538 = 82062. For a short with the same entries the stop would go above: 84600 + 2538 = 87138.

What happens on the subscriber's side

• The stop from the signal goes into the subscriber's trade; the subscriber can override it with their own settings (Stop-Loss: settings and trigger type).
• A futures signal without a valid stop is by default not executed for a subscriber — they receive: “Signal skipped: the LINEAR signal has no valid stop-loss and the bot is configured to skip such signals (protection against trading without SL). Enable a default SL in the bot settings or include an SL in the signal.” The subscriber decides whether to substitute their own stop or to trade without one (The 'no SL in the signal' policy).
• Stop notifications in the channel cannot be turned off — neither by you nor by subscribers.

Common mistakes and what the bot says

• “Value not found for STOP_LOSS” — there is no stop line, or it contains no number.
• “Unfortunately, we currently do not support multiple Stop Loss orders in a single trade” — two stops (two lines with numbers in the stop block).
• “Stop-Loss: invalid format. Use a price (e.g. 29500) or percentage (e.g. 2%). Received: 0.5%” — a fractional percentage, brackets or a range next to the stop.
• “Stop-Loss percentage must be greater than 0” — 0% was written.
• “Stop-Loss (84500) falls within the entry price range (85000 - 84200). SL must be below entry (for LONG) or above entry (for SHORT). Check the SL price.” — the stop is between the entries.
• “Direction conflict: Take-Profit (87000) is above entry (85000) — like LONG, but Stop-Loss (86000) is also above entry — like SHORT…” — the stop is on the wrong side.
• You need to move the stop of a signal that is already published — /change_sl_to_83500 as a reply to the post. A stop exactly at a subscriber's entry price ends up in “skipped”: place it slightly below the entry for LONG or slightly above it for SHORT.