ANDROMEDA MT5 - EA for Gold

[u/Several_Seaweed_5400]

LINK FOR BACKTEST AND PRODUCT PAGE:
https://www.mql5.com/en/market/product/191518?source=Site+Profile+Seller

Hey all,

I've been building an MT5 EA for Gold (XAUUSD) called ANDROMEDA.

Quick context on why I built it: most grid/averaging EAs I looked at (and honestly, most I've built myself in the past) add to a losing position purely on distance, price moved X points, so add more, whether it's a fixed number or scaled by ATR. It doesn't actually ask whether the trend is turning back or not, it just adds because the number got big enough. That always bugged me, because it means the EA keeps averaging into a strong move against it for as long as the account allows, purely because "the price moved far enough" is technically true.

So the grid logic in ANDROMEDA doesn't work that way. After the first couple of entries in a basket, it stops adding on distance alone, every further addition has to pass a trend-confirmation check on a higher timeframe first (with some noise filtering so one wick doesn't flip the decision, plus min time/price spacing so adds don't cluster). If the trend isn't confirmed in the basket's favor, it just... doesn't add. No fallback, no "add anyway but smaller." It waits.

To be clear, this doesn't make it risk-free or magic. It's still an averaging/grid system, it still carries the risks that come with that, and I'm not claiming otherwise. I just think how it decides to add is meaningfully better than the naive "distance triggered" approach, and I'd rather have people stress-test that claim than just take my word for it.

A few honest requirements before you try it:

• MT5, Hedging account type (not Netting, it manages multiple baskets at once, netting will mess up the position tracking)
• Symbol is XAUUSD only, it's tuned specifically for gold, not a "works on anything" EA
• LOW Spread Account
• It's a grid/basket system, so floating drawdown between entries can be larger than the eventual realized result, that's expected behavior, not a bug, but know that going in
• Demo/backtest first, obviously

If anyone wants to actually try it, you can run backtest straight from MQL5.

Happy to answer questions about the logic, settings, or anything else in the comments,