I will code your EAs and Indicators for no charge

Quoting mwlrct

Disliked

--- image: - chart timeframe: M15 - v.11 set timeframe: M30 {image} --- how to: Just replace 30 with any timeframe you need like 240,1440 etl {image} --- changelog: /*-------------------------------------------------------------------- change-log: Bri date: 27-02-2025 by: Mwlrct filename: 'bri v.11.mq4' -------------------------------------------------------------------- - [added] input parameter 'timeframe' to allow drawing imbalance lines based on a user-defined timeframe, independent of the chart timeframe. - this enhancement enables multi-timeframe...

Ignored

Quoting MwlRCT

Disliked

{quote} Download: {file}

Ignored

Quoting WGR21

Disliked

Can you convert MT4 robot mq4 to a MT5 ? Thanks

Ignored

Quoting zeroline

Disliked

{quote} So, I tested the last one you posted, with updating the signals outside the levels there. Do you know if running the visual backtest of the strategy tester is different from testing in real time with an open market, the issue of autorefresh? Because the visual test I did here was in the strategy tester

Ignored

Quoting BestTraderEv

Disliked

{quote} Yes, it can't refresh like that in the tester. You can't switch between timeframes in the tester.

Ignored

Quoting TooSlow

Disliked

{quote} How are we supposed to make contact?

Ignored

Quoting zeroline

Disliked

{quote} Now I understand. How often does it refresh the graph?

Ignored

Quoting clinton

Disliked

Hello, can anyone code an indicator with alerts and push notifications using these parameters? EMA 5 CLOSE EMA 13 CLOSE RSI 24 CLOSE WITH LEVEL 50 Buy: When the 5ema cross the 13ema above and the rsi is above the 50 level Sell: When the 5ema cross the 13ema below and the rsi is below the 50 level Thanks In advance {image}

Ignored

Quoting BestTraderEv

Disliked

{quote} Debes preguntar dónde dice: {image}

Ignored

Quoting Iagol

Disliked

{quote} Thanks

Ignored

Quoting walvekarraje

Disliked

{quote} Observed Behavior 1: In live market, the change from Up to Dn and vise versa is does not happen .Even after the cross happens, the signal does not change. eg. US30 should change to UP in the below pic. {image} Expected Behavior 1: Solution : real-time data should be processed correctly.1) Up/Dn should be printed correctly in relation to the price and gann line. If price is above gann Up should be displayed. if price is below gann line Dn should be printed. When price crosses gann line from above below; Up should change to Dn. If price crosses...

Ignored

Quoting walvekarraje

Disliked

Observed Behavior 1: In live market, the change from Up to Dn and vise versa is does not happen .Even after the cross happens, the signal does not change. eg. US30 should change to UP in the below pic.

Ignored

Quoting walvekarraje

Disliked

Expected Behavior 2: Alerts should be processed clearly. When Up changes to Dn, Alert in form of " Instrument name : Time frame : Gann Hi Lo : Dn". should be displayed
When Dn changes to Up, Alert in form of " Instrument name : Time frame : Gann Hi Lo : Up". should be displayed.
Alert to be generated on CLOSE of candle only.

Ignored

Quoting BestTraderEv

Disliked

{quote} I'm not sure that what you want to achieve is at all even possible. You see, MT4 needs to scan through all the symbols and timeframes, and that through all the indicators. Which means that you may not see the signal in the dahsboard for some time, and especially for lower Tfs, speed matters. MT4 is only 32bit, you can't do anything about that.

Ignored

Quoting jeanlouie

Disliked

{quote} It is what was described by the person I responded to. Looking at the pdf, I guess it's similar, 2 movements in the same direction then a movement back, but that is over several candles, the person I responded to had only 2 candles. Attached has a 3rd pattern that is closer to the pdf, and uses 3 candles. Candle_Pattern_scanner_v1.1 - scans market watch, selected tfs - pattern 1 = 2 opposite candles, HH/LL - pattern 2 = 2 same candles, HH/LL & closes back inside - pattern 3 = 2 same candles, HH/LL then 1 opp closes behind 2nd mid v.12 -...

Ignored

/*--------------------------------------------------------------------  
# Change-log: Gann High-Low Cross Dashboard With Alert v1.08  
Date: 03-03-2025  
By: MwlRCT  
--------------------------------------------------------------------  
## Problem: False Direction Signals
**Solution:**
- Return neutral state (0) when historical data is inadequate
- Prevent incorrect baseline assumptions
## Problem: Inconsistent Alerts
**Solution:**
- Fixed `Notify()` to trigger only on valid direction changes (1/-1)
- Eliminated duplicate alerts for unchanged conditions
--------------------------------------------------------------------*/
Image: 
[attach]screenshot.png;4910270[/attach]

Quoting MwlRCT

Disliked

{quote} --- Root Cause: {quote} --- Verification : Identified Indicator Limitation The indicator doesn't update "Up/Dn" signals in real-time because: The indicator uses only closed candle data (iClose(..., 1) and previous EMA values) Signal updates only trigger when a new candle forms (via _candleClosed flag) The indicator is specifically designed to evaluate signals at candle close, not during candle formation Root cause: The indicator relies on completed candles rather than processing tick-by-tick data for...

Ignored

Quoting walvekarraje

Disliked

{quote} I agree. I was using lower TF and low setting only to check the funcation and accuracy of the dashboard. Practically the setting will be much higher so the change will be after many many candles in lower TF and a delay will also not matter. I will get back to you after I reset my settings and also explain the logic behind. Kind regards.

Ignored