Yes, you can create a group of trades and the use a 'for each trade' loop for that specific group. That means any trade belonging to any other group will not be considered in the calculation.

@Reyhaneh77 I mean this:

01.png

Just select H1 on the block instead of using a constant, as per your screenshot.

on trade tab, trade created - delete pending orders. the tabs on init, on timer, on trade, on chart, work at different times and have area specific blocks... so for this you want to work with a trade just being opened

@doeveR
Maybe normalization by ATR can help. Say, divide the increment or slope, by ATR. Or you can even try the square root of ATR. That make sense as ATR is approximately proportional to time square. And the slope is given by increment over time.

Just make some test to see what you want

If you paid via crypto, payments can be confirmed up to one week later. Sadly, the admin does not check cryptopayments automatically but manually. However, you will be given the time period you paid for.

Thank you.

@deathkid13 You can do it this way:

01.png

Ahhhh i see. Thank you brother

Once you have the ID, you know which candle or within a range you need to check for engulfing.

Can you please share the link to your project?

Could you please open a new thread with your question instead of using this one?

Actualmente puedes usar fxdReema gratis si construyes proyectos con un máximo de 10 conexiones entre bloques. Si quieres crear proyectos mayores, entonces debes usar la versión de pago.

This happened once long time ago, while using a previous version of fxDreema. I remember the admin did some changes and never happened to me again. I'm using Firefox all the time, so probable the issue is the project itself. Just in case you could contact the admin himself and let him know.

If crypto can take days, admin will see and sort soon. You can message here it may speed up the process: https://fxdreema.com/support

instead of variables use constants, this way they can be changed in your EA's inputs.

@jstap

Yep, the project i have shared does exactly what you just described : splitting the 1% risk to 3 (0.33%) whilst also calculating the gap distance.

Though, i just use a simple TP for this (percent of SL). I'll leave the customized TP to whoever wants to use this project as a base.

My current conclusion : The No Position Nearby Block is incredibly unstable, any usage of it should be minimized 😅

Thanks for helping out!

I can help, but not sure exactly what you want, simple tree would be: no position block - condition block (to say reason for placing trade) - buy or sell block (set TP and SL inside)

439a07bd-9153-41f5-bfa8-523db4b9b648-msedge_LksLk0xB15.png

@nikolay_s
The code seems straightforward and should work. I have tried it with codes similar to you. Try this one: https://fxdreema.com/shared/K9SXQIxK

If in your case still not working, it might be the csv file problem. The csv file in above demo is created with path fxDreema\positionAllowed.csv in the File folder. I have tested with or without delimiter, space, line feed, ... and they are all working. By the way, how do you edit and save the file ? Have you debug and check file_handle has been valid ?

My code is simple:

string InpFileName="positionAllowed.csv" ;
string InpDirectoryName="fxDreema" ;
//--- reset the error value
ResetLastError();
//--- open the file for reading (if the file does not exist, the error will occur)
int file_handle=FileOpen(InpDirectoryName+"//"+InpFileName,FILE_READ|FILE_CSV|FILE_ANSI);
if(file_handle!=INVALID_HANDLE)
{
v::positionRead = (int)FileReadNumber(file_handle);
//--- close the file
FileClose(file_handle);
}
capture_001_31012026_002040.png

This is true 🙂 Check this post - post/10298

you have to search for what you want