Comments

The source code to all bot triggers can be found here:

https://github.com/StefanBelo/BetfairBotSDK

Soon I will add ExecuteAtPricePercentagesBotTrigger.fs.

From betfair forum:

Originally Posted by JayBee

JAYBEE, you are wrong.

Bfexplorer BOT SDK is free and everything what user needs is to post on bfexplorer forum, and there is for it just one rational reason. Betfair api access is activated automatically each month by my authorization system on my web site, to active betfair api access, or better to say to generate betfair subscription code, and this is done only for those who posted articles, or comments. I do not have to do it manually, it is done automatically also for those who use free version of bfexplorer, not only for BOT SDK users.

Using Bfexplorer BOT SDK, anyone can choose what he will use, and there are 4 different levels of using Bfexplorer BOT SDK code and/or assemblies/services.

Bfexplorer app is just environment for loading markets, bots execution, and evaluation of results, and so on. If betfair programmer chooses to use BOT SDK and create bots which will be integrated to bfexplorer app (those are just projects MyCsharpBot or MyFsharpBot and MyBotTriggers), then is obvious he needs to execute them with bfexplorer.

On the other hand he can use those 2 levels of programming with api only, and bfexplorer app domain, and in this case he will build his own app on those libraries, and it is really up to him, if he builds some user interface for his app, or will run it like console app or as a service, or as a web application on asp.net platform.

For those who would require my support with bot development and will use bfexplorer app, there are 2 subscription plans. Either he decides to post on bfexplorer forum, or not, then of course he will subscribe, but his subscription fee can be just zero 0 GBP, 2.5 or 15 when posting on bfexplorer forum, or when donating amount between 2.5 to 15.

If he does not want to post anything to forum, then of course he will subscribe with Professional or Basic subscription plan.

I fully understand your opinion because no one will need to read your book, all what you describe in your book is already done.

Please leave on betfairians what and how will be used. Those who want to build betfair apps from scratch and cannot read betfair documentation to betfair api will certainly buy your book.

Those who want to skip this part, and actually develop only bot strategies or trading models can use my BOT SDK, or any other publicly available assemblies. On this forum I think can be found at least 3 or 5 such betfair libraries, mine is just one of them.

Thanks for replies. I had no idea what term backbook/laybook meant I thought it relates just to prices on the back/lay side. So thank you for explanation. I use fill kill bot instead of place bet bot because I want only place bet after finishing the first set and before any point of the second set is played. In the place bet bot when I set the range of odds I would like my bet to be matched the bot will be waiting until these odds are met but it could mean that some points have already been played in the second set. Anyway thanks again I will test last traded price criteria. Cheers

“Close Selection Bet Position At Odds” places a bet at current offered odds when you set the Odds parameter to 0, so this bot actually does not check your target odds in such case.

Similar to Place Bet ... bots Min/Max odds difference feature, this bot offers the parameter CheckingLastPriceTraded (by default set to true, so this feature is active) and with the parameter CheckingLastPriceTradedDifference to place your bet only when odds difference between last price traded and current offered odds is <= CheckingLastPriceTradedDifference, so it waits till selection prices settles, as when odds rapidly changes mostly it is because offered bets are cancelled.

You can use the parameter BetMatchingTimeout to set the time the bot will wait for your bet to be matched.

You are not right, when price/odds changes the bot cancels your bet and a new bet is calculated for new price/odds, so stake cannot be the same. I think you did not realize that on any bet placed on betfair is applied best execution rule, your bet is matched at better odds if such odds is offered at the moment your bet is processed by betfair matching algorithm, therefore correctly hedged bet size will result in not balanced bet position.

The bot does not start because your entry criteria is faulty.

LayBook (and BackBook) refers to book percentage. This tells you in percentage terms what all the decimal prices for each runner add up to. You can find this in Bfexplorer just under market time.

Your corect criteria would then be LastPriceTraded Is less than or equal to 1.5. Or you can set PlaceBetInAllowedOddsRange to True and MinimumOdds to 1.01 and MaximumOdds to 1.5.

Why are you using Fill or Kill bot, are you familiar with term book value, and what does it mean?

