Examples 11-15
Example 11. We want an application where it will automatically place lay bets when in play. E.g. when 2 runners go under odds of 2.0 or 3 runners go under 3.0 etc.. We do not want it to place the lays until both sets of odds are under the figure. This tends to happen at the end of the race when the prices are fluctuating a lot. Can MarketFeeder Pro do this on trigered bet?
Here is the trigger that I would suggest:
Cell: "Second Winner Lay Price"
Condition: "is less than"
Trigger Value: "2.0"
Action: "lay"
Price: "best"
Amount: you select
Market: select from the drop-down list OR choose "All In-Play Markets"
Selection: either "All Except Winner" or "All Selections" - depending on what selections you want to lay on
Active: "once in-play & wait"
Setting up this trigger will lay on the selections ONLY if at least two runners are priced under 2.0. If you want to condition three runners, then set Cell column to "Third Winner Back Price".
Update:
Since usually it is reasonable to wait a couple of seconds till the prices settle after the event goes suspended, we suggest that you make some amendments to the trigger:
Price: "IF(Now() - event_off >=0.0001157, best, 0)"
This way the software will wait for at least 10 sec after the off, and only then will place the bets. In order to use formulas in the Price column set "Max attempts on failure" option to "-1".
Example 12. If the odds are low, the time in the match is towards the end of the game and the amount staked so far is low, I would like to stake more per bet than in the beginning of the game.
You must use three pre-defined variables available in MarketFeeder Pro to make your stake amount depend on them:
- back_price
- back_matched
- event_start
If you are watching lay side and your bets were previously laid, then instead of back_price and back_matched you'll be using lay_price and lay_matched.
Variables of this kind are automatically recognized by MarketFeeder Pro and interpreted according to the current market situation.
So in order to make your bet amount dependent on the above factors, modify your trigger as follows:
Amount: "=IF(AND(back_price<3, NOW() - event_start > 0.052083, back_matched<10), 100, 10)"
Please note: the values used in this expression are taken as an example and you must correct them according to your strategy.
So, the Excel function "IF" returns the second parameter if the condition in the first parameter is true. Otherwise it returns the third parameter.
The Excel function AND returns true if all its operands are true. In our case it will return true if the current back price of the selection we're betting on is less than 3.0, and it's been over 1 hour 15 min since the start of the match, and total matched amount for this selection is less than 10. In this case bet amount will be 100 - as the second parameter states. Otherwise, if at least one of the conditions does not come true, the bet amount will be 10.
The value 0.052083 is a representation of the time fraction "1 hour 15 min" in Excel.
See more details on date and time in Excel in this article.
Example 13. I have been using the following..
Cell: "Any Selection Back Price"
Condition: "is equal or less than"
Trigger Value: "1.25"
Action: "Lay"
Price: "8"
Amount: "100"
Market: "All Currently Monitored"
Selection: "Third Winner"
Active: "once and wait"
But around every 6/7 winning race for me my horse wins...so I would like to add an extra trigger to cut my losses..
I would like to say if that same horse that I have bet on gets to a back price of 4 I would like to Back 3.5 @175
is this possible??
Set up the following stop-loss trigger
Cell: "Triggers Worked Out"
Condition: "is equal to"
Trigger Value: "6"
Action: "back"
Price: "3.5"
Amount: "=IF(back_price<=4.0, 175, 0)"
Market: "All Currently Monitored"
Selection: "All Matching Selection"
Active: "once & wait"
This trigger will be executed as soon as the other trigger in row 6 has worked out. "All Matching Selections" in the Selection field indicates that it will be applied to the same selections as the first trigger. The Amount field contains an IF function that conditions your bet amount on the current back price of the selection. Only if it is equal or below 4.0 will the amount be 175. Otherwise it will be 0 and the trigger attempt will be considered unsuccessful and it will keep trying as many times as it is set in "Max attempts on failure" option on "Triggers Options" tab.
Example 14. I am looking for commands that trigger things off but do not make a bet just remember. 2 mins before start as long as winner is between 1.75 and 8 store the information of the winner (lowest horse). Then while in-play if this horse has a price leap to 16 again trigger off to the next stage but still do nothing. Then if that same horse goes back down again to 3 back £20 @2.
We'll obviously need three triggers here - one per each stage. You'll also need to crrect your "Allow triggering/offset no sooner than ... mins before the event's start" setting to "2" - to make it trigger no sooner than 2 minutes before the off.
Then set up the following triggers:
Trigger 1, in row 5
Cell: Winner Back Price
Condition: "is between"
Trigger Value: "1.75, 8.0"
Action: "react on price"
Price: "back_price"
Amount: doesn't matter
Market: select desired market or just "All Currently Monitored"
Selection: "Winner"
Active: "once idle & wait"
Just a quick note: this trigger will "remember" that the condition of the trigger was true and, depending on the value that "Price" column returns will either consider this trigger having worked out or not. The words "react on price" in the "Action" column indicate that the state of the trigger is conditioned not only by the "Condition" column, but also by the expression in the "Price" column. If it results to anything between 1.01 and 1000 it's considered valid. This is a trick we play to have another field for building our conditions - in cases when "Condition" plus "Trigger Value" are not enough. It actually doesn't have anything to do with "price" or odds - since no betting is made.
There is a more detailed explanation of "react on price" in the help file.
Trigger 2, row 6
Cell: "Triggers Worked Out"
Condition: "is equal to"
Trigger Value: "5"
Action: "react on price"
Price: "=IF(back_price>=16, 2, 0)"
Amount: doesn't matter, leave blank
Market: select the same market
Selection: "All Matching Selections"
Active: "once in-play & wait"
Another quick note: pay attention to the "Price" column now. If in the previous trigger we used "back_price" just to make it return valid value, this time we put in a condition. "IF" is an Excel function. It will return 2 if current back price of the selection is >=16, or zero - otherwise. Since we again have "react on price" in the "Action" column the second trigger will be considered "worked out" if - first - trigger in row 5 has worked out AND if the current back price is >=16.
The words "All Matching Selections" guarantee that the second trigger will "remember" the same selections as the first one did.
Trigger 3 - row doesn't matter
Cell: "Triggers Worked Out"
Condition: "is equal to"
Trigger Value: "6"
Action: "back"
Price: "2.0"
Amount: "=IF(back_price=3, 20, 0)"
Market: the same market
Selection: "All Matching Selections"
Active: "once in-play & wait"
Finally we got to the last trigger. It will watch the second trigger in row 6 and "IF" back price is 3, the amount will be 20 and the bet will be placed at 2.0. Otherwise - if "Max attempts on failure" in "Trigger Options" are set to "-1" - it will make endless attempts to check if the back price has become 3 - until the end of the event.
If you don't find some of the options described make sure that you have the latest version of MarketFeeder Pro. Here you can find the latest news about MF Pro builds.
Example 15. A back bet of 10 Euro should be placed on the winner at the best price if all of the following (sample) conditions are met:
1.) Minimum of total matched bets of event must be Euro 400 000
2.) Event must be "in-running" for a minimum of 30 seconds
3.) back odds of lowest priced runner must be less than 1.6
4.) lay odds of lowest priced runner must less than 2.4
5.) back odds of second lowest priced runner must be greater than 7
6.) lay odds of second lowest priced runner must be greater 12
7.) back/lay ratio of lowest priced runner must be greater than 4
8.) Unmatched lay volume of lowest priced runner is greater than Euro 4000.
First, you must check "Retrieve all price offers" setting in the main interface of the application. This will substantially slow down the refreshing because each runner will require a separate request sent to BetFair for the whole list of price offers made for it. But this is necessary because among the conditions you listed "Unmatched lay volume of lowest priced runner". If you don't check this setting the volume will be gathered within the price range than is 2 ticks lower than the best back price and 2 ticks higher than the best lay price.
Next, we will combine some conditions into one trigger, grouping them by the selection they're applied to.
Trigger 1, row 5
Cell: "Any Selection Back/Lay Ratio"
Condition: "is greater than"
Trigger Value: "4.0"
Action: "react on price"
Price: "=IF(AND(market_volume>400000, lay_volume>4000, back_price<1.6, lay_price<2.4), 2, 0)"
Amount: doesn't matter, leave blank
Market: select market from the drop-down list
Selection: All Matching Selections
Active: once each in-play market
Trigger 2, row 6
Cell: "Triggers Worked Out"
Condition: "is equal to"
Trigger Value: "5"
Action: "react on price"
Price: "=IF(AND(back_price>7, lay_price>12), 2, 0)"
Amount: doesn't matter, leave blank
Market: the same as in trigger 1
Selection: Second Winner
Active: once each in-play market
Trigger 3, row doesn't matter
Cell: "Triggers Worked Out"
Condition: "is equal to"
Trigger Value: "6"
Action: "back"
Price: "best"
Amount: "=IF(NOW()-event_start>0.000694, 10, 0)"
Market: the same as in triggers 1 and 2
Selection: Winner
Active: once each in-play market
Let's comment on these triggers. The first trigger is designed to cover several conditions at once: conditions 1, 3, 4, 7 and 8. As a main condition we set the "Cell" to "Any Selection Back/Lay Ratio". The "Action" is set to "react on price" which guarantees that this trigger will calculate the "Price" column - and if it is something above 1.0, the trigger will be considered as "worked out". Thus we put conditions 1, 3, 4 and 8 into that "Price" column using Excel functions and pre-defined trigger variables. Trigger variables are listed in the application's help file, they are calculated by MarketFeeder Pro "on the fly" - that is each time a market is refreshed the fields containing variables are re-calculated. The values of these variables are computed for every selection that is specified in "Selection" field. In our case we have "All Matching Selections" there which means: all selections that meet conditions described in "Cell", "Condition" and "Trigger Value" columns. Strictly speaking there may be several selections with back/lay ratio over 4. But due to the fact that we have other conditions in "Price" column, we eliminate the possibility of meeting any other selection except the winner that will match all of these conditions at once.
The meaning of the first trigger is simply to "remember" than some of the conditions from our list were met. If that happens we can proceed to the next two triggers.
Trigger 2 will work out only if trigger 1 did. It will check two conditions related to the second winner. Again, we're doing it by using "react on price" and pre-defined variables back_price and lay_price. Only this time they will be calculated for the second winner. Again, the state of this trigger will be "remembered".
And only if the first two triggers have worked out, the third one will snap into action. As its parameters indicate it will back 10 @ best price on a winner, but only in case it's been more than 1 minute since the scheduled start of the event. We used 1 minute except 30 sec because events often don't start at announced time and it is impossible to determine when exactly it'll happen. So this parameter is in question and you need to adjust it eventually.
The field "Active" is set to "once each in-play market" which confirms that all the conditions will be monitored only when the market is in-play.
