MT4 complex custom indicator

MQL4 Indicators

Specification

Hi,

I’m currently working on a trading system that should be automated. The first step will be to code an indicator for detecting special/important support and resistance areas on any forex chart and suggesting appropriate SL/TP levels for making the corresponding BUY/SELL market orders. Said indicator needs complex calculations and a lot of input parameters for the user in the GUI. Therefore the budget is up to $ 100 and I need the final product (incl. bug fixes) soon resp. within the next few days.

A detailed description of the requested indicator’s functionality is attached in the postscript (see below).

Who can do this VERY accurately?

[An advanced mathematical understanding is strongly required!]

Best,

Ben

PS: Description of the requested indicator:

MT4 Indicator “SupRes_v1”

Concept:
“SupRes_v1” detects strong up/down price movements followed by a support/resistance area and draws a down(sell.order) / up(buy.order) arrow contrary to said strong movement. The requested indicator also plots lines for suggested fixed SL/TP levels along with said arrows that symbolize the recommended trading direction.

It is recommended to open the attached image in a separate browser tab etc. for a better understanding when reading the detailed description below.

Description in detail:

Stage 1:

The fx chart resp. price makes a strong up(sell.order) / down(buy.order) movement for at least n bars. A “strong movement (SM)” must be calculated as follows:
SM = [(Difference in points between the highest high and the lowest low of the last n closed bars)/n]/[SUM(length of n bars)]
In the Indi’s GUI the user must also be able to define the minimum value for SM:
-> Minimum value of SM: 0.55 [etc.]
-> Minimum number n of SM bars: 5 [etc.]
If e.g. SM = 0.50, the strong movement’s bars’ “overlapping value” must be averagely at least 50 %.
If e.g. SM = 1.00, the strong movement consist of consecutive “non-overlapping” bars.
If e.g. SM > 1.00, the strong movement’s bars must have partly gaps between each other.

The indi must permanently scan the chart’s last n closed bars and recognize if all conditions for a valid “SM” are fulfilled.
Once a SM is detected the indi must “note” the value resp. price of SM’s lowest low and highest high and their positions (time/date). From then on the indi must continually check resp. recalculate if the movement stays “strong” (definition see above) when including the follow-up bars n+1, n+2, n+3, …, n+x (instead of calculating only with n) and – ONLY IN THIS CASE – update the values/dates for SM’s lowest low and highest high (see above).

Furthermore a potential SM(n) resp. SM(n+x) must be ignored by the indi if it exceeds “maximum points of distance SM” or undercuts “minimum points of distance SM”, whereby “distance” = difference between the highest high and the lowest low of all “SM valid closed bars (n+x)”:
-> Maximum points of distance SM: 300 [etc. (if TF = M1)]
-> Minimum points of distance SM: 60 [etc. (if TF = M1)]

Stage 2:

The strong movement slows down. This means that the “Minimum value for SM’s n bars: 0.55 [etc.]” is undercut by the currently closed n+x+1 bar e.g. SM’s calculated current actual value shrinks from >0.55 to 0.54 or 0.43 etc. In this case the indi must make the “final notation” of SM’s lowest low / highest high (see above) BUT EXCLUDING the last closed bar that caused the end of SM!
Now the bars of SM consist of the initial bar (IB) followed by n-1 bars + x bars that let the movement stay strong (x can also be 0!) including the final SM bar (FB), before SM is terminated by the terminating bar (TB) which already belongs to the “support/resistance area (SR)”, see below.

Stage 3:

The “strong movement (SM)” is – per definition – followed by a “support/resistance area (SR)”. Now the indi must check if at least the next k closed bars within SR – starting with TB (see above) – are fulfilling the following conditions:

1.) The difference of SR’s k bars’ highest high and lowest low must be a “maximum percentage (SR-MP)” in relation to SM:
-> Maximum value for SR-MP: 0.35 [etc.]
-> Minimum number k of SR bars: 5 [etc.]
If e.g. SR-MP = 0.35, the k bars in the support/resistance area (SR) are all swinging within a range of maximum 35 % in relation to the strong movement’s (SM) distance [calculated according to “Stage 1”).

