quick update on a triger

no rush Mark  take your time thanks

Hi soulreaverz, I've some cases in which I've duplicated opening back bet, like the trigger doesn't see that there already is in place an unmatched back bet.
do you see also something like that ?

thanks mattia

i guess it never happened to me, the things that happens is when the back bet enters the lay bet isnt placed..when the game is 2+m in play it shud had closed the position at 2m and it does not and sometimes it closes at 15m 20m.. but Mark is working on it we shud have a update to test it soonish xD..

Hi
Update: I am still testing it. Because the prices you offer move when the market moves (you are always best price), it is difficult to test in test mode, because they do not get matched. I want to test some more tonight and I hope to post a trigger file for you tomorrow.

hi MArk!
thanks for the update on the trigger, ya in test mode shud be difficult to test it well cause of the price movement idd..looking forward to test it aswell  thanks!

Hi
Attached please find the update.

New Constants:
price_dif_ticks  match at best price if lay price is greater than back matched price + price_dif_ticks
vol minimum matched volume in the market

Testing notes:
If you have an unmatched back bet waiting and mbo is reached and the price changes, it will cancel the unmatched bet and not bet again (no bet).
Distribute loss will match the lay bet at best price, and then red-up. You need to have the setting Allow Small Bets ticked.
The more markets you are monitoring, the slower the refresh rate. You can disable the Set refresh trigger block and use your own refresh rate.
I think you should make mso longer than 2 minutes.
The different OU markets move at different rates. e.g. U5.5 will move down quicker in the first 2 mins than U2.5.

Please test the trigger in test mode. If you want more realistic chance of being matched you will need to use real mode. Please use small stakes (I have preset the ta constant to 4.00)

Because this trigger uses lots of repeating triggers for the fill or kill (always at best price), it is recommended that you use a “circuit breaker” in case of any error. e.g. Settings > Betting Options > Banking > Stop automated betting etc….

hi markv, thanks a lot for the update im testing it now in test mode and tomorrow if all is good i will test with real money.. you tested it in u 2.5?

Hi
I tested in 2.5, 3.5, 4.5

best results were on what?

i just got home and i see this..how can it be? lol something is not correct Mark? and sometimes it places a back bet then a lay bet then another back bets?..and other times it doesn't make hedge on loss or profit.. any clues? print screen attached mark

Hi
Thanks for the screenshots. There is something wrong with distribute loss. I will look at it.

ya i thought it was something not working right it was a very huge loss i got scared   ehhe ill continue testing this one for the rest of the day ill post if i find something abnormal! thks mark one more thing mark, sometimes the back bet still there if not matched witch result in less money to bet on the other games.. the back bet remains there unmatched

Hi
Next update:
Corrected Distribute Loss after x mins inplay
The unmatched back bets should be cancelled when the market turns inplay. I have added a cancel unmatched back bet after mso.

Testing note:
As is always the way with scalping for a few ticks, the prices and liquidity must be there. I found closing problems where there is a big gap in the prices after inplay, and sometimes no lay prices. This means the distribute loss will not work until there is a lay price offered.

I can add a condition so the trigger checks there is a lay price, and the gap is not too big, but it will delay closing if there is low liquidity.

This trigger (and all scalping triggers) work best in high liquidity markets.

Please use test mode to test the trigger.

hi mark, thanks for the update.. i just loaded all under 2.5 markets in this case and the refresh rate is at 200.. so what you advice to do in this case? since i wanna motorizing all day markets its possible? the refresh rate then il then interfere with the market and sometimes for what i see it doesn't close cause of that when it shud? its this? OR I HAVE TO FIND A FILTER FOR THE GAMES?

Hi
It is not practical to monitor so many markets at the same time plus bets refresh and market score. It is best you work out according to your refresh rate you want, how many markets to monitor. Below are some figures you can use:  
BetFair allow you 20 free data requests per second.
20 markets refreshing at 1 sec = 20RPS
40 markets refreshing at 2 sec = 20RPS
etc..
bets update (weighted as 5 requests ) every 3 seconds = 1.7RPS
statement update (weighted as 5 requests)
market_score
silks
market locator
If all your data requests exceed 20RPS (or the RPS in Connection Monitor), the Connection Monitor will start queuing the requests, and the refresh rate will slow down.

Things you can try:
You can disable the first trigger block which sets the refresh rate to the number of markets being monitored. It will then use your own refresh rate.

I think it would be a good idea if you use Market Locator to select markets with a good traded volume. This will reduce the number of markets being monitored. You can also use Scheduler to add markets every few hours.

For real mode (but do not use it until you are happy with the trigger) you can enable the trigger which deletes markets which are green or have no trade.