C7 BOT 2.1 __DESCRIPTION Uses advanced channel detection capabilities to determine the probability and extent of the breakout and will adapt to it. This bot operates on only stop order entries, is not a scalper, delays won't matter at all and slippage and small spread differences won't kill you (but you should avoid erratic variable spreads and terrible spreads will eat in to your profits especially on 5m charts. For instance EU spread plus slippage should not exceed 2 pips.) It can use strategically trailed stop-losses based on big round numbers as many successful traders. Message me for the newest settings bendx77@gmail.com and or check the comments area of the market for newest docs. Check 'C7 Bots' signal for real live results. Reports of back-tests are available in the MT5 version comment area contained inside the latest .zip. This is a breakout bot and the simplest way to describe this bots function is, first it detects a horizontal channel then it places stop order(s) when price moves away from the channel wall deep in to the channel. It is recommended to run this bot on many pairs and time-frames like the 'C7 Bots' signal is. Most settings are actually in ATR instead of pips. This allows us to create blanket optimizing strategies as well as adjusts automatically to current market conditions. Money management is simple. Either specify a percent of equity or just specify lot size. This bot generally produces results that also work well in testers forward tests, especially if all the MT5 version optimization features are being taken advantage of. But please don't believe what I say, check it out for yourself. This particular bot has no hard coded tricks to generate false positive forward tests. It simply places stop orders with wider-than-scalper sl and tp and then trails the stop in a strategic manor. It makes no calculations on ticks or tick patterns and only analyses completed bars. Therefore you will be pleasantly surprised at the correlation to tester forward tests and real live results. OBV not perfectly matching back-tests and all brokers are different. I will warn about brokers with spiky data and or erratic spread variations in particular may do exceptionally poorly. Again, you should test yourself. I can only speak for MQ data, and OpenFX data of which I am pleased. I have done a small amount of testing on other brokers and was pleased with those too but do recommend you to test yourself. The signal server is on OpenFX data of which I am especially pleased at the crossover of optimizing in MT5 MQ data and transferring settings to OPenFX. __ABOUT I originally designed this bot to run on my own personal account but when I saw how easy and safe it was to sell bots on the market, I decided to give it a try and sell my bots here. __MT4/MT5 The MT4 bot was designed for production. MT4 itself is more friendly to multi orders on single symbols therefore I use this version to produce the signal and have 7 different TF/Symbol combos at the time of writing this although I intend to add more. The MT5 version can also be used for production but can not currently handle multiple instances for a single symbol. MT5 version was designed for optimizing. MT5 itself is a lot more powerful for optimizing and C7 bot truly unleashes more than enough of this power. The new PUREDD mode optimizes toward smoother equity curves with its introduction of an algorithm which utilizes a 'trades since last peak' stat as well as DD and profit. We can also specify a minimum profit factor and minimum trades which, if not met, will penalize the frame to a degree set by the user. Contains also a separate mechanism to slowly increase lot size over time in order to "trick" the optimizer in to preferring later(more recent) performance over earlier performance. MT5 version also contains a visual optimizing module so you can see the optimization and equity curves as they are produced. The MT4 version can be used for optimizations but lacks many of the features in the MT5 version for optimizing. If you want to do your own optimization, MT5 version is recommended to do the optimizations, even if you will be running MT4 for production. MT5 is available for free and you can use a free demo server for the data. Much effort has been put in to testing to make sure the MT4 version and MT5 version act the same. You must remember that settings can only be copied/entered in manually from/to MT4/MT5 versions as .set files are not currently interchangeable between MT4 and MT5 and actually don't even load all the drop down settings properly sometimes to/from tester/chart of MT4. (The settings ARE compatible of course but the .set files won't load properly if you try and load a .set file from another version of MT.) __AUTO BACK ORDER REPLICATOR I have added a mechanism which when it first loads, the ea will try and detect if an order should have been placed in the recent past and then if so, places the pending stop order. In fact, in 2.0, this mechanism runs each time a new channel is detected. In case it is your first time running the bot or maybe your computer crashed and you missed a signal or perhaps you accidentally deleted an order. Rebooting the C-7 will place orders that you missed or deleted most of the time. But this mechanism is not perfect. In some cases, it will not be able to detect if an order would have placed in the distant past and that this order would still exist. If you know an order is supposed to be there you can trick the bot in to placing all pending orders by temporarily setting CHANNEL_CORE to 0.001. (WARNING: DO NOT CHEAT by forcing orders out that the bot did not / should not take. Don not use this trick if you are unsure.) If you reinitialize and set the CHANNEL_CORE to 0.001 before it initializes the orders will be immediately placed as long as a channel exists. If you set CHANNEL_CORE to 0.001 without restarting the bot, then the orders will be placed at next bar open. If a channel does not exist and you know an order should be there, you are unfortunately out of luck, although it is just a matter of time before the EA was going to delete the order due to no channel existing anyway. If you do mess with CHANNEL_CORE then please DO NOT FORGET TO SET CHANNEL_CORE BACK TO ITS ORIGINAL VALUE! __OPTMIZING The settings for the optimizing templates are set for an optimization process that I found to work best going forward. There are many factors which play in to this. The lot-size does matter, a percent should be used as opposed to a fixed lot size to allow the size to fluctuate based on the stop-loss. Raising it up from the 0.1 recommended setting will place more emphasis on profit and less on draw-down. Currently it is very tuned towards reduction of draw-down. There is typically a note in the description string of how long to run each optimization but I encourage you to experiment. A word of note: To speed up optimizations 10x, set swing-point type to "none" and optimize that way first then re-optimize the swing-point settings __SETTINGS ** A warning about loading .set files provided. Sometimes they do not load properly. I'm not sure why but it is a problem I've had with MT4. You should double check the settings match after loading them by opening the .set in a text editor. ESPECIALLY CHECK THE DROP DOWN ENTRYS such as true/false settings. d99="[GBPUSD][5]Default-Settings-Optimized-02/25/2014/V1.6...Please check signal 'C7 Bots' for real results on live account. Please message me for the newest settings. bendx77@gmail.com. Please check the comments area for settings and docs."; //Description-->This is just any string that contains the symbol name and time frame in minutes square bracketed. The bot will not run if the TF and symbol are not place in this string within square brackets. This is a safety mechanism requested by my users to make sure you don't run the wrong settings on the wrong chart/TF. d0="***********OPTIMIZABLES";//***********OPTIMIZABLES-->Remark d0a="***Definition of New Wall";//***Definition of New Wall-->Remark SWINGPOINTONLY = false;--> If true, will not draw channel walls unless the swing-point criteria are met. This is just for testing. MINSWINGSPACE = 25;-->Minimum bars between swing-points for touch defined walls MAXSWINGSPACE=500;-->Maximum bars between swing-points for touch defined walls MINSWINGS=2;-->Minimum touch points for touch defined walls [2-4] MINSWINGOUTRATIO=0.8;-->Minimum distance a swing-point must swing inwards towards the core to be counted as a swingpoint, expressed in fraction of core. ALLOWANCE=1;-->Tolerance of touch-point accuracy expressed in ATR SWINGTYPE=none;-->Swing type. Experimental testing only. Use normal or none for production. sd0b="***Definition of Channel";//***Definition of Channel-->Remark MAXCHANNELWIDTH=17.5;-->Maximum width of channel expressed in ATR CHANNEL_LENGTH =450;-->Length of Channel in bars ExpressCore=ePercent;-->The units for expressing CHANNEL_CORE. (either percent or ATR) CHANNEL_CORE=7.0;-->Core of the channel in ATR or percent. Price must reach core for an order to be placed. NOCHANNELBARS=260;-->Timer in bars for how long the condition of "No Channel" is tolerated before orders are deleted. d0c="***SLTP and Order Criteria";//**SLTP and Order Criteria-->Remark STOP_LOSS=3;-->Stop Loss in ATR TAKE_PROFIT=9;-->Target in ATR TRAILING_STOP=0.5;-->Trailing stop in ATR CUSHION=-0.1;-->Distance from channel wall for orders to be placed in ATR. Can be negative. SAR=true;-->Stop and reverse mode. If false will simply exit an open position if the opposite wall is hit. If true will enter the new position AND exit the current position. d0d="***Big Round Numbers";//**Big Round Numbers-->Remark BRNSTOP=true;-->If true will use the BRN stop mode. this works in conjunction with Trail Stop. Will keep stop behind a BRN for protection. BRN=.005;-->The actual BRN level BRNSTOPLOSS=0.6;-->The distance behind the BRN the stop will be placed when trailed. expressed in ATR. d1="**************RISK & ORDER INFO";//**************RISK & ORDER INFO-->Remark SLIPPAGE=2;-->Allowed slippage for orders LOT=3;-->Lot size either in percent or lots. LOT_TYPE=percent;-->Lot size type. can be percent or standard. Will never risk more than 50% of available margin on a single order. if you get the margin warning, please reduce your risk size. MAGIC_NUMBER=8677;-->Magic number to identify which orders it controls. Should be unique to other instances on the same symbol. "****************ATR Bars";//******************ATR Bars-->Remark ATR_BARS=15;-->Averaging period for the ATR indicator. d2="**************TESTER INPUTS";//**************TESTER INPUTS (must not be 0)-->Remark __THE FOLLOWING IS ONLY AVAILABLE ON MT5 VERSION TesterMinTrades=100;-->Minimum trades. Frames that do not meet this requirement will be penalized to the PENexp exponent. TesterSharpWeight=5;-->Weight of SR in custom score. TesterDDRatioWeight=5;-->Weight of DD in custom score. TesterPFWeight=25;-->Weight of profit factor in custom score. TesterProfitweight=1;-->Weight of profit in custom score. ScoreMultiplier=10;-->To adjust score whe its too big or too small to read. PUREDD=true;-->If true uses an alternate mechanism for custom score involving draw-down, amount of trades between peaks, profit factor, amount of trades and profit. If true only MINPF, TesterTrades, PENexp and TesterLotinc will be used. TesterLotInc=0.005;-->Slowly increases lotsize over time so the optimizer prefers later performance over earlier performance. MINPF=1.33;-->Minimum Profit Factor. If not met the frame will be penalized to the exponent of PENexp. PENexp=5;-->Will penalize depending on how far from the requirement the frame is. The higher this number the steeper the penalty curve.