Indicator to detect support/resistance

MQL4 Göstergeler

İş tamamlandı

Tamamlanma süresi: 42 gün

İş Gereklilikleri

Hi,

I'm seeking an experienced coder with advanced mathematical understanding to let him programm a complex custom indicator that will later be part of the corresponding final EA. Budget is $ 90.00 (only for the indicator) here on mql5.com. Who can do this accurately?

Best,

Ben

PS: Here's the description of the requested 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 resp. figure 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 Indis 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.60, the strong movements bars overlapping value must be averagely maximum 40 %.
If e.g. SM = 1.00, the strong movement consist of consecutive, averagely non-overlapping bars.
If e.g. SM > 1.00, the strong movements bars MUST have partly gaps between each other.

The indi must permanently scan the charts 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 SMs 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 SMs 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: 70 [etc. (if TF = M1)]

Stage 2:

The strong movement slows down. This means that the Minimum value for SMs n bars: 0.55 [etc.] is undercut by the currently closed n+x+1 bar e.g. SMs 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 SMs 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 SRs 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 movements (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 bars 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 SRs 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 bars 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-SR:
-> Minimum number l of SRs last bars with lower/higher extremum: 2 [etc.]
If Minimum number l of SRs 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 SRs 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-SRs 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) SRs 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.
This means that all values above 1.00 result in an price must exceed(sell.order) / undercut(buy.order) a special price level that lies OUTSIDE SR. This calculation is NOT the same as for values between 0.00 and 1.00, because the latter values result in an price must reach specific area.

NOTE:
Its 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 arrows price level
resp.
for TP subtracted(sell.order) from / added(buy.order) to the arrows price level:
-> SM-SRs percentage for calculating SL buy: 0.35 [etc.]
-> SM-SRs percentage for calculating TP buy: 0.25 [etc.]
-> SM-SRs percentage for calculating SL sell: 0.40 [etc.]
-> SM-SRs 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 brokers 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 further calculations for the current signal triggering bar AND for r (recess) follow-up bars. After r bars it starts again with Stage 1:
-> Number of recess bars after signal: 10 [etc.]
NOTE: The indi must be 100 % non-repaint and every arrow resp. TP/SL line will stay forever!

Extra filter:
If enabled, all potential sell/buy signals will be skipped if not at least b bars BEFORE SM have a lower.high(sell.order) / higher.low(buy.order) 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 !!

Dosyalar:

Yanıtlandı

1
Geliştirici 1
Derecelendirme
(107)
Projeler
149
36%
Arabuluculuk
29
3% / 55%
Süresi dolmuş
35
23%
Serbest
2
Geliştirici 2
Derecelendirme
(61)
Projeler
120
34%
Arabuluculuk
17
18% / 41%
Süresi dolmuş
51
43%
Serbest
3
Geliştirici 3
Derecelendirme
(258)
Projeler
396
28%
Arabuluculuk
69
19% / 49%
Süresi dolmuş
121
31%
Serbest
4
Geliştirici 4
Derecelendirme
(180)
Projeler
301
30%
Arabuluculuk
54
24% / 56%
Süresi dolmuş
98
33%
Serbest
Benzer siparişler
We are looking for an experienced TradingView / Technical Analysis expert who can suggest and build the best combination of indicators for a profitable and structured trading strategy. This is not about random indicator stacking. We need someone who understands market structure, confirmation logic, risk management, and strategy optimization. The goal is to create a clean, high-probability setup with minimal false
Indicator 100+ USD
Does anyone know what indicator this is on the image because I'm looking for something like this but just a bit more sensitive. Speaking about the diamonds all the rest is irrelevant
Hello . Hello I already have an indicator on TradingView written in Pine Script. I need some modifications and fixes for the existing indicator. The indicator sometimes gives wrong signals and I want to improve it. I will provide the Pine Script source code. The developer should check the code, fix the problems, and adjust the logic if needed
DO NOT RESPOND TO WORK WITH ANY AI. ( I CAN ALSO DO THAT ) NEED REAL DEVELOPING SKILL Hedge Add-On Rules for Existing EA Core Idea SL becomes hypothetical (virtual) for the initial basket and for the hedge basket . When price hits the virtual SL level , EA does not close the losing trades. Instead, EA opens one hedge basket in the opposite direction. Original basket direction Hedge basket direction (opposite) Inputs
Kindly see details below BUY ALERT 1. Supertrend turns Bullish 2. On this candle , or the last 10, BBStops is Bearish 3. On this candle , or the last 10, price was < or = MA1 4. Instrument is in trend (STEP MA1 and STEP MA 2 are both Bullish) 5. Distance in pips between Lowest price during last time BBstop was Bearish, and the value of Step MA 1 at last bearish candle of Step MA1
EA requirements and necessary correction to be done . The EA monitors the PROFIT of open positions and turns ON or OFF the ALGO TRADING accordingly. By PROFIT I mean the SUM of profit + commission + swap. The EA will have two strategies, the INITIAL and the SECONDARY. Each one of them will be selectable by the user in the EA inputs. Let me explain here how the EA will operate: 1. INITIAL strategy: ·
Hello, I have a breakout EA with reversal logic. I own the full source code for both MT4 and MT5 versions. I need the modifications implemented for both MT4 and MT5 versions. I need several modifications: – Multiple reversals with configurable parameters – Breakeven functionality – Entry only after candle close beyond range + offset – Time-based activation – Alternative offset calculation logic – Automatic close at
Hi I have a simple task (hopefully) I have a custom strategy that I built with the help of Claude Anthropic - everything is finished and I zipped it with power shell but when importing it NT8 gives me the error message that the file was made from an older, incompatible version or not a NinjaScript. My folder structure is correct as far I can see so I don't know what the issues is and it's costing me too much to go
Subject: Development of Ultra-High Precision Confluence Indicator - M1 Binary Options (Non-Repaint) ​ Hello, I am looking for a Senior MQL5 Developer to create a custom "Surgical Precision" indicator for MetaTrader 5, specifically optimized for 1-minute (M1) Binary Options trading. The system must integrate three distinct layers of algorithmic analysis. ​ 1. Core Logic: Triple-Layer Confluence ​The signal (Call/Put)
Hello, I have an MQ4 indicator that works with a specific strategy. I want to modify some aspects and convert the file to MQ5. It's simple and won't take much effort or time for someone experienced in this field. Ideally, the person undertaking this task should be familiar with the MX2Trading software, as I will be using it to transfer the signals from the indicator to the trading platform

Proje bilgisi

Bütçe
40 - 90 USD
Son teslim tarihi
from 1 to 4 gün