Important change in version 6.0.0.22 BetFair betting bot - MarketFeeder Pro - triggered automated betting software
After a fortnight's holiday break we are resuming our blog.
An update was made today, which fixed an improved a couple of things, and also administered an important change in the way the trigger's action "set user variable" is executed.
The "set user variable" trigger used to create and/or assign a value to a variable with the specified name. It value did not depend on what you would put in the "Selections" field of the trigger. So the result would always be the same, no matter whether you choose "All Selections", "Favourite", "Second Favourite" etc. as the "Selections".
Now the need to expand this action's usage made us change the way it works. Now it will be executed as many times, as the number of qualifying selections for the trigger. So for example, if you choose "All Selections", the user variable will be changed as many times as the number of runners in the market.
Here is an illustrated example.
Can you guess what the value of the "ab" variable will be after the trigger named "changing variable" is executed? Here is the hint:
The trigger has added all runners' chances for winning (100 divided by their price) and "ab" is now equal to the back book percentage.
In the previous versions its value would have been 100/3.95 = 25.32, regardless of what was in the "Selections" field.
This change will affect triggers that add or deduct something from the existing value of a user variable. For example, in staking plans, when the value of the current loss is calculated based on what it was in the previous market. Therefore it is very important that you review your triggers and make appropriate changes. If a variable needs to be changed only once per market, then set "Selections" to "Favourite", or any other option that implies only one selection.
We have updated trigger examples accordingly, where needed.
What benefits does the new change introduce?
The new behaviour of the trigger action makes it possible to apply some simple statistical functions to selections and their parameters. We will try to suggest several examples later in our blog, but here is the simplest one.
How to calculate the maximum profit/loss of all selections in the market.
Right-click here to download the trigger file.
The example consists of two triggers, each being repeated with an interval of 10 sec. The first trigger resets the initial value that all selections' P/L figures will be compared with. This number should be a big negative figure, so that in case all P/Ls are negative, the maximum of them will still be found. Here it is set to -1000, assuming that the maximum P/L will not be less than -1000 (Lord save you from such P/Ls!).
Now to test the triggers, start refreshing a market and placing back bets on different selections, randomly if you choose. Open the "View Variables" window and watch how the value of "maxpl" changes. Naturally, this variable can then be used in other triggers as well.
So, double-check your triggers now: wherever you'll meet a trigger with the action "set user variable", to be on the safe side change "Selections" to "Favourite", unless you want to explore the new opportunities this action provides.
More examples will follow in a short time.
If you have questions / suggestions, do not hesitate to leave your comment here.
