Moving Average Crossover EA

• For every new candle the EA attempts to open a new position, according to the MA crossover direction:
• If MA1>MA2, open a BUY position
• If MA1<MA2, open a SELL position
• There is a limit for current open trades which is also set in the settings. If the number of open trades reaches that limit, the EA can’t open any new positions until another open trade closes.
• If the new position was not opened due to this limit, the EA simply moves on and attempts to open another new position on the next candle.
• Each created position has a Take Profit and Stop Loss value. Both values are set in the EA settings.
• The candle timeframe is set in the EA settings, NOT the current chart timeframe.
• The trading instrument used (e.g. EURUUSD) is also set in the EA settings, NOT the current chart instrument.
• Lot Size is specified in the EA settings.

• Instrument (free text)
• Timeframe: M1, M5, M15, M30, 1H, H4, D1 (text options list)
• Lot Size (float)
• Stop Loss (points, as an integer)
• Take Profit (points, as an integer)
• Open Positions Limit (integer)

Also, Both Moving Averages are configured in the EA settings as follows:

• MA1 Period (integer)
• MA1 Method (text options list):
• Simple
• Exponential
• Smoothed
• Linear Weighted
• MA2 Period (integer)
• MA2 Method (text options list):
• Simple
• Exponential
• Smoothed
• Linear Weighted

• Apply to: Close Candle
• Shift: Always 0 (zero). No shift.

• Every Attempt to open a new position specifying position type (BUY, SELL)
• If the position WAS NOT opened due to max limit of open positions reached, add a note in the Expert Tab with the current number of open positions
• If the position WAS opened, add a note in the Expert Tab with the position type, id and the updated number of open positions after the opening
• If a position was closed, add a note in the Expert Tab with the position type, id and the updated number of open positions after the closing
• If there is an MA1/MA2 crossover, add note in the EA Tab specifying the crossover direction and the current value of each MA.
• Any other relevant event or information the developer may consider.

• The code must be clean, efficient, commented AND, most importantly, organized in several separate subroutines. I plan to reuse this code as a filter in another EA in the future.