@alphaomega Thank you for your kind words. And also...you're welcome.

Use this immediately after your Buy/Sell block:

I don't think anyone here would do that. What you are requesting is an extraordinary effort even for experienced programmers. Just my opinion.

This is one possible way to do it:

This block is looking for the previous 10 bars, from candle ID 10 (ten bars ago) to candle ID 1 (the bar immediately previous to the current one. Notice that I had to specify the cross width as 9, becuase that's the range being considered.

@PrinceErielle902 Using ChatGpt on fxDreema is an error. Simply don't do it. fxDreema is using libraries and other elements chatGPT doesn't necessarily understand. It is not that intelligent, trust me.

@ideal Trust me, martingales are never worth your time. They will destroy your account sooner than later.

The 'delete objects by type' block doesn't work when deleting 'arrow up/down' options. However, when selecting just 'arrow' it works correctly:

https://fxdreema.com/shared/T6QD99YOd

Could the admin take a look at it, please?

I don't know how brokers can know you're using a EA, but certainly a script is a one bullet gun as far as you don't use it repeatedly very often. I'm afraid I cannot give you an answer for that question.

There is no 'wonder' indicator for what you want. In general any indicator following the trend or even oscilators can do it. The problem is how to limit their action on the chart.

I'm not one of those most experienced members, but I guess the only way a EA can operate on another EA is by using terminal variables. Miro and roar would probably can offer more detailed info here.

Interesting. I don't understand why it doesn't work on MT5.

Por desgracia no, debe ser manual. Aun así, puedes ahorrarte muchos errores si substituyes todos los bloques rosa "For each trade" de MT4 por los de "For each position" de MT5.

Not necessarily. I have no idea what values that variable can store. I see they depend on previous calculations. That means some time the value can be higher than other. Those days were the distance is very short should be the reason for that behaviour.

Not sure I completely get it. Isn't the grid used exactly to avoid that?

There is none AFAIK.

Probably the issue is with the value of the variable used to determine the price offset. Depending on the result of the calculations prior to the order programming, the variable result is too close to the programmed open price. That makes the broker to block it. You should ask your broker which minimum distance is accepted between current price and an accepted pending order. Then you should check your variable should always be bigger than that distance.

@l-andorrà This is what ChatGPY created.

//+------------------------------------------------------------------+
//| Function to check if trade was opened and closed in same candle |
//+------------------------------------------------------------------+
bool IsTradeClosedInSameCandle(ulong ticket)
{
// Get trade history by ticket
HistorySelect(0, TimeCurrent());
ulong history_ticket = HistoryOrderGetTicket(ticket);

if(history_ticket == 0)
return false;

// Get trade open and close times
datetime open_time = (datetime)HistoryOrderGetInteger(history_ticket, ORDER_TIME_OPEN);
datetime close_time = (datetime)HistoryOrderGetInteger(history_ticket, ORDER_TIME_DONE);

if(open_time == 0 || close_time == 0)
return false;

// Get current timeframe in seconds
ENUM_TIMEFRAMES current_tf = Period();
int tf_seconds = PeriodSeconds(current_tf);

// Calculate candle start times
datetime open_candle_start = open_time - (open_time % tf_seconds);
datetime close_candle_start = close_time - (close_time % tf_seconds);

// Check if both open and close are in same candle
return (open_candle_start == close_candle_start);
}

How could I make it work below a 'For each position' block?

Can you please share the link to the project?

I'm afraid it didn't work.

I need to identify those trades that were open and closed within candle ID 0. I'm not sure why this config is not working:

Is the comparison searching for the exact UNIX time the current candle was open, maybe? The trade can be closed at any moment AFTER the current candle was open. It doesn't need to be open at the first tick of the current candle, as this setting is apparently doing.

Am I missing something?