Posts made by hasanrockefeller

When I want to close only buy or only sell positions in my EAs, I just filter on the position type inside the loop. Usually, I’ll grab each open position, check if it’s a buy or sell using PositionGetInteger(POSITION_TYPE), and then call the close function only when it matches what I want. That way, I don’t touch the other trades, and it’s quick because the function just skips over the wrong side. You can throw in this check right before you call PositionClose on each ticket.

If you're automating this sort of thing or want even more customization, it helps to use something modern like a prop trading API. Makes bulk management, filtering and order handling way smoother without messing with a ton of MQL directly.

I haven't used FxDreema with AMP Futures specifically, but I've worked with MT5 for futures before. The big difference I noticed with futures is the data feed and execution speed—it can be a bit different from Forex CFDs. You’ll want to double-check the broker’s settings, especially if you're automating strategies with EAs. As for advice, I’d recommend starting small and testing strategies on demo accounts first since futures can be more volatile.

Hey Romain, I’ve been trading futures with AMP on MT5 for a while now, and it’s been solid. When I switched from Forex CFDs, the biggest thing was adjusting my EAs for tick values and the contract specs—FxDreema can handle it, but you’ll probably need to fine-tune your risk settings. Another thing to watch out for is the trading hours since futures don’t run 24/5 like Forex. It’s a bit of an adjustment, but once you get the hang of it, it’s pretty straightforward.

I’ve had similar issues with trailing stops in fxDreema before, and it’s usually down to how the conditions are set to update. One thing that worked for me was using a variable to track when the trade hits 1R, then adjusting the stop based on that instead of relying on fixed steps. Make sure your trailing stop logic is recalculating on every tick or whenever the profit hits a new level, otherwise, it might not trigger properly. I’d also double-check that your break-even logic isn’t conflicting with the trailing stop—it’s easy to accidentally overwrite one with the other. If nothing else works, sometimes scripting that part directly in MQL can give you more control.

Hey, I’ve built something similar before, and it’s not too hard once you break it down. You’ll need to write it in MQL4 or MQL5, depending on what platform you’re using. Basically, you set the logic for the two short SMAs to trigger a cross and use the OrderClose function to close the trade. When I started, I found YouTube tutorials and the MQL forums really helpful for figuring out the basics.

I know it’s challenging to stay disciplined with rules like this, so having something in place to enforce it can help a lot. On a side note, when I need a break from the screens, using something like Crave Max Beast to relax for a bit helps me come back with a clearer mindset.

I've done something similar before where I needed to track a key candle for drawing dynamic levels. What worked for me was storing the time of the h0 candle from the ZigZag indicator using something like Time[ZigZagPeak]. Once you've got that timestamp, you can use it as your reference point for the Fibonacci. I made it so the 100% level stays fixed at h0, while the 0% level adjusts with the current market price. You just need to update the 0% level with the live price in your on-tick loop. It took a bit of trial and error to get it to update smoothly, but once it’s set up, it’s super handy for catching those touch trades.

Yeah, you can definitely do that with FX Dreema. I’ve played around with it myself, and it’s actually pretty straightforward. You can set up a custom UI where users can choose whether they want their stop loss to be based on ATR, pips, or even a percentage of their account. Just use the input parameters to let them pick, and then set up the conditions in the logic. I’ve done something similar for a bot that adjusts settings based on market conditions, and it worked pretty well, so I don’t see why it wouldn’t work for this too.

What I usually do is use the "For Each Trade" block to loop through all my trades, then sort them by the time they were executed. To get just the last two, I put in a condition using the "Get Trade Count" so it only grabs the ones with the highest index numbers. This way, it always picks up the most recent trades, and you don’t have to worry about specific pairs or IDs.

Yeah, I've dealt with that before in fxDreema. When you're adding your custom indicator, you can change the buffer in the "Indicator Buffer" dropdown. If your buy is on Buffer 0 and your sell is on Buffer 1, just set it to 1 for sell signals. The shift thing confused me at first too, but you should see a "Shift" option right there when you’re setting up the buffer. That’s where you put the number of candles back you want it to check. I remember messing around with it for a while before I figured it out, so just play around with those settings till it lines up right.

You could try programming an automated system or using trading software that lets you set conditions for pauses, like stopping after a loss and resuming only after a win.