Community Articles
- Popular
- Recent
- Comments
-
Hello. Since yesterday I have a delayed API on my BF Explorer trading software. I had no bots running when this happened and now I am also unable to trade as all stakes in the markets keep flashing all over the ladders on random odds, being absolutely impossible to figure out what was the last price ...
9.5.2020 16:19:41 -
I tried BFexplorer, having used 3-4 different software applications beforehand. The 2 days utilising the software, I managed to get a feel for the product and like the modern display on the black background. Bets placed were very responsive with no lagging experienced from other products. A few ...
25.3.2015 17:55:00 -
Version 3.22.0821 Cumulative updates to the Bfexplorer Preview version Version 3.10.0721 Cumulative updates to the Bfexplorer Preview version (.net 8.0) Version 3.9.0425 Cumulative updates to the Bfexplorer Preview version Version 3.1.1021 - preview Betfair menu ...
22.8.2024 14:37:12
-
Overfitting: The art of avoiding overfitting and the importance of comparing training and test results to detect it. ROI Calculation: Different methods of calculating ROI, including the impact of flat stakes versus stakes based on odds. Feature Selection: Emphasize the importance of ...
21.11.2024 8:41:42 -
All about Luck and Success betting
The Role of Luck Unpredictability: Betting inherently involves a degree of unpredictability. No matter how much analysis you do, there are always elements beyond your control, such as unexpected injuries or weather changes. Short-Term Variance: In the short term, luck can significantly influence ...
10.9.2024 13:27:05 -
Some insights into different betting strategies, including trading in and out versus betting based on fundamental probabilities. Trading In and Out: This strategy involves placing bets and then trading out of them to lock in profits or minimize losses. It’s similar to stock trading, where ...
10.9.2024 13:24:03
- by : Betfair Bot
- by : adska
- by : adska
- by : adska
- by : adska
- by : Betfair Bot
Lacoste
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.
Lacoste
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!
Lacoste
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).
Lacoste
Nice. I'll try to set up my bots using existing parameters/criteria and come back to say how it went.
Lacoste
“Anytime this number changes it is either a newer player break, or re-break, right?” Yes.
Everytime first page conditions are applied, a break occurs, but only if this break happens as both players are on serve (there’s no advantage/disadvantage in breaks).
Let’s say the score goes: 1-0 (P1 hold), 1-1 (P2 hold), 2-1 (P1 hold), 3-1 (P1 break) - this break is registered by 1st page conditions - 4-1 (P1 hold), 4-2 (P2 hold), 4-3 (P2 break) - this break is registered by 2nd page conditions and now conditions are reset - 5-3 (P1 break) - again this break is registered by 1st page conditions - 5-4 (P2 break) - again this break is registered by 2nd page conditions - and so on…
Another situation: 1-0 (P1 hold), 2-0 (P1 break) - 1st page conditions - 3-0 (P1 hold), 4-0 (P1 break) - this break is registered by 2nd page conditions - from now on if P1 breaks again will not be registered by my conditions, but if P2 breaks before P1 gets another break then page 2 conditions are waiting for another break that will be registered.
Page 2 conditions are applied when there is a re-break or the player gets the second break advantage. If there’s a difference bigger than one break beetween players, it won’t be triggered.
Maybe if you put parameters like PointsScore, PlayerServing and criteria to set up difference beetween GamesScore (based on players) or Player1SetScore / Player2SetScore / Player1GameScore / Player2GameScore / Player1Serving etc. and conditional criteria.
I’m thinking this to be used by other traders.
link
Lacoste
Stefan, consider this!
I think these conditions identify what I need, but not all break situations. It seems head-spinning to create all situations only based on game score.
It shows first break scored in a set and the second break - taking into account who broke first.
Lacoste
Also, having the option to reverse the book will be very helpful.
Suggestion: Put a friendly voice in your videos explaining the software.
Godspeed!