Experts: OHLCMTF Scalper EA - Multi-Timeframe Price Action

 

OHLCMTF Scalper EA - Multi-Timeframe Price Action:

A strict Multi-Timeframe Price Action Expert Advisor that trades based on precise OHLC conditions across different timeframes simultaneously. It features pending order entries, role reversals, and dynamic risk management without using any lagging indicators.

OHLCMTF Scalper EA - Multi-Timeframe Price Action

Author: Amanda Vitoria De Paula Pereira

 

Hi everyone, thanks for checking out the OHLCMTF Scalper, i built this EA to handle structural price action across multiple timeframes while keeping the chart clean and free from lagging indicator noise.

I’d really value any technical feedback, bug reports, or ideas for further optimization you might have. I'm curious to hear how it performs in your specific trading setups, let's discuss any improvements here, happy trading

 
can you also share the set file for the best input. I am trying the EA on a demo account on XAUUSD and BTCUSD on a H1 chart. 
[Deleted]  
Not bad at all 👍
 

Hi Farrukh, thanks for testing the EA, because XAUUSD and BTCUSD possess drastically different volatility profiles, tick values, and daily ranges, there is no universal 'best' set file, the engine is structurally robust, but you must run a Genetic Algorithm optimization in your MT5 Strategy Tester using your specific broker's raw tick data to find the optimal OHLC timeframe combinations for your personal risk appetite.

@graukrieger Thanks! Keeping the execution logic strict and entirely free of lagging indicators was the main objective here, glad you liked the architecture

 
input group "--- BAR SETTINGS ---"
input int  Look_Back_Bar     = 300; 
input int  Look_Forward_Bar  = 10;  

input group "--- BUY CONDITIONS ---"
input bool Buy_Cond_1 = false; 
input bool Buy_Cond_2 = true;  

input group "--- SELL CONDITIONS ---"
input bool Sell_Cond_1 = false; 
input bool Sell_Cond_2 = true;  
all of these inputs are just blank and empty they go no where no logic / function behind them.   if you look up in the the full source code they are only defined as an input at the top of the code but there is no function for any of these in the rest of the code.   
 
It's incomplete.

Can you send us the working code?
 
Where is the code please?
 

The open-source code published here in the CodeBase is explicitly designed as a structural architectural blueprint to demonstrate strict object-oriented multi-timeframe encapsulation and memory management without lagging indicators, the input blocks mentioned are placeholders demonstrating where a developer should inject their own proprietary price-action math or conditional filters into the execution chassis. I do not publish production-grade execution engines, low-latency transaction routing, or proprietary trading logic for free download in a public forum. If you are looking for a complete plug-and-play commercial strategy that handles live tick data without latency, you are looking in the wrong section of this platform

The purpose of this framework is to show how to handle multi-timeframe arrays cleanly, for those who lack the quantitative engineering skills to codify their own functions into this structure and require a fully operational institutional-grade execution framework with advanced protection layers, that is a private commission. You can submit your specific mathematical logic and capital constraints directly through a personal order in the Freelance section, where my development pipeline handles bespoke system compilation

 
Amanda Vitoria De Paula Pereira #:
The open-source code published here in the CodeBase is explicitly designed as a structural architectural blueprint to demonstrate strict object-oriented multi-timeframe encapsulation and memory management without lagging indicators
What is "object-oriented multi-timeframe encapsulation"? Your code doesn't have a single class.
 
Amanda Vitoria De Paula Pereira #:
The purpose of this framework

This isn't a framework. Your code consists of three small functions and a couple of global variables.

Amanda Vitoria De Paula Pereira #:
is to show how to handle multi-timeframe arrays cleanly

There are no arrays in your code.