I saw the first minutes of the video shared and this is my opinion

IS = 5 months
DD = 7629.68
Max. Consecutive Losses = 156 (6578.52)
%WINS = 5.51
Av. Loss =34.25

Your average risk per trade is (34.25/200)*100 = 17.125 what means that you will loose your account if 5.83 (5) consecutive loss trades happen. Accordingly to your maximum consecutive loss streak (156), there is a high probability to loose your account. In addition to that, there is a Max DD of 7629.68 in a 5 months period what it should be considered enough to do not trade this strategy,

BUT...IT´S JUST AN OPINION

It Works as expected

This is an example of what you are requesting

https://fxdreema.com/forum/topic/4858/total-profit-reduces-by-x-then-close-everything

Thanks to the people involved on that post because it is a really nice "Account Profit Trail Stop". This is why the forum and the info sharing is so valuable.

@timmyhanke
@roar

Follow the advice given by @isp00rt

It is highly recommended to read the fxDreema's tutorial web

https://fxdreema.com/tutorial

It is a good starting point.

"If Testing" block is working correctly on my projects

Hello

Is there any way to copy all the constants and variables from one Project and paste them in other one?

I have my projects in MQL5 language and I want to transform some of them to MQL4. I know that it is posible to copy all the blocks from the source to the destination. But, what about the constants and variables? Is there any way to do it as well?

Thanks

It looks like a "Martingale" strategy.

Take a look at this tutorial made by @miro1360

https://fxdreema.com/forum/topic/4321/tutorial-08-candle-formations

It has been really useful for me.

Hi

If you want to draw an arrow for each crossover condition, this should be work

But if what you want to draw is an arrow when both conditions meet at same time, it is probably that you Will get few times or noone.

Check this out

@AlphaOmega Sorry, I cannot still understand your project because you are giving the whole puzzle but we need to build it piece by piece.

Let´s make it simple and then if you have a good EA's behavior, we can try to add the suggestions given by other forum members.

What do you need to happen when the codition/s to open trade/s takes place? I remember from the begining of this topic that you wanted to open a trade when a new bar opens and the condition is still true. Is that correct?

@AlphaOmega I have to say again that you must simplify the project as much as you can or we can try to help you step by step to build what you are trying to get from a simple starting point. Maybe this way is not quick but we can get a more understandable project behavior instead of trying to look at your code to see the trouble. I am sure that other forum members are smart enough to find the problem but the way that fxDreema explained to me is as I said above.

Let's get started by doing a simple project. For example, I want that the EA opens a position every new bar after a bull crossover happened on the previous candle. There is no need to share your conditions to trade. After that simple project we will increase the complexity with what you want to obtain. What is important is to avoid adding more than 2 new features on each step of the project to be sure that what we added behaves as expects.

@AlphaOmega

That piece of code is placed on the 'OnTrade' tab that is intended to do things with trades. I would say that you have to place 'Position created' block on top what would mean that when a trade is created, some things will happen. As it is right now, I would say that the code does not execute anything.

Give it a try and let us know.

Hello @roar @AlphaOmega Happy to know that you were working on this and found a solution. Well done!!!
Keep pushing on learning fxDreema and building your projects.

@AlphaOmega It´s tough to understand what are you trying to reach if we don´t know what you would like to achieve. Said that, I will try to do my best in order to help you.

First of all, I would suggest you to read the information for the "For each position" block

We will focus on the main branch of your project because I would say that the reset branch looks correct at least in respect of the project´s logic.

If we assume that block with ID = 120 is true, next block is evaluated

We have that if the postions count is less than 1 (=0) for positions that match filters Group#=1 and Type=Buys, block passes. Then, do you want that the project´s execution passes if there is no buy position?

If we assue that there is no buy postion and block ID = 60 passes, it will not be true anymore and the false output will be active but there is nothing attached to the false output so I suppose that the project stops at this point.

As I said earlier, there are many questions to answer before reaching what you want.

@AlphaOmega Forum members will be glad to help in your growth using fxDreema. We all learnt like that.
Believe me. I was also concerned in sharing some aspects of my strategies in the past but it was needed to move forward. I am not saying that you share all details of your strategy but if you ask for some help, you will need to provide what you are trying to achieve. Keep on trying and learning with fxDreema.

@AlphaOmega

If you add a "No position" block, that will only open the parent trade and none child trades because on the second excution of the code, the "No position" block false output will active and will not pass through the open trade block. You said that you wanted to open a child trade for each new bar once the parent trade was opened.

If there is no child trade, Take profit average is not calculated because it only exists one trade that is the parent one.

If you want to limit the number of trades after opening the parent trade, you will have to use a variable like TradesLimit that will be increased each time that a new trade opens. Then, add a condition block to let pass the project execution while the limit of trades is not reached.

My suggestion is that you should write down your strategy´s rules and then we will try to help you to get what you want. Begin with a basic rule like when this condition is true, do this. When that step is correct, add a new step to the project and check it out.

But remember that the forum members are helping to make the people be more comfortable using fxDreema. They are not EA's coders for free.

@AlphaOmega

As I mentioned earlier, there are several ways to achieve the same result with fxDreema. This is just an option and, of course, the project can be optimized to get a more efficient code. Here it is the long trading side:

https://fxdreema.com/shared/xblYjK0uc

0_1598858539003_Profit Math.mq5

Whatever the condition is true to enter at market, that piece of code will open a trade for every new bar with the original take profit value (100 pips in the exxample). When a child trade opens, it calculates the take profit average by getting which is the take profit in pips of the child trade using the parent open price as the reference following this formula structure:

TakeProfitAv == (TakeProfitPips + (TPLevel_ChildTrade1 - OpenPrice_ParentTrade) "as pips")) / nTrades

After that, the code will modify the child´s TP to TakeProfitAverage.

That logic will repeat until you break the loop when your condition to do not enter long at market is met (maybe when start to go short).

Keep in mind:

• I defined the Pointsize with a number but it can be set with 'Market Properties'. This parameter is used to convert from points to pips or vice versa.

• I have used a "Counter: Pass once' (Id=3) block to split the parent trade from the child trades. This block will need to reset at some point along your code. For example, when you break the go long loop. If it is not reset, when the EA starts with a new go long loop, it will not activate the true output of the block.

One of the best suggestion that I got from fxDreema support & other forum members is to add blocks that makes me to see if the code is going as I expect:

"Draw Arrow" allows me to see that the execution passed through the "modify stops" block
"Comment (ugly)" allows me to see the parent trade values
"Comment" allows me to see that the calulations are correct

Hoping that this example provides you some starting point.

@ramimoujaes Your project has some blocks fields empty that are important for the project´s logic.

My suggestion is always to try to understand the logic of what you are building. The "How To" examples are just a guide to help you to begin from something. Same applies for the suggestions provided on the forum.

Said that, what you want is to open - close trades on opposite conditions of a MAs crossover. Here you have an approach

As you can see above,

when MA (5) x> MA (200), EA closes Sells (no sells were running, no Buy - Out) and opens Buys (Buy - In)
when MA (5) x< MA (200), EA closes Buys (Sell - Out) and opens Sells (Sell - In)

As I mentioned earlier, that example is just an approach to what you want but it does not mean that is the only one because fxDreema allows to do the same through different ways.

if you share the project, it is easier for any forum member to suggest something to try