Price Action Trading with Indicators! The Freebie System

Now this is exciting!!

Why is this thread in the recycle bin?

Upgrades are FINITO!

Done. Stack, Trailstop, BE, BE+Lock have been tested and work.

The stack function will now start to look for new stack opportunities whether or not the previous trade is BE. It does however only start to look for new stack trades when the profit of the previous trade positive

Here are the Stack Inputs and what they mean
StackTradeStep = 0 (Change 0 to some number and that is the pip interval for new stack trades. 0 means do not do any stacking)
StackLotsMultiplier=0.5 (This multiplies previous lotsize for new stack trade, if you enter number > 1, EA will set it to 0.9)
MaxStackTrades=0 (if left as default, EA will create new stacks up to margin allowable, if u set a number, EA will create up to that number or up to margin allowable, which ever is first)

No changes to the BE, BE+lock and TrailngStop options. All where tested and found to work

See Next Post, previous files were updated.

If anyone needs any help deciphering the inputs let me know.

Zero Divide Fix.
Folks, the zero divide beast showed up during back testing (keysharp pointed this out).
I took a look and once and for all fixed the issue. I revamped the function that makes these calculations. This mainly happened on the strat tester but let me know if u see this problem when applying the EAs on live/demo charts.

Guys, I been cleaning out the software in the last couple of version so you may see some new bugs due to missed items that I may have missed placed while cleaning the code up. Eventually the code will be bugfree clean and operate without any problems.

Thank you!!!!!!!!

Just in time for me to switch over to the new versions.

Just to be clear, The "Starting Bal PercentProfit" is a dynamic value that is being affected by the DD and not just the closed trades, did I get it right this time?

[EDIT]
I'm going to try the WeeklyPercentLock this week, last time it didn't perform too well, has this been tested in this release?

The intention of this Starting Bal PercentProfit was just to have measurement that you could use to tell how much the account had gained or loss since the start of trading it with an EA.

The Starting Bal Percent is basically the percent gain since u started to trade with that account or EA.

So for example. When I started to trade my OANDA live account, I had $500.
Now the account balance is $130. So the Starting Bal PercentProfit= (130/500-1)*100=-74%

That means that my account is 74% down from $500, which is what I started with.
If I had $500 right now as equity then Starting Bal PercentProfit= 0%
if I had $700 then Starting Bal PercentProfit=+40%.

Those numbers just measure how far your account has gone UP or DOWN in terms of percent
since it STARTED or you can change the initBal in the GlobalVariables window (press F3) to whatever balance you have at the moment.
You would do this whenever you wanted to record the start of the use of new EA. You active the EA, and then change the initBal to the current account balance.
This way you have a measurement of how the EA did since it started with $xxxx account balance. No need to open another demo account,,, etc etc,



WeeklyPercentLock:
I changed the code and made sure the logic was exactly correct on this one. I did test it, while I was trading that EA on my live account last week LOL.
Remember?? I mentioned that I had closed out the BOLOSO account at 3.1% cause as I modified the EA I would compile it and in one of them the EA thought that it had to close ALL TRADES cause the weekly target profit was -245% or something like that. Or course my account was at +3.1% which more than qualified LOL.
I recall that I also testes the PRofit LOck cause at one point the EA was just closing ALL immediately cuase it thought that LOCK was satisfied. I fixed that. Once I saw the fix I continued on with the other functions. I didn't re-test it.

I am very confident these fixes are working now.

I am getting the code ready. ALOT OF CLEANING UP and I am also improving the flow and logic. I plan to release the source soon, cause, I think we are fairly at the end of doing anything different other than add new trend indicators or maybe more LOSS protection functions. The core approach stays fairly the same, it has not changed since ... we did 3C. Even 3Cs core approach does not change. All we are changing right now are MM and LOSS control functions. So basically it's almost a done deal. I guess the next thing that could be done is to create an interface of buttons with like a panel display of all the Pairs (the ones u pick).

Besides, I got like 3 projects that are looking very promising. One they are final, I hope to share them with you, so you can use them along with these EAs.

I take it that my ATR multiplyer is too close. Maybe should be 3 or 4.

John go to the history and show the entry, stop, take profit numbers so we can calculate if the ATR was too small that the STOP LOSS function took it out.
I can't tell but was it a profit or a loss?

It was a loss.

Price= 1.29224
S/L = 1.29070
T/P = 1.30223
Cl/P = 1.29182

Here is another one. A loss because of commission. I have moved the multiplyer to 3, let's see what it does.

John: send me yer set file. I need to run it myself. Tallimex right?Oh' in the journal are there any errors??

I sent you the set file and there were no errors in the journal.

Krahs!!! I think I know what the problem is. Even though I fuxed the BE logic and compiled it. I must of posted the previous copy with the same version number. Ok stay tuned, I will test it anyway so icna see it working properly.

Well that's why we test and search and understand. Glad I can help, even though I feel helpless most of the time.!

. I could of sworn I uploaded the correct files. I saw the new code and clicked on COMPILE. I even verified that the new ex4 had been just created.
But then this happens. I saw the same exact problem u are experiencing last Saturday when I was testing it. I did a step by step and it turned out that the BE function was making the EA think that it was below the LOCK. So at the instant a trade opens... it's closed. I fixed it and tested it in combination with the Trailingstop and Stack functions,, it was working nicely.

I just checked and low and behold the source code does not have the updated coded. Yea, the exact code I modified is not there... how is that?
Well here's the deal lol, in order to not have a gazillion Expert/Indicator folders I only have one of each on the cloud (dropbox). So where ever I go all I do is create a new MT4 folder and POINT the Expert and Indicator folders to those on the cloud. It is REAL convenient, especially when I travel. But here's where it gets tricky.
supposedly if I make a change it should be reflected in the folder that reside in dropbox, right? Dropbox keeps a copy locally and syncs it with what is on the cloud. Recently I have noticed that DropBox has not been sync the files. So what you have is older versions that have not been updated either on the cloud or locally. In this case I think it's on the cloud. I know I made the changes and they are probably on my machine on the local copies.

Ok ok.. enough... I'll get it all synced when I get home and re-upload the files. Plus I'll forward test it with the set file u sent me on tallinex to see the trades working. Problem will be fixed...

aroxalot:

Don't know, I just started posting around post 300 or 330 ... it was already in the /bin.
I think it's best cause it keeps the riff raff away LOL Joking

Thanks for the update, but I believe you are speaking Greek!

I screwed up and I am going to fix it... hows that?? LOL

UPDATE to EAs.

Folks:
I saw the damn mistake. The STOP Conditions were the opposite!! Instead of looking to close trade if they were negatvie the EA was looking to close trades if they were immediately positive LOL and of course by the time it took place the commission wasn't even covered.

Alright... new versions... this verifies that the files are correct.

John I have setup Tallinex to use 3C with the set file you provided. So I should pickup any errors u might see.

Guys:
There is problem with the STOP LOSS condition. I removed one of the conditions.
Please download these EAs, these have the change.

If you still see your trades are getting closed too fast. Set the CheckBarsBack=0;

I will continue to look into this. John using the ATR has no affect on this, so that is ok.