Install the latset version of bfexplorer I changed live score update routine when more Tennis Bots is executed on one market.

You do not have to set IsInPlay Entry Criteria, the bot itself, waits till market is turned at in-play and then starts updating live score data.

Yup. You're right.

"[...]as two bots retrieve the same score data, only first one receives notification about score data changes[...]". Executed the tennis bots without the action bot.

When I execute as I previously said, none of them trigger. My issue still stands.

Thanks!

Your bots should be executed and working, but as two bots retrieve the same score data, only first one receives notification about score data changes. You can test it by executing two tennis bots (without action bot setting) on the same market. You will see that only one line of score is displayed in Output view.

Confirm that you understand this issue, because as you said “I can't execute both of them at the same time in the same market”, you actually can do, but triggering is taken by first executed bot only.

I will investigate this issue, and release update soon.

The only Entry Criteria I have set up is IsInPlay Equals True.

The thing is I can't execute both of them at the same time in the same market. If I execute only one of them the bot goes through. It works. It fails to work concurrently.

The parameters are simple: Lay at odds given with stake given when InPlay if Player, Score, PlayerServing conditions are met and EvaluateOnlyOnce.

I thought first that score conditions in these bots are conflicting, but after checking, they are not (as you can see).

Yes, you can insert images to your article as well, but you have to use direct link to the image, not web page link.

What is Entry Criteria setting, do you understand that if Entry Criteria are not met and you set EvaluateEntryCriteriaOnlyOnce then bot stops its execution after the entry criteria are not met.

 Why do you ask?

Here are some questions:

Can you place a bet when a market is suspended or closed?

Is your bot (bfexplorer bot) executed when a market is suspended or closed?

 I'm testing an Excel spreadsheet and I have the following observations:

1. Both matches ended up - is a mismatch in the tabulation of results on the sheet.

2. At the same time, the Excel spreadsheet presented other data.

Watch my video.

Stefan:  Let me know when you're done working on this project.

Thanks, I have no further questions...

Actually all Entry Criteria are sharable properties of the market or the market selection/s, and running bots with its activity influence all those values. Your question just shows that you do not understand what you asked.

Stefan, thank you very much for explanation!

-----------------------------------------

And what about "Entry Criteria"?
Is it possible that ongoing results of concurrent running bots can influence the activities of each other? (means through ProfitBalance, SelectionProfitBalance, HaveMatchedBets)

Miro, this is actually quite funny because if I remember it correctly I added “Concurrent Execution” bot by your request when you tried to build some trading strategy.

The main difference between those two bots is the “Execute Bots” bot just starts bots execution and then stops.

The “Concurrent Execution” bot starts bots execution in its own execution pool, so your action bots are hidden, in the “Market Bots” view you can see running only your “Concurrent Execution” bot.

That is one advantage, hiding action bots execution, so by canceling one bot, you can execution of all actions bots.

Let’s say you want to create a spoofing bot, placing bets 2, 3, 4, 6 ticks from the best offered price. To construct such bot you would need to create four “Place Bet” bots, allowing place a bet in odds range and setting the PriceImprovement parameter.

It is obvious that you would like spoof on back, and sometimes on lay side, but you do not need to create four versions for backing and four versions for laying. You will use bots execution from clicking on ladder feature, so you can name your “Place Bet” bot settings with general names, like “Place 2 ticks from”

Finally you add bots to “Execute Bots” or “Concurrent Execution” bot parameter: BotNames, and name your spoofing bot, job done.

Activating “User Ladder” and selecting your spoofing bot in “Bots to Execute” view, you can now execute your bot by clicking on ladder. Bot will take bet type, stake and odds as the maximal lay odds your bot will operate to, and opposite for back side.

“Concurrent Execution” bot has internally implemented two features:

If any of internally running bots will end, all the rest of bots is forced to end their execution as well.

When bots are created for execution, only the first bot will take parameters from a click on ladder. Unfortunately this feature limits for now using the “Concurrent Execution” bot in scenarios similar to spoofing bot example I described above.

I can remove this feature, what I have done in my tests, or can make it adjustable.