Easylanguage Developer needed to assembly trading system for Multicharts platform with some add-ons

Вescription Task: to assembly a technical analysis based algorithmic system from Multicharts Signals and Indicators using Easylanguage script. Maybe It can include some add-ons taking in accounts restrictions of basic features (e.g Globals, DLLs). The trading system includes the following components: 1 Money&Risk management 1.1 Position Size 1.2 Opened positions limit 1.3 Max Drawdown Limit 2 Entrance logic 3 Exit logic 3.1 Stop Loss 3.2 Take profit 3.3 Time expiration 3.4 Stop Loss modifying 3.2.1 Breakeven 3.2.2 Trailing 4 Scale-In logic 5 Scale-Out logic I am ready to send detailed Specification 1 The system should be developed using EasyLanguage for latest Multicharts platform 2 Specific logics should be stored in separate signal files and to be assembled in one system then (according to MC features) Note: all Signals used in this Specification are implemented in basic MC version 3 Modules should exchange data between themselves via accepted MC features (e.g. Globals, DLLs etc) 4 Inputs should be stored in external file. They should be saved after optimization (buy user or automatically) and loaded form a text (csv) file before run of trading at stream data 5 Open&Close logic for thread of position can be differ from MC original one because of custom features such as trailing stop, scaling in&out algorithms In case there are no solutions to manage positions with MC standard features, the custom virtual positions should be stored in dynamical list (queue) and being handled via "foreach" structure Thus, trading results with information of custom positions (e.g. orderID, open-close order type, open-close time, open-close price, volume, gross-net profit, open-close slippages, open-close processing time, exit type (SL or TP etc) etc) should be stored in external trading log file (according to MC features) Eventually, total amount of Profit for MC log and custom one should be equal, nut number of position can be different 6 Stop Loss modify logic should be implemented via both approach: modification of prior opened Stop order and algorithmic modification with a real order to be sent after an Close event I.e. Stop order can be sent and modified at Broker/MC side or emulated with custom algorithm 7 Code should be correctly work in both real (paper) and backtest/optimization modes with equal results at the same period (taking in account requirements of Items 2, 3, 4, 5)