2.) At least e bars of the k closed bars (within SR, see above) have a high(sell.order) / low(buy.order) that is close to the highest.high(sell.order) / lowest.low(buy.order) of “SM-SR”, whereby “SM-SR” includes ALL closed bars starting with IB (initial bar of SM) and ending with the last closed CURRENT bar. Said “e” bar’s upper/bottom extrema [high(sell.order) / low(buy.order)] must be in a specified range [in points]; for example 2 bars out of 5 within SR are close to each other AND close to said extremum of “SM-SR”:
-> Maximum range of SR’s e bars: 10 [etc.]
-> Minimum number e of SR bars with similar extrema: 2 [etc.]
If “Minimum number e of SR bars with similar extrema” = 0, there MUST NOT be any couple/triplet etc. of bar’s with similar extrema but CAN BE.

3.) At least the l last closed bars of k are lower(sell.order) / higher(buy.order) OR EQUAL to the corresponding extremum of SM:
-> Minimum number l of SR’s last bars with lower/higher extremum: 2 [etc.]
If “Minimum number l of SR’s last bars with lower/higher extremum” = 0, the last closed bars within k have no further restriction at this point.

NOTE:
If not all conditions of “Stage 3” are fulfilled at the close of bar k, the indi must continually check resp. recalculate them with bars k+1 (instead of k), then k+2 (instead of k+1), then k+3 (instead of k+2), … and so on. This process will end if
a) all conditions are fulfilled
or
b) “Maximum value for SR-MP” is exceeded by the currently processed bar.
If “b” occurs the indi must go back to resp. start again with “Stage 1”.
If “a” occurs the indi must proceed with “Stage 4” (see below).

Stage 4:

If all conditions of “Stage 3” are fulfilled the indi must wait until the current price reaches the end region of SR = ER-SR. The “ER-SR” is – per definition – located in the upper(sell.order) / bottom(buy.order) area of SR and finally ending with the SR’s highest.high(sell.order) / lowest.low(buy.order). ER-SR must be set in the GUI by the user as a percentage of the distance between the highest high and the lowest low of SR:
-> ER-SR’s percentage for entry price level: 0.25 [etc.]
In this case the current price must reach the top(sell.order) / bottom(buy.order) 25% of SR to fulfill this condition.
If said value is set to e.g. 1.25 (= 125%) the current price must exceed(sell.order) / undercut(buy.order) SR’s highest.high(sell.order) / lowest.low(buy.order) with a “distance of at least 25% SR”, whereby “distance of SR” = highest.high - lowest.low of the current/actual SR in points.

NOTE:
It’s very important that all follow-up bars after “Stage 3” resp. while “Stage 4” must apart from that ALSO be in the range of “Maximum value for SR-MP” [see “Stage 3: 1.)”], even the currently processed (not closed) bar!
As soon as a (current) follow-up bar of “Stage 4” exceeds “Maximum value for SR-MP” before reaching “ER-SR” (see above) the indi must go back resp. start again with “Stage 1”.

Stage 5:

If all conditions of “Stage 4” are fulfilled the indi must draw a colored down(sell.order) / up(buy.order) arrow above/below the current price reaching ER-SR (see above):
-> Color of the up/buy arrow: yellow [etc.]
-> Color of the down/sell arrow: yellow [etc.]
Furthermore the indi must calculate and draw suggested fixed SL/TP levels (horizontal thin and dotted lines with a length of 20 bars):
-> Color of the fixed SL line: red [etc.]
-> Color of the fixed TP line: lime [etc.]
The value resp. price level of SL/TP must be calculated as follows:
A user defined percentage of the difference highest.high and lowest.low of the whole movement IB->ArrowBar is converted to points and
for SL added(sell.order) to / subtracted(buy.order) from the “arrow’s price level”
resp.
for TP subtracted(sell.order) from / added(buy.order) to the “arrow’s price level”:
-> SM-SR’s percentage for calculating SL buy: 0.35 [etc.]
-> SM-SR’s percentage for calculating TP buy: 0.25 [etc.]
-> SM-SR’s percentage for calculating SL sell: 0.40 [etc.]
-> SM-SR’s percentage for calculating TP sell: 0.20 [etc.]
Furthermore the final SL/TP levels must ALWAYS be “expanded” by a user set spread (in points) that best represents the broker’s average:
-> Spread added to expand TP/SL: 12 [etc.]

Stage 6:

After an arrow and its corresponding TP/SL lines were drawn by the indi the latter must “pause” all calculations for r (recess) bars. After r bars it starts again with “Stage 1”:
-> Number of recess bars after signal: 10 [etc.]

