Entry Strategy settings
The setting boxes in the Entry Strategy section: what each box does and what each value means. From the window the "?" next to the box opens in the bot.
RSI
RSI LEVEL
What exactly does this condition ask?
The line RSI is compared against. The number the panel keeps ready is 50; whatever you enter in the box, all four RSI conditions are measured against that number.
What is it for?
RSI is a strength measure that moves between 0 and 100. The bot cannot decide on its own that "RSI is high", it needs a boundary line; you set that line. All four of the conditions you can select (above, below, cuts upward, cuts downward) use this single number. In the crossover conditions, the place at which the crossover will count is exactly this value.
Example with numbers
| VALUE | WHAT HAPPENS |
|---|---|
| Level 50 (default), condition "RSI Above Level", RSI is exactly 50.0 at that moment | The condition IS NOT MET. Equality does not pass; RSI must genuinely be above 50. |
| Level 70, condition "RSI Crosses Level Upward", RSI rose from 68 to 71 on the last candle | The condition is met; the crossover is considered to have occurred at the 70 line. |
| The box was left empty | The level is taken as 0. The "above" condition is met on almost every candle and the filter is effectively removed. |
What does it affect?
It affects all four conditions in the RSI box at once and touches no other indicator. Increasing the number makes the signal rarer in "Above the Level" and more frequent in "Below the Level"; decreasing it does the opposite. In crossover conditions, changing the number does not reduce the signal, it moves the PLACE where the crossover is looked for.
What should you watch out for?
CONDITION WINDOW
What exactly does this condition ask?
Works only in RSI CROSSOVER conditions: it says within how many recent candles the crossover may have occurred. The number the panel keeps ready is 1 candle.
What is it for?
A crossover happens and is over in a single moment; if you miss that candle, the opportunity is missed too. This box states how many candles back the bot will look. If you enter 1, the crossover must be on exactly the current candle; if you enter 3, it is enough for it to be on any one of the last three candles. This way you can also evaluate a crossover that the scan did not coincide with.
Example with numbers
| VALUE | WHAT HAPPENS |
|---|---|
| Window 1 (default), condition "RSI Crosses Level Upward" | The signal passes only if the crossover occurred on the very last candle; a crossover on the previous candle does not count. |
| ACTIVE pressed on the toggle next to the box | 2 is written in the box and 2 goes to the bot (measured). In RSI, ACTIVE corresponds to 2 candles — 7 in Fisher, 5 in EMA, 3 in MACD. |
| 3 · the crossover happened 2 candles ago | PASSED. The signal passes; but price may already have moved during those two candles — that is where the risk of a late entry lies. |
| "Above the Level" or "Below" selected as the condition | The box fades and closes in the panel (measured). The engine does not read this number at all either; it only looks at the RSI value of the last candle. |
What does it affect?
It affects only RSI's upward/downward crossover conditions; it does not touch the level box or the other indicators.
What should you watch out for?
EMA
CONDITION WINDOW
What exactly does this condition ask?
Sets within how many recent candles the EMA condition may have occurred. While the toggle next to the box is OFF, 1 goes to the bot; press ACTIVE and 5 goes (measured).
What is it for?
The bot decides at every candle close and looks back; this field states how many candles back it will look. In crossover conditions the window determines how many candles ago the crossover may have occurred.
Example with numbers
In the continuously rising/falling with increasing strength conditions, the window is at the same time the length of the requirement: the first candle of the window must have passed the width threshold, and from that candle to the last one the gap must never have narrowed. In the confirmed crossover it determines for how many candles the fast EMA must have moved in the same direction without interruption.
What does it affect?
| VALUE | WHAT HAPPENS |
|---|---|
| 1 · panel default, toggle OFF | Only the last closed candle is examined. ★ At this value the "Cross Up/Down · Strength Rising" and "Confirmed Cross" conditions produce NO signal AT ALL: in the first, the gap drops to zero on the crossover candle, so the question "did strength increase" necessarily returns no; in the second, there is no second candle to compare. |
| ACTIVE pressed on the toggle → 5 is written in the box, 5 goes to the bot | In crossover conditions, a crossover on any of the last 5 candles counts. In "continuous" conditions, the first of the 5 candles must have passed the threshold and the gap must not narrow at all over the five candles. |
| 10 | In a sustained-strength condition, the 10-candle chain must be entirely unbroken; a narrowing on even a single candle makes the condition fail. Also, this condition gives no signal until 10 candles of history have accumulated. |
What should you watch out for?
It affects all of the crossover, continuously-strong and confirmed conditions. The fast EMA above/below and rising/falling conditions do not use this field.
MACD
MACD STRENGTH FILTER
What exactly does this condition ask?
Sets at least how many times the MACD line's own fluctuation over the last 20 candles the histogram must be. While the toggle is OFF, 0 goes to the bot — i.e. there is no strength requirement; press ACTIVE and the number in the box (1.0 preset) goes (measured).
What is it for?
The histogram is the difference between the MACD and Signal lines; it shows the strength of the move. This box says how large that difference must be for the signal to count. The measure is not a fixed figure: the difference is divided by the MACD line's standard deviation over the last 20 candles and turned into a multiple. That way the same number behaves with similar strictness on different coins and timeframes.
Example with numbers
The larger the number, the more faint and indecisive moves are filtered out.
What does it affect?
| VALUE | WHAT HAPPENS |
|---|---|
| Toggle OFF · panel preset | 0 goes to the bot. There is no magnitude requirement; only the SIGN requirement remains — it is enough for the histogram to be positive on LONG and negative on SHORT. |
| ACTIVE · 1.0 | On LONG, the histogram is required to exceed one times its own usual fluctuation; moves that do not reach this magnitude do not count as a signal. |
| 2.0 | The required magnitude doubles relative to the default; the condition is met far more rarely and signals come only on strong accelerations. |
What should you watch out for?
It comes into play in the crossover + strength conditions (both the one with increasing/decreasing momentum and the one without momentum) and in the continuously increasing/decreasing strength conditions. The above/below zero, confirmed crossover, standalone histogram colour turn and MACD rising/falling conditions never look at this field.
CROSSOVER WINDOW
What exactly does this condition ask?
Sets within how many recent candles the event on the MACD side may have occurred. While the toggle is OFF, 1 goes to the bot; press ACTIVE and 3 goes (measured).
What is it for?
The bot looks back at every candle close; this number says how many candles it will look back. For the crossover and the histogram colour flip, it is how many candles ago the event may have happened. In "Continuous strength" it is the length of the chain.
Example with numbers
In the confirmed crossover it is for how many candles the MACD line must move in the same direction without interruption — but the crossover itself must still be on the LAST candle.
What does it affect?
| VALUE | WHAT HAPPENS |
|---|---|
| 1 · panel default, toggle OFF | Only the last closed candle counts. ★ At this value "Confirmed Cross" produces no signal at all — there is no second candle to compare for the confirmation. |
| ACTIVE pressed on the toggle → 3 is written in the box, 3 goes to the bot | The requirement is met if a crossover or histogram colour flip happened on any of the last 3 candles. |
| 6 | For the confirmed crossover, the MACD line must have moved in the same direction without interruption for the last 6 candles; also, this condition gives no signal until 6 candles of history have accumulated. |
What should you watch out for?
It affects the crossover, histogram colour turn, confirmed and continuously-strong conditions. The above/below zero and MACD rising/falling conditions do not use this field.
Fisher
CONDITION WINDOW
What exactly does this condition ask?
Sets within how many recent candles the Fisher condition may have occurred.
What is it for?
The bot looks back at every candle close; this field states how many candles back it will look. In crossover conditions it determines how many candles ago the trigger crossover may have occurred.
Example with numbers
In the continuously rising/falling with increasing strength conditions, the window is the length of the requirement: the first candle of the window must have passed the strength threshold and throughout the window the strength must never have gone backwards. This way both the freshness of the event and the continuity of the move are adjusted with a single number.
What does it affect?
| VALUE | WHAT HAPPENS |
|---|---|
| 1 · the number shown in the panel | Only the last closed candle is looked at — the crossover must be on that candle. |
| 3 | If the crossover happened on one of the last three candles, it still counts as fresh. |
| 7 | The last seven candles are accepted; signals get more frequent but less fresh. |
What should you watch out for?
The larger you make it, the more frequent signals get and the less fresh they are; the smaller, the rarer they get and the fresher the remaining ones are. It affects only the entry.
ADX / DMI
STABILITY WINDOW (CANDLES)
What exactly does this condition ask?
For the above condition, sets how many candles the dominance must hold without interruption.
What is it for?
One line moving ahead through a single-candle fluctuation does not mean a lasting direction. This window holds off until the dominance has really settled.
Example with numbers
| VALUE | WHAT HAPPENS |
|---|---|
| 1 · counted as the default | Only the last candle is checked — it is enough if the dominance exists at that moment. |
| 3 | The same line must be on top in all of the last 3 candles. |
| 10 | The requirement becomes very strict; when the bot is newly started, this condition never holds until 10 candles of data have accumulated. |
What does it affect?
Works only with the ▲ Above and ▼ Below conditions. In crossover conditions it is not a filter — there it only sets the minimum amount of data the bot needs.
What should you watch out for?
CROSSOVER WINDOW (CANDLES)
What exactly does this condition ask?
Sets how many candles back the crossing of the green and red lines will be searched for.
What is it for?
A crossover happens in a single moment. This window says for how many more candles the signal still counts as valid if that moment is missed.
Example with numbers
| VALUE | WHAT HAPPENS |
|---|---|
| 1 · engine default | Only a crossover on the last candle is accepted. |
| 5 | If the crossover happened 3 candles ago, it is still valid; if it happened 6 candles ago, it drops out. |
| 20 | Very old crossovers are accepted too — most of the price move may already be over. |
What does it affect?
Works only with the ↗ Cross Up and ↘ Cross Down conditions. It is not read in the being-on-top conditions.
What should you watch out for?
Slope Strength (Min Increase)
What exactly does this condition ask?
The bot checks whether ADX has risen by at least 0 points against the previous candle on the last 1 candle. If it rose on that candle the gate is open; if it failed on it, the gate is closed.
Why does it exist, and what is it for?
ADX being high and ADX rising are two different things. At 40 but falling, the trend is dying; at 25 but climbing fast, the trend is being born. The level box measures the first, the slope box the second. Most users set both.
If you set Strength to 0
With strength at 0 the requirement drops to “ADX must not fall”: a rise of zero is accepted, but anything negative breaks it. To switch the layer off completely, turn off the Slope Check button on the panel — typing 0 in the box does not close the layer.
Does this condition close the position?
It only approves the entry; even if the condition breaks later, it does not close the position. What closes it is your choice: if Profit Lock is on, PNL tracking (while it is on, the Trailing Stop, Take Profit Net and Limit TP Net boxes are locked); if it is off, the figures you enter in these three are placed on Binance as orders and the position closes there. DCA Rescue and Liquidation Shield step in under their own conditions; you can also always close it with CLOSE on the panel or manually on Binance.
Drop Duration (for V)
What exactly does this condition ask?
The bot looks for a V on the ADX line: an unbroken fall over 5 candles, immediately followed by a rise of 0 points. The first number is this group's Drop Duration box — type 7 and the bot looks for 7 candles. The second number is NOT IN THIS GROUP, it is the neighbouring group's Slope Strength box — see the card below.
Why reversals?
If a trend has been running for a long time, ADX is already high and most of the move is behind you. The V formation picks the moments where ADX has just turned up from a bottom, aiming to enter near the start of the trend. The price of this: the number of signals drops sharply.
Where the 0 score comes from
The screen shows 0 because the box on your panel holds 0. That box is not in this group: it is Slope Strength (Min Increase) in the neighbouring 📈 Slope Check group — in the engine the V runs inside the slope layer. The panel warning says the same: “The V formation only works while Slope Check is on.” What does 0 mean? The sharpness of the turn is not required — it is enough that ADX does not fall. Type a number and the turn must be that sharp.
What number should I enter in the box?
Drop Duration (this group) is 5 candles in the panel — 3-5 is common on small timeframes, 5-10 on large ones. Slope Strength (neighbouring group) is 0 in the panel: no sharpness of the turn is required. There is no magic number — change the boxes and watch the shaded strip.
Does this condition close the position?
It only approves the entry; even if the condition breaks later, it does not close the position. What closes it is your choice: if Profit Lock is on, PNL tracking (while it is on, the Trailing Stop, Take Profit Net and Limit TP Net boxes are locked); if it is off, the figures you enter in these three are placed on Binance as orders and the position closes there. DCA Rescue and Liquidation Shield step in under their own conditions; you can also always close it with CLOSE on the panel or manually on Binance.
Cross Value (DI Difference)
What exactly does this condition ask?
The bot looks for this: the net DI gap was below 20 on the previous candle and rose above it on this one. It triggers only on that candle; even if the gap widens further on the next candle it does not trigger again.
If you enter 0
Because the net gap is DI+ − DI−, 0 is a special number: the gap crossing 0 upwards means the moment the DI+ line crosses above the DI− line. So typing 0 means “buy on the classic DI crossover”, while larger numbers say “buy once the gap has opened this far after the crossover”. 0 does NOT mean OFF here — to switch the layer off, turn off the ⚡ Spread Crossover button on the panel.
How it differs from Min DI spread
Min DI Spread: absolute gap, measured on every candle, an ongoing state. Spread Crossover: net (signed) gap, holds only on the candle it crosses, an event. You can use both together; they are separate boxes joined by AND.
What number should I enter in the box?
The Cross Value box defaults to 20. Make it smaller and the trigger fires earlier, but the direction is less clear; a very large number shows “not reached in this scenario”. There is no magic number.
Does this condition close the position?
It only approves the entry; even if the condition breaks later, it does not close the position. What closes it is your choice: if Profit Lock is on, PNL tracking (while it is on, the Trailing Stop, Take Profit Net and Limit TP Net boxes are locked); if it is off, the figures you enter in these three are placed on Binance as orders and the position closes there. DCA Rescue and Liquidation Shield step in under their own conditions; you can also always close it with CLOSE on the panel or manually on Binance.
Volume
VOLUME SPIKE MULTIPLIER
What exactly does this condition ask?
Sets how many times the average volume of the last 20 candles a candle's volume must reach.
What is it for?
Because every coin's volume size is different, the bot does not look at a fixed figure but at that coin's own average over the last 20 candles — this candle is included in those twenty. The comparison is strict: volume exactly equal to the multiple does not count as a spike. A high multiple means rarer spikes, a low multiple means more frequent triggering.
Example with numbers
| VALUE | WHAT HAPPENS |
|---|---|
| Multiplier 1 · default | It is enough for volume to rise above 1,000,000; volume equal to the average does not count as a spike. |
| Multiplier 5 | 5 times the average is required — on that single candle, the trading that normally takes five candles. |
| Multiplier 10 | 10 times the average is required. It triggers very rarely; it only catches unusual moves. |
What does it affect?
It directly determines the triggering frequency of the volume rule; together with the direction candle confirmation and the spike window it works as a single condition.
What should you watch out for?
SPIKE WINDOW
What exactly does this condition ask?
Sets within how many recent candles the volume spike may have occurred.
What is it for?
A spike happens in an instant and passes. This box says how many candles back the bot will look: enter 1 and the spike must be on exactly the current candle; enter 3 and it is enough for it to be on one of the last three candles.
Example with numbers
| VALUE | WHAT HAPPENS |
|---|---|
| Window 1 (default) | The spike must be on the very last candle; a spike on the previous candle does not count. |
| Window 3, spike occurred 2 candles ago | The condition is met; but price may have already made part of the move during those two candles. |
| 0 entered as the window | It behaves like 1; only the last candle is checked. |
What does it affect?
It affects only the condition consisting of volume spike + candle colour confirmation; it does not touch the multiplier value.