User Comments

Checking results:

https://youtu.be/RYxd64S1B2s

Fake scores from betfair live score provider is really big problem. I asked betfair about that, here is their reply:

https://forum.developer.betfair.com/forum/developer-program/general-betting/26180-var-rules

As you can see from my video:

https://www.youtube.com/watch?v=8csHYSPyUM8

In the Bundesliga match: FC Bayern Munich - SC Freiburg, there was no VAR decision:

https://fcbayern.com/en/matches/profis/bundesliga/2018-2019/fc-bayern-muenchen-sc-freiburg-03-11-2018-liveticker#content-navi

On the official Bayern web page there is live score provided by sportsdata, and no fake score was reported by sportsdata.

I think there is “insider trading” on fake scores to be blamed. This is not first occurrence on fake score on Sunday matches.

Automated trading is any algorithm choosing your bet selection automatically. In this strategy a bet selection is driven by goal scored event in a football match, so it can be called automated trading strategy.

Yes, you can run automated strategies using bfexplorer in 24/7 mode.

This strategy is good example to introduce bots for bettors, or to those whose place bets manually as it is simple, but can be executed with different parameters, for instance no placing bet on correct score market, or starting placing bets only from set match time when goal is scored.

The trigger bot code can be updated to not place bets but instead just notifies you about goal scoring, so bot would automatically display match and selection/team which scored goal, then you can make your bet decisions manually. Have a look at how that works in in-play horse racing strategy: Watch Favourite bot.

As said before this strategy profitability or risk affinity depends on number of scored goals, and time when last goal is scored. Biggest profit is made on 0 – 0 match results, biggest loss for more goals (3 and more, when score goes from one team to other and/or draw) and not match bet after goal scored in last minute.

Top leagues matches starts on Friday, but will leave running some matches with bigger liquidity through this week as well.

Maybe the VAR is used, but in such case the market should be suspended till VAR decides.

Today I made my own bot and found some time for testing.

Again I noticed one false score on SPAL – Frosinone match, at 32 minute of the match it was reported 0 – 1, then later in next minute the score was fixed to the right one: 0 – 0. When checking another source of score data, in 34 minute of the match was awarded yellow card only. I do not know whether betfair has problem with their feed or just provider of football live data plays with us its own strategy, as again prices reacted to that false score, betfair suspended and reopened the market, and new prices formed.

Here are some videos:

Back Goal Strategy Test 1

Back Goal Strategy Test 2

Back Goal Strategy Test 3

So I tested this strategy on 7 markets with total profit 24.72 Euro, but as I mentioned before to win just 25 Euro in total on some matches my liability reached 192 Euro to win 4 Euro.

I will run blindly this strategy in following days on each match from top of European leagues to see what could be won or lost.

It is a better idea to run this strategy on selected matches using either manual selection or automation by match statistics similar to this bot: Football Trigger Bots

Today I tested this strategy on eight matches so here are my thoughts.

It seems to be a good strategy for automatic/bot football trading.

As mentioned in my post I changed the bot trigger code to place payout bets when goal is scored by team adding correct score 0 – 0 bet liability and previous liability on match odds selection to goal bet.

I did not change the bot trigger code, I left it as a simple coding task for anyone who would like to test this strategy as well.

It is a good idea as well to set “Place Bet” bot parameter MaximumOddsDifference as not in all cases market odds stabilized after goal is scored, so without this parameter setting (I set it to 3) your bet could be matched on unfair odds/price.

If you read the strategy specification, in each step it is repeated: … back with greening … what is from my point of view nonsense as if you would like to green up your position your bet stake amount would go quite high after couple unsuccessful back bets placed.

I used “Close Market Bet Position” bot, so your bet position is closed on all selections you place your bets on. In my test I used 2 Euro for correct score 0 – 0, and 2 Euro payout for “Back Goal” bot, 3 Euro profit for “Close Market Bet Position” bot.

