Sajjad Mohammad Nezhad Aghdam Tatooine Part 2

MQL4 전문가

작업 종료됨

실행 시간 5 일

명시

The only part that is a little different is 18.14, as I re read everything and was not clear enough. 

 

 

18.14) Recording the Entry Position

Every time Tatooine gets into a new position, it writes the position to a file called LogFileTxt.txt in the files folder.

*****EntryPostionName*****

EntryName:Tatooine

EntryTimeFrame:1440


This information should be written to LogFileTxt.txt


"01_Tatooine","GBPUSD",1440, 1.4187,"LONG","STOP","1.4181"


In other words:


"POSITION_ENTRYNAME",

"ASSET",

TIMEFRAME NUMBER,

PRICE,

"DIRECTION",

"STOP", (The Word STOP is the variable Name)

"STOPLOSS" (The actual stop loss number is the value here)

Thus, if Tatooine enters long a second time in a row, we should see a
"02_Tatooine" entry.

UPDATE for Tatooine V 1.0 - Clarification on ONLY NATURAL STOPS for positions that are not TAKEN.

In other words, Let's say the Tatooine buy algorythm has started going along untill it gets to position 01 Long 1D GBPUSD. However, let us further suppose that the Position is set to 2. This means that Tatooine will NOT be investing in position 1. Another Example: if SELL ONLY is set to true, then Tatooine will NOT be investing in in any Long positions, OK?

When Tatooine does not invest in a position, it does not have to set a fixed stop, or add additional pips to a natural stop, or use a jump stop. Instead, it only has to record the natural stop to the log.

Remember, the Natural Stop is written in the SmallBuy.txt and SmallSell.txt files, like this:


2016.04.18 12:35, 1.41870, 1.41811

DATE TIME, ENTRY PRICE, NATURAL STOP LOSS PRICE

When a natural stop is taken, Tatooine prints the following:

01 Long GBPUSD 1D 2016.04.18 12:35, 1.4187 was not taken, just recorded.
The natural stop was 1.41811. If this virtual stop is hit, Tatooine will move on to

take postion 02.




So, instead of placing a stop with the broker, Tatooine remembers the virtual stop of


1.41811


If the position is LONG and the price falls BELOW this number, then the virtual stop has been hit. If the position is SHORT and the price rises ABOVE this number, then the virtual stop has been hit.

Tatooine reports like this:


01 Long GBPUSD 1D 2016.04.18 12:35, 1.4187 has hit the virtual stop of 1.41811 and so is now searching for position 02



파일:

응답함

1
개발자 1
등급
(103)
프로젝트
205
41%
중재
17
29% / 71%
기한 초과
45
22%
무료
2
개발자 2
등급
(1)
프로젝트
1
0%
중재
1
0% / 100%
기한 초과
0
무료
3
개발자 3
등급
(219)
프로젝트
370
42%
중재
145
17% / 41%
기한 초과
124
34%
무료
게재됨: 38 코드
비슷한 주문
OFFICIAL MQL5 SOFTWARE REQUIREMENTS SPECIFICATION (SRS) Project Name: "Quantum-Shield 2.0" Institutional EA Platform: MetaTrader 5 (MT5) Execution Logic: Fully Automated Instrument: GER40 (DAX) Timeframe: 10 Minutes 1. ARCHITECTURAL MANDATE The Expert Advisor must be a monolithic, high-performance C++ based MQL5 application. No DLLs, no external python bridges. The logic must be entirely self-contained. 2. SIGNAL
Hi All, I am looking for an EA which I have attached the video of. It places a buy stop and sell stop with 250 pips above and below current price for every minute with SL as 300 pips and TP as 500 pips. If any of of them triggers in the minute other will be cancelled, it will not place any pending orders till either of SL or TP is hit and places new set of pending orders the very next minute of SL or TP hit minute
EA Development Request I need an EA with this logic: Detect channels / wedges / triangles Entry: Reversal at channel edge + engulfing candle Breakout of pattern Timeframe: M5 / M15 / M30 (scalping) SL/TP: Fibonacci or fixed pips (settings) Filters: Trend (H1/H4) Spread Time filter Settings: Lot size / risk % Enable/disable modes Max trades Requirements: Must work on XAUUSD No repaint Fast execution Send your proposal
I need a smart and profitable DCA or Martingale robot that can trade from 10,000 to 1 million cents with good profit. Please send me an ex5 demo so I can test it. It needs to be compatible with 2-digit or 3-digit brokers by default. Source code will be provided upon completion
Specification I need a mt5 Expert advisor EA to manage intraday trades with strict risk management. The EA must -Handle between 5 to 8 clean trades a day max altogether throughout all 3 sessions. no big news trading times and no overnight trades -Use 1 % on forex pairs and up to 2% on XAUUSD risk per trade - Automatically calculate lot size based on stop loss -use fixed RR ratio [1:2] For forex pairs
The Expert Advisor (EA) must work with any custom indicator that provides Buy and Sell signals through buffers. The EA should read signals from the indicator and execute trades according to the defined rules. The EA must be universal and able to work with different indicators as long as they provide signal buffers. I will share the rest of the details with you shortly
I have an existing TradingView Pine Script. I will provide the Pine Script source code after agreement. Goal: Convert the logic into MT5 (MQL5) and build an EA. Phase 1: Create MT5 indicator that matches TradingView signals (M15 only) Phase 2: Build EA with strict execution rules: max 4 trades total one trade per symbol gold lot limit (max 0.02 total) reversal logic (close then open opposite) no re-entry after manual
Requirements 1.Robot for Entry and Exit rules as per my indicators. 2.Back testing which can work on all time frames. 3.A system which i can modify later on as well according to my studies
I have been working on an EA that is based on Ichimoku cloud and SMC internal blocks for stop loss. ENTRY BUGS: 1. I have entries issues with the chenkou and price action. It is entering trades when chenkou is poking through the kumo. This shouldn't happen. There should be a candle close with chenkou above kumo or below. 2. Another entry issue with other criteria for tenkan and price action also these entries are
MT5 Dual-Account Hedge Synchronization EA I need an Expert Advisor for MetaTrader 5 that runs on two trading accounts (same broker, same VPS). The EA must work in a bidirectional way (both accounts run the same EA). Core Functionality: - Detect when a trade is closed using OnTradeTransaction() - Capture: symbol, closed volume, account ID, timestamp - Send this data to the other account via a shared local file On

프로젝트 정보

예산
125 USD
기한
에서 1  20 일