Extra filter:
If enabled, all potential sell/buy signals will be “skipped” if not at least b bars BEFORE SM have a lower(sell.order) / higher(buy.order) extremum than the highest.high(sell.order) / lowest.low(buy.order) of SM-SR with at least p points difference:
-> Enable extra filter: true/false
-> Minimum number of lower/higher bars b before SM: 100 [etc.]
-> Minimum points of lower/higher bars before SM: 120 [etc.]

!! Please optimize the indicator for the lowest possible CPU usage – thx !!

Responded

1
Developer 1
Rating
(258)
Projects
395
28%
Arbitration
69
19% / 49%
Overdue
120
30%
Free
2
Developer 2
Rating
(107)
Projects
149
36%
Arbitration
29
3% / 55%
Overdue
35
23%
Free
3
Developer 3
Rating
(219)
Projects
370
42%
Arbitration
145
17% / 41%
Overdue
124
34%
Free
4
Developer 4
Rating
Projects
0
0%
Arbitration
0
Overdue
0
Free
Similar orders
Where are my developers colleagues . i want you to support me on existing work i just need a little addon on it. Am still a student kindly support me. You will be get paid at the end of the work. If you want more details maybe the worth of the project or any other thing let me know. THNAKS FOR THE SUPPORT
** Entry Condition **: - ** For Long**: The trade is entered **after BB + ** is confirmed. - ** For Short *: The trade is entered **after BB -* is confirmed. ### 2nd **Stop Loss **: - ** For long Entries *: stop loss is triggered on a ** candle close above the high* of the breaker block shown by the indicator. - ** For Short Entries **: stop loss is triggered on a ** candle close below the low ** of the breaker block
Hello, am in need of a developer that can help in developing a trading bot that can effectively navigate the foreign exchange (Forex) market or other financial markets to generate passive income. My objective is to create a sophisticated algorithmic trading system that can consistently produce profitable trades with minimal manual intervention. I am seeking a reliable and efficient solution that can be tailored to my
am looking for who help me convert tradingview indicator to mt5 car trading strategy and make sure you are an expert before u apply to this and also my budget for this is 30$ so the name of the indicator is Breaker Blocks with Signals (LuxAlgo) ### 1. ** Entry Condition **: - ** For Long**: The trade is entered **after BB + ** is confirmed. - ** For Short *: The trade is entered **after BB -* is confirmed. ### 2nd
I have a custom MT4 indicator that I need converted to MT5. I'll share the source code with the applicants. Please only apply if you have vast experience in converting complex indicators successfully to MT5, and making sure that the MT5 version functions exactly the same as the MT4 version
I need an expert to help me convert chopzone traingview pinescript to mt4, I need an expert to get it done for me on between 1 to 2 days i hope this will be done by then, i will attach the file and my budget is $30 as of minimum here
Looking for someone to edit/optimize and existing NN (neural network) in my EA so it is more compatible/profitable with the multiple strategies. The expert advisor is a portfolio expert advisor consisting of 33 separate advisors/strategies compiled into one. A NN has been added to the EA but it does not compliment or help the EA's performance. I've attached the original EA (without NN) as well as the EA with the NN
Procuro programador que consiga modificar essas estratégias, com a mesma capacidade de alteração das suas funcionalidades. Reitero, não consegui contato com o programador da fonte, nem mesmo mandando diversas mensagens no telegram! br.tradingview.com/script/PfpFNXyI-Braid-Filter/ br.tradingview.com/script/kv8N05R7-AlphaTrend-Screener/ Ambos os indicadores precisam agir em conjunto, tanto para as funcionalidades em
--- ### Basic Rules for You 1. **Time Management**: - All tasks should be completed within the agreed-upon timeframe. Clear deadlines will be set, and it's essential to adhere to them to ensure smooth progress. 2. **Fixed Budget**: - The budget for this project is fixed. Please ensure that all work done remains within this budget. Any additional costs must be discussed and agreed upon before proceeding. 3
CORREÇÃO NOTIFICAÇÕES Ø O indicador muda a cor dos candles e da MA200 quando ocorre as entradas e é somente nesse momento que ele deve enviar notificação de entrada porem está enviando em outros momentos que não atende as condições conforme imagem abaixo. Ø Sempre que abro o MT5, mudo o time frame ou a plataforma perde conexão o indicador me envia notificações de entradas passadas, o indicador deve enviar

Project information

Budget
50 - 100 USD
VAT (19%): 9.5 - 19 USD
Total: 59.5 - 119 USD
For the developer
45 - 90 USD
Deadline
from 1 to 4 day(s)