When you think about this strategy then in case when no goal is scored your 0 – 0 back bet could be closed to required profit as well, unfortunately none of my tested matches went to 0 – 0, so I missed to test such scenario.

What could go wrong with this trading strategy?

Back bet liability of placed match bets when score goes from leading goal to draw and back (through many score changes) could reach dangerous amount. In my test maximal reached liability of placed bets was only 42 Euro.

This trading strategy requires relevant score data, as a matter of fact, betfair score data are stable, but yesterday when testing the code wrong score appeared on one match played in Serbia, wrong score 0 – 1 appeared for couple minutes, even betfair odds reflected that goal had been scored, but after a while right score 0 – 0 appeared again, so “bot trigger” fired again back bet.

Late goals at the end of the match, without chance to get matched placed bets, or reaching dangerous liability of placed bets. For such scenarios the strategy requires to close bet position at 85 minute. In my test I programmed the “bot trigger” code to close “bot trigger” execution, at 85 minute of match time, so no “Back Goal” bets are placed.

“Close Market Bet Position” bot had not been setup to close bet position at loss. This feature requires to run more tests, it should be found optimum time at what the bot trigger stops its execution, so any bet position is closed at that time, at profit or loss. This trading feature should be executed not only by match time but also by match score. It is safer to close bet position when just one scored goal could change our bet position.

In my test for 5 from 8 matches, had been closed bet position (greened up) in reached profit. In some matches, even when match score suggested, that we are in 90% profit position, for instance match  Sheff Utd – Wigan, the bot greened up our bet position at 80 minute when scored was 4 – 2 for Sheff Utd.

The question is, what is better for entire profitability of this strategy, to leave running our bet position at some match point, or better to close bet position for profit or loss?

Here is link to my video from today’s test:

Testing Wave Strategy Bot Trigger

Lupuente has Spanish version of Windows 10 installed on his computer. The script code is compiled by bfexplorer to dll assembly, so bfexplorer can executed such bot assembly.

In Lupuente case during compilation compiler returns error message:

Mscorlib.dll missing or not found, but the assembly is actually on his computer, in the folder:

C:\Windows\Microsoft.NET\Framework64\v4.0.30319

During teamviewer session I did not manage to find problem on his computer, so I solved it by compiling the script to assembly. To compile script assembly on your computer you need either Visual Studio (Community) or Microsoft Code with installed support for F#.

On the forum you can find many posts showing how to program and compile bot assembly.

You need to download script to your computer, and ensure that it is in format you can see on github page:

https://gist.github.com/StefanBelo/e49bdc9fdd60c580a212b688190dd33c

It is code and bfexplorer compiles it executable assembly, so there must right code without code errors or wrong text formatting.

Have a look at here, on this post where you can see, what IDE you can use to write or update bot trigger script, and be sure that all is ok:

Betfair Bot Programming for Non-Developers

There are quite a lot of examples of using bot trigger script, for instance here in this post: Double or Bust - Betfair Trading Bot for Horse Racing

You can see (from 15 seconds of the video), how bot trigger is setup with bot: “Execute Trigger Bot”.

Download bot trigger script to you computer, and repeat bot setup seeing in this video.

Keep in mind that it wise to test any script in practice mode, as bot script really just place bets without any strategy, just hoping that bets will be matched making zero risk profit per selection, which is hedged at set time.

You need to test it on more races to estimate your Profit/Loss percentage, or just try to introduce parameters which could work for you better. It is more an introduction to bot trigger programming than presentation of 100% profitable strategy.

Betfair historic data are in json format, so you must know how to process them. I do not know what betfair has been thinking when releasing data in that format as most people are not programmers.

What does it mean for you?

As many others like you who may bought that data, after opening them have no fuck idea what they just bought from betfair, so such people end on freelancer web sites hiring someone to export from those data what they want.

So my hint for you google for instance:

"betfair data json" site:www.freelancer.com

And from that web site, when data are still available you can download some PRO data for free, of course you must be registered on web site to download data.

Keep in mind that to your valid betfair api activation there are three services, so three different types of problems could occur. You can check your subscription status by login on bfexplorer web site and clicking on menu item User / My Subscription Details.

My authorization service registers your details only, activation of betfair api access to your betfair account is done on betfairs servers, and in some cases this procedure could take more time, that is the way how betfair does this procedure.

When first attempt to activate your betfair api access fails, white for a while and repeat login procedure again. In this process there could be two problems: your new subscription code is not generated from betfair servers, or your generated subscription code is not activated on betfair servers.

Yes, from the nature of betfair api activation there could be a short time when your betfair api activation is not activated, mainly when you use bfexplorer in fully automatic mode, as the activation process requires re-login procedure, so closing bfexplorer and login again. If you use bfexplorer this way them better solution for you is to buy 1 year subscription, but again when subscription expires you need to re-login, that is actually betfair requirements to activate betfair api.

For common users there are no such problems as he/she runs bfexplorer on daily bases, so reactivation of api access is no problem, as times of login differs.

In-play horse racing markets are very volatile. I made short video showing situation on such in-play horse racing win market, you can see that in many cases back book value goes from 101 up to 135% what means there is big gap between best offered back/lay prices.

On in-play markets there is applied bet placement delay (1 second for horse racing markets), therefore placed bet calculated at current best offer price can be unmatched, when it appears on the market after bet placement delay expires. Close selection bet position offers the parameter: BetMatchingTimeout, so when you bet is not fully matched bot waits for set bet matching timeout, so for chance the unmatched bet be matched, and when bet is not fully matched it is cancelled and bot tries again to close your bet position at set parameters.

Keep in mind that betfair applies so called best execution rule when bet is placed, it means when there is better bet price then price you asked for in your offer, your bet is matched at this better price. This rule can introduced some problems when closing your bet position, or when hedging, as the hedging bet stake is calculated to exact priced.

When this best execution rule is applied your bet position is not equally hedged, therefore is such in-play scenarios is a good idea to use “Close Market Bet Position”, this bot closes bet position on all selections where is possible to close bet position, and checks if position evenly closed, if not bot tries again to close bet position trying to level profit/loss on all applicable selections.

This bot (“Close Market Bet Position”) offers the parameter: ClosePositionAtTime, when set to unrealist value, for instance to -1.00:00:00 (minus one day), bot immediately closes bet position on market, not checking whether Profit/Loss were reached.

In your trading scenario is better to use trading bot: “Place Bet and Close Selection Bet Position” setting the parameter: CloseBetPosition/ClosePositionImmediately what means that after your opening bet is fully matched bet to close your trading position in Profit is calculated and immediately placed on market offering it.

If you want to execute your strategy with two bots: “Place Bet” and “Close Selection Bet Position” then first evaluate all offered parameters to get the best execution of your bot, switch off parameter: CheckingLastPriceTraded, try different values for BetMatchingTimeout, OfferMyBet.

You can program your own Close Bet Position bot of course, for instance checking gap between bets offered back/lay prices, you can place your bet in the middle of the offered prices, or just calculating latest price trend you can place your bet at most probable matched price.

The last possibility is to change your trading strategy to place dutch bets on potential winners.

I would suggest to rephrase “… uncontrolled bet placement …”, as bot place bet/s the way you instruct to place them.

So you want to say that you do not understand how bets are placed by your bots?

I have just added "Limit Action Bot Execution" bot to bfexplorer, install the latest version of bfexplorer and setup this bot to execute your action bot.

Keep in mind that bot limits number of executed action bots not number of bets, as depending on your action bot settings, such action bot can place more than one bet, mainly when bot is allowed to place bet in odds range, or when you use bots like: "Be The First In Queue".

In such cases you should revise market refresh rate setting, ChaseOddsTimeout, BetMatchingTimeout and similar bot parameters of bfexplorer bots.

If you place your bets by bots, then yes I can create a bot that executes action bots (bots placing bets) and records number of such action bots execution per hour, so limiting further bet placement if set limit per hour is reached.

IntelliSense in action:

Mike, this is not a joke, but I wanted to start with something you, and I believe everyone working with computer knows.

So in text editor app, the spellchecker checks your grammar underlying misspelled or wrong words by red line. If there are more options to correct wrong word a list of options is presented.

It is the same when you write code in IDE, any wrong construction of your code is underlined by red line, and error icon with possible solutions is presented. In IDE it is called Intelisense, and option to present properties or methods available for object types your code interacts with.

In trigger code, you can interact only with objects offered by bfexplorer app when trigger is instantiated, so that is your world of objects the intelisense offers properties and methods to you, so there is no need to make a list of offered objects your trigger can interact with, you already have this option in your IDE (Visual Studio, Visual Code, Atom, or whatever you use).

That is answer to your last question! Do we understand each other?

Watch video in my article: Betfair Bot Programming for Non-Developers

Where you can see what I am talking about, intelisense support, method description, for instance when hovering over code, or functions descriptions, like for Execute method there is description: unit -> TriggerResult, so you know that function takes no arguments (unit) and returns TriggerResult

What is TriggerResult and what options it offers is again offered to you by intelisense, when typing TriggerResult following . intelisense offers you list of all options you can use.

So basically any written code is checked against any error, and options are offered like spellchecker offers you correcting your bad spelling.

Keep in mind that using bfexplorer you agreed with T&C and I suggest to read it again if you did not do so.

Mir, back to the point, as I said in my first reply you have no subscription for bfexplorer, so your posts here are just spam. I did not want to delete your article as it could have some value for bfexplorer subscribers as well, so I replied with relevant answers.

I just want you to understand one thing. People mostly read just titles, so ones could have such impression that using bfexplorer app could lead to restricting or closing betfair account because of misusing betfair api data.  

You used another betfair app, and betfair restricted your api access, but you did not mentioned that.

Where you mentioned not so true arguments, I replied with my opinion, and I know something about it as myself programming for betfair users from 2007.

Last hint: ask betfair for software vendor license, then you can use betfair api as you want to. From my position I monitored data, or tested bespoke bots for days without placing a bet, and have never been restricted in betfair api usage, but that of course makes sense.

Mir, your problem is that you do not understand what you read about your software in a manual. In market feeder manual it is said that you can globally set two values for market refresh rate: idle refresh rate and in-play refresh rate (page 175). You can change trigger value evaluation interval in your triggers, but that does not change market refresh rate we talk about.

Just common sense, if you want at the moment, to monitor all football matches for 2 days (match odds markets) with more than 500 Euro traded, then you can open 177 markets now.

If you would like to really monitor each of them at different refresh rate (as you mentioned) then it would mean to call market data refresh for each market so 177 calls at different time intervals, that is of course nonsense.

Using rest api I can refresh up to 25-50 markets per one api call, or using streaming api I can just open stream for all 177 markets changes and get at set refresh rate only updated values from betfair servers.

Market feeder maps market data values to mapped variables, so in your triggers you can use such variables in condition formulas, and when evaluated conditions are met it is triggered preprogrammed action, mostly bet placing, or bet cancelling. You construct evaluation formulas, not parts of code, bots which could be executed and add new features to market feeder app. You cannot add new features to market feeder app, only evaluate values which are offered.

Bfexplorer app approach is different, as what we call a bot is real part of execution code which adds new features to bfexplorer app.

For instance in this article: Betfair Tennis Trading Automation, in my tennis bot code I implemented loading and evaluating match results and statistic, tipster selections, and common user votes on who will win the match from 3 different web sites.

Yes, it is a code, a program executing specific operation, so in this context I could use it only in bfexplorer for the specific purpose, but the code implementation allows me to reuse data provider assemblies in different apps when I would like to use it.

You cannot do that in betfair apps where automation is done just by evaluation of mapped values in trigger or in excel cell formula.

Mike, shortly to your last question, do you know what spellchecker is?