MPTM's new home

[stimpy]

Hi all,

a few issues I have realized with MPTM.

It is not moving the SL on all occasions. I have used 2 different terminals with 2 mptms in various ways and it still happens so be warned.

[fxdaytrader]

which settings do you use (post setfile?), ...

[opieness]

I had the same problem with the SL not moving. I'm using the candlestick stop 1 candle back on 240. No BE or anything else. It moves to the correct position initially, but doesn't move as more candles show up. If I move the SL, it snaps back to that initial candle SL, even with new candles on the screen.

I would add a set file, but I customized the candle stop to the low/high instead of the close, added a few screen comments and a pip cushion to the high/low. Nothing that would affect the SL from moving.

[dudest]

I had the same problem with the SL not moving. I'm using the candlestick stop 1 candle back on 240. No BE or anything else. It moves to the correct position initially, but doesn't move as more candles show up. If I move the SL, it snaps back to that initial candle SL, even with new candles on the screen.

I would add a set file, but I customized the candle stop to the low/high instead of the close, added a few screen comments and a pip cushion to the high/low. Nothing that would affect the SL from moving.

Does the stop move with the candles when you used the vanilla (default) MPTM on post #1?

.

[opieness]

I had the same problem with the SL not moving. I'm using the candlestick stop 1 candle back on 240. No BE or anything else. It moves to the correct position initially, but doesn't move as more candles show up. If I move the SL, it snaps back to that initial candle SL, even with new candles on the screen.

I would add a set file, but I customized the candle stop to the low/high instead of the close, added a few screen comments and a pip cushion to the high/low. Nothing that would affect the SL from moving.

Does the stop move with the candles when you used the vanilla (default) MPTM on post #1?

.

OK.. Using MPTM direct from post #1, I created this .set file:

mptm 1m 5candle trail.set

.
Put it on the 1M timeframe to see results quick. Got same results on 15M. These are the only settings:

TrailingStop - true
UseStandardTrail - false
TrailingStopPips - 30
UseCandlestickTrail - true
CandlestickTrailTimeFrame - 1
CandleShift - 5

Problems: (I tried to fix all of these but this was way over my head!)

1. Comment says "Trailing stop on and set to 30". This is wrong according to the settings. Simple fix I made to my copy.

2. Buy/Sell trade - s/l doesn't adjust until it's moved about 25 pips from the open, then it finally snaps back to the correct s/l behind the 5th candle from when the trade was taken. It should just snap back at the next tick. Same whether in profit or not.

3. The s/l never adjusts from the 5th candle of when the trade was taken.

4. The s/l should also be on the High of 5th candle during sell, or Low of 5th candle during buy, not the close of candle. Simple fix I made to my copy.

My coding abilities are pretty basic, but an extra I would LOVE to see is this choice:
1. CandleShift = 5, sets s/l on the high or low of 5th candle back. (current setting, but also..)
2. CandleShiftHL = true, would set s/l on the highest or lowest candle of last 5 candles.
Seems like an easy add I may be able to do, once the above problems are fixed.

Thanks for the help!!!

[SteveHopwood]

I had the same problem with the SL not moving. I'm using the candlestick stop 1 candle back on 240. No BE or anything else. It moves to the correct position initially, but doesn't move as more candles show up. If I move the SL, it snaps back to that initial candle SL, even with new candles on the screen.

I would add a set file, but I customized the candle stop to the low/high instead of the close, added a few screen comments and a pip cushion to the high/low. Nothing that would affect the SL from moving.

Does the stop move with the candles when you used the vanilla (default) MPTM on post #1?

.

OK.. Using MPTM direct from post #1, I created this .set file:

mptm 1m 5candle trail.set

.
Put it on the 1M timeframe to see results quick. Got same results on 15M. These are the only settings:

TrailingStop - true
UseStandardTrail - false
TrailingStopPips - 30
UseCandlestickTrail - true
CandlestickTrailTimeFrame - 1
CandleShift - 5

Problems: (I tried to fix all of these but this was way over my head!)

1. Comment says "Trailing stop on and set to 30". This is wrong according to the settings. Simple fix I made to my copy.

2. Buy/Sell trade - s/l doesn't adjust until it's moved about 25 pips from the open, then it finally snaps back to the correct s/l behind the 5th candle from when the trade was taken. It should just snap back at the next tick. Same whether in profit or not.

3. The s/l never adjusts from the 5th candle of when the trade was taken.

4. The s/l should also be on the High of 5th candle during sell, or Low of 5th candle during buy, not the close of candle. Simple fix I made to my copy.

My coding abilities are pretty basic, but an extra I would LOVE to see is this choice:
1. CandleShift = 5, sets s/l on the high or low of 5th candle back. (current setting, but also..)
2. CandleShiftHL = true, would set s/l on the highest or lowest candle of last 5 candles.
Seems like an easy add I may be able to do, once the above problems are fixed.

Thanks for the help!!!

The trailing stop was the first function I coded into mptm about 6 years ago. The candlestick trailing stop I added a lot, lot later at the request of a user. I have never used it.

It is possible that the cst code does not work. Looking at it with the benefit of hindsight and acquired coding knowledge, I am amazed that I coded it within the trailing stop function rather than separately.

I might try to sort this out at some stage but am called upon to do quite a lot of coding here and have no interest in this, so don't hold your breath.

[danjuma]

Hi guys, I know Steve no longer wish to maintain/upgrade this EA any more. So, if there is somebody else willing to accommodate my request for an additional function on this EA, I would be most grateful.

The hedge trade settings has a setting for HedgeAtLossPips, which is number of pips you want the first trade to fall for a pair before the EA opens an hedge for that pair. One additional setting that would be most helpful is to be able to also set the amount of total loss for all current trades (i.e. in a basket of trades, the current UPL) before the hedging for a pair is triggered. So, basically two conditions before a hedge is triggered: 1) current UPL/DD down by a certain amount, 2) hedge a pair down by a certain number of pips.

Many thanks

[danjuma]

Hi guys,

Ok, I enabled the 'Add a missing Take Profit' feature, which subsequently put a red dotted line on my chart. This I then moved (by clicking and dragging) to change where I wanted to take profit. My questions/issues are:
1) Does it still work after it is moved (i.e. will take profit occur when price hits the line in its new position)?

2) After I removed the EA, this line (Add a missing Take Profit) remained on the chart. Switching time frames did not make it go away, and it does not show on the 'objects list' for it to be deleted. So the line is just stuck on my chart without anyway of removing it! Anybody else experienced this and knows how the line can be removed? Many thanks

[SteveHopwood]

Hi guys, I know Steve no longer wish to maintain/upgrade this EA any more.

Just so you guys know, I am not actually unwilling to upgrade mptm.

You must understand LUC. LUC stands for Law of Unintended Consequences. mptm was the first ea I published, back in the days when I used coding it as a vehicle for learning Crapql4. The coding is a disaster and it is a miracle that it works. Others have added to it without causing a catastrophe; they are stunningly brilliant people.

LUC kicks in when a tiny change here leads to the need for a change there but I forget the need for the change there. And I will. I coded mptm 7 years ago. Who the hell thinks I am going to remember what I coded after such a long time? Only an idiot.

And then we have the general usefulness of a proposed change. Put yourselves in my shoes:

• you coded a stunningly complex piece of software several years ago.
• you know that interfering with the code could cause chaos.
• someone comes along and asks for a specialised modification that nobody has asked for in the previous 7 years.

What is your reaction?

Exactly.

And that is why I seldom entertain requests for updates to mptm these days. This does not mean I will always refuse/ignore requests, but any that I do accommodate will have to be of wide interest to members here.

[danjuma]

Ok Steve, completely understand, and thanks for the reply.