trabajo MQL5: 032518 Request

Descripción

Tarea técnica

is modification request is centered around creating "as needed" limit orders created until the desired pips goal "y" is obtain. Meaning,

limit order positions are created until the "y" is obtained.

The opening positions are a limit "buy" position and a limit "sell" position opened "x" pips away from the current price.

Example-1, let's say EUR/USD is currently @ 1.1000 and x=10

A limit buy position will be placed @ 1.1010

-AND-

A limit sell position will be placed @ 1.0990

The closure of these positions is determined by "y".

Example-2, let's say EUR/USD is currently @ 1.1000 and x=10 y=10

A buy limit position will be placed @ 1.1010

-AND-

A sell limit position will be placed @ 1.0990

If the buy position is opened @ 1.1010, then the closure will be 10 pips -- as determined as "y".

In this case, it will be 1.1020 and the position will be closed along with the removal of the sell limit order @ 1.0900 even

though it was never opened.

When a set of limit orders are placed and both the buy and sell orders are opened prior to reaching "y", this is called a "grid lock". Thus, when a "grid lock" happens,

an additional set of limit orders are placed--an additional set of buy and sell limit orders. The placement of the additional set is "x" away from the 1st set of limit orders.

Example-3, let's say x=10 y=10 using Example-1

A buy limit position was placed @ 1.1010 and was opened and did not reach "y"

-AND-

A sell limit position was placed @ 1.0990 and was opened and did not reach "y"

A 2nd set of limit orders are placed "x" away from the 1st set of limit orders. In this case this would be the following:

A buy limit position placed @ 1.1020 since it is "x" away from the 1st buy limit order @ 1.1010.

-AND-

A sell limit position placed @ 1.0980 since it is "x" away from the 1st sell limit order @ 1.0990.

With the limit orders reaching its 2nd set, the "closure" would be determined by "y". Remember "y" is the net positive difference off all present opened position.

Once "y" is achieved, all positions are closed and removed. Thus, ending this cycle.

Example-4

Continuing fomr Example-3

In the 2nd set of limit orders placed, the buy position was opened @ 1.1010 and reached "y". In this case, "y" will be @ 1.1050

sell-1 opened @ 1.0990 closed @ 1.1050 = -60 pips

sell-2 never opened n/a

buy-1 opened @ 1.1010 closed @ 1.1050 = +40 pips

buy-2 opened @ 1.1020 closed @ 1.1050 = +30 pips

----------------------------------------------------------

Sum = +10 pips

y = 10 pips

Once "y" is achieved, the "cycle" starts again in Example-1.

Since the market is the market, the total number of "grid locks" occuring will always change. Thus, the number of sets of limit orders needed to achieve "closure" can vary.

Thus, whenever a "grid lock" happens, an additional set of limit orders is placed.

If after a new set of limit orders is placed and a "grid lock" doesn't occur, then the next focus would be "Y". "Y" is the total sum of all present opened positions.

This is the process of this request. It is as follows:

1. |START|

2. Define "X" and "Y"

3. Place 1st set of limit orders

4. Did Grid Lock occur? Yes or No

5. If No, proceed to "closure" determined by "Y". Cycle Ends. Start over.

6. If Yes, place 2nd set of limit orders. Placement of orders is determined by "X".

7. Did Grid Lock occur? Yes or No

8. If no, proceed to "closure" determined by "Y". Cycle Ends. Start over.

9. If yes, place 3rd set of limit orders. Placement of orders is determined by "X".

10. Did Grid Lock occur? Yes or No.

11. Repeat this process as needed until there is no "Grid Lock" and "Y" is achieved.

In the already provided robot "Montiero_ea" I would like to keep the following variables:

nCycles

Base

Magic

nCycles is number of times you want the robot to complete a closure.

Base is using the balance to determine the number of "lots" for the limit orders.

Magic is the instance number used.

I forsee (as an example) of the following to be the variables|value for this robot request

Variables Value

_1_ __EA Settings__

nCycles Same as Montiero_ea

currencyPair Same as Montiero_ea

Base Same as Montiero_ea

X see example above

Y see example above

Magic Same as Montiero_ea

<END>

If there is any clarification needed on any part of this, please let me know and I will provide greater clarity.

Han respondido

Evaluación

(94)

Proyectos

148

59%

Arbitraje

38% / 13%

Caducado

17%

Libre

Ha publicado: 1 ejemplo

Solicitudes similares

I need a fully automated trading robot designed to generate consistent profits while strictly controlling risk and minimizing losses. The robot should use a combination of strategies, including trend-following, scalping, and price action, and must be able to adapt to different market conditions such as trending and ranging markets. It should analyze the market using indicators like Moving Averages, RSI, MACD, and

Seeking developer service to code an EA. Interested developer must have good experience and understanding on how ORB and FVG works, and agreed to the terms below : 1. Shall demonstrate a fully functional EA that operates as specified in the requirement and function automatically as requested in real-time environment (forward test - demo/live), regardless of good results obtained in strategy-tester. Backtesting

Hey guys, looking for a crazy good EA / Indicator that can either help me for futures trading (eg. Topstep, Lucid Trading etc) https://t.me/nqsniperz - telegram Or looking for a CFD EA that i can run on personal accounts Budget is very high and negotiable. https://t.me/nqsniperz

I’m looking to partner with an experienced developer who has a proven, working EA that delivers stable and consistent monthly performance . A bit about me: I run an active trading community and a TikTok channel that consistently drives targeted traffic and potential clients into my ecosystem. I’m now looking to collaborate with the right developer to scale EA distribution and monetisation together . What I’m Looking

am looking for an experienced MQL5 developer to build a high-frequency trading Expert Advisor (EA) for XAUUSD (Gold) on M1 and M5 timeframes . The EA must include advanced execution logic, dynamic pending orders, risk management, and news/session filters. Clean, efficient, and well-documented code is required. Strategy type: Scalping (fast trades, quick profit). Very fast execution logic (optimized for speed). Goal

Title: MT5 EA Needed – Prop‑Firm Compliance Tool (SL/TP at Entry, 60‑Second Hold, Daily Profit Cap, 0.5% XAUUSD Risk) Description: I need an MT5 Expert Advisor that enforces prop‑firm compliance rules for Instant Funding accounts. The EA must NOT trade automatically — it should only monitor and control my manual XAUUSD trading. I trade all sessions, so there should be no time restrictions. MY TRADING STYLE (Important

1. Project Overview Asset: XAUUSD (Gold) Timeframe: M1 (1-Minute) for execution; M5/M15 for trend filtering. Objective: Execute high-frequency scalps during peak liquidity (London/NY overlap) to capture 10–30 pip movements with high precision. Core Logic: The "Poverty Bot" strategy relies on Mean Reversion combined with Momentum Burst (Price Action + RSI/EMA filters). 2. Strategy Logic (The "Poverty"

I need any highly profitable robot which can trade small account like 50-100USD and any currency pair(s) The robot should avoid trading around news time and have good risk management. It should use any strategy which is profitable and not those unacceptable by brokers. Demo versions will be required before selection

Hi, I hope you doing Greate, Let me share details , so the original EA already working but you can check and verify everything fine.First you verify that all original EA features are working correctly then add a user dashboard showing the number of detected zones, buy sell both none status, and an on off button. also ensure mitigated zones disappear properly and that trades follow the zone rules, and integrate the

I need a high-speed Expert Advisor (EA) for MT5 designed specifically for XAUUSD (Gold) scalping. The bot should focus on fast entries and quick profits with high efficiency. Main requirements: 1. Symbol: XAUUSD (Gold only). 2. Platform: MetaTrader 5. 3. Strategy type: Scalping (fast trades, quick profit). 4. The bot should open trades frequently based on fast market movements. 5. Small Take Profit (quick profit

Información sobre el proyecto

Presupuesto

30+ USD

Calidad de la tarea técnica
Calidad de la verificación de resultados
Disponibilidad y habilidades de comunicación