Comments

  • PleBeY
    26.3.2019 17:43:00

    Hello!
    I'm trying to run a script  TennisBreakPointAlertBot.fsx
    and this problem appeared, below was a description of how to solve it, but it turned out to be difficult for me, English is not my native language.
    Is it possible to help me?)

  • Stefan
    26.3.2019 15:25:12

    mscorlib.dll is part of .net installation package, and is installed on every Windows OS, .net is here from 2002, so my question is what you do and on what OS?

    http://dllsearch.net/dlls/m/mscorlib-dll-file

  • Stefan
    26.2.2019 18:17:03

    More about TLS 1.2 for software developers:

    https://blogs.perficient.com/2016/04/28/tsl-1-2-and-net-support/

     

  • Stefan
    26.2.2019 18:12:16

    I do not know on what version of .net is built Geektoy, but for instance cymatic is built on .net 4.5, and also does not support windows xp and 7.

    http://www.cymatic.co.uk/forum/topic1680.html

    By general TLS 1.2 is supported by .net 4.6 and above so all apps built on such .net version does not require any changes, but of course TLS 1.2 must be directly supported by OS, so it must be its default protocol for https.

    Other versions of .net require:

    ServicePointManager.SecurityProtocol = SecurityProtocolType.Tls12

    Because bfexplorer app is always built against the latest version of .net, I did not have to rebuild my app to comply TLS 1.2 requirements, but on the other hand users must use latest updates for OS.

    Once again keep in mind what I said before: “I use bfexplorer app daily, so you can be sure there is no problem in bfexplorer app.”, so any problem you have got are in 99% cases on your side.

    Similar problems reported at the same day one user from Asia, he told me that app worked day before but not 19 February, I replied similarly like in your case.  Later after 1-2 days he reported that all works fine on another computer?!

    So now think a little bit, he used the same app, one was not working and the other was working but on another computer, of course he did not bother to report on what OS he runs bfexplorer that have problems to connect, again I replied by more details about TLS 1.2 as I was sure that it is his problem. He did not reply on what OS he runs bfexporer but again complain, actually just copy pasting original email.

    Finally he managed to execute TeamViewer   session, and what do you think what OS he was running, well yes Windows XP.

    Keep in mind that when using OS which is no more supported by Microsoft you did not get anymore any security patches, there is 100% chance your computer is full of viruses and all kinds of malware.

  • Corneliu
    26.2.2019 17:39:39

    I got it ! I managed to update TLS 1.2 on my computer. Just can't understand why this problem only happened wit BFExplorer, as with Geeks Toy always worked fine all the time. Thanks for all your help !   

  • Stefan
    26.2.2019 16:15:05

    What is your OS version? Send me TeamViewer access (by support email) code so I can check it myself.

    I tested bfexplorer on Windows 10 and Windows Server 2012 and all works fine. I can confirm that bfexporer will not work on Windows 7 or XP, as bfexplorer app is compiled to .net 4.7 version without support for Windows 7 or XP.

    If you want to run app with TLS 1.2 on Windows 7 or XP them it is just not a question of installing the latest version of .net assemblies, just google: tls 1.2 on windows 7.

  • Corneliu
    26.2.2019 14:09:50

    It's not the OS because Geeks Toy works fine, I have updated the OS and still cannot log in BFExplorer. Why I paid yesterday and it still says in your website that my subscription expired on 23 FEB ?

  • Stefan
    26.2.2019 9:25:54

    There was planned maintenance-Tuesday 26th February & Wednesday 27th February 07:00 - 07:15 GMT on betfair servers.

    From 19th February 2019 betfair servers accept only TLS 1.2 secure protocol.

    Whenever any problem occurs with connection to betfair servers, first what you should do is click on menu item: Help / Betfair Exchange Api Status, it opens the following web page:

    https://status.developer.betfair.com/

    And so here you can check whether all betfair services work without problems.

    If you problem is with TLS 1.2, then simply update to the latest version of windows operating system.

    I use bfexplorer app daily, so you can be sure there is no problem in bfexplorer app.

  • Corneliu
    26.2.2019 1:10:08

    Also, I have subscribed (again) today, paid the subscription, but in your website it still says it expired on the 23red of February. :(

  • Stefan
    4.2.2019 21:08:50

    First you need to setup your action bots, Place Bet bots, to place your bet on exact market selections, so 4 action bots, simply you need to declare what bets and on what market selections you want toplace your bets automatically.

    You need to create 4 Football bot settings, setting your Start or Stop Criteria, MarketName and BotName (your action bot).

    You can use Clone bot (click on popup menu item for Add a new bot), and change your MarketName and BotName for rest of Football Bots, if your Start or Stop Criteria are the same for all your football bots.

    And finally you can use “Execute Bots” bot to create your strategy bot executor, adding all 4 football bots to BotNames. This way you have got one bot you can execute with Bot Executor.

    Yes, as your strategy requires to place bets/execute action bots on three additional associated markets: Correct score, Over/Under 2.5 Goals, Over/Under 1.5 Goals the Bot Executor will open these markets for when Start Criteria are met, but all bfexplorer bots have the parameter: StopMarketMonitoring.

    When you set StopMarketMonitoring parameter to True (checked) then when bot finishes its execution, and no other bot is running on the market, the market monitoring is stopped for such market.

    Bot Executor does so automatically as well, even when you did not set the parameter StopMarketMonitoring, simply bot executor will check whether there is still some bot activate on the market, and when no bot is active/running, the Bot Executor stops market monitoring.

    You say that on Correct Score market you want to place two bets, then of course you need to create/setup 2 Place Bet bots, and create executor bot for them, so as mentioned: “Execute Bots” bot setting, and this bot add as action bot to football bot BotName parameter.

    Of course if you are familiar with bot programming, you can create bot trigger script to orchestrate your place bet bots, this way you will setup only your action bots, and the rest is simplified by bot trigger code, so this way you will need 5 bot settings.

    The strategy orchestration just by setting up bfexplorer bots requires 9 bot settings.

  • Mir.
    4.2.2019 17:38:53

    Hi Stefan, it is interesting. Bot Executor seems very useful.
    But I am interested in a Football Bot. And its Start/Stop Criteria.

    I see that from a "managing" Match Odds markets  is very easy place bet on associated markets, for example at specific time and at specific score. It is good for one time action.

    Example: Footbal Bots via a Place bet bots place 5 bets:
    Correct score - 2×
    Over/Under 2.5 Goals - 1×
    Over/Under 1.5 Goals - 1×
    Match Odds - 1×

    Is there any simple solution through Football Bot (Start/Stop Criteria) how to orchestrate all affected markets, its market profit/loss!, time, actual score etc.


    Is it at all possible?
    And what about Market Data Request Limits in this cases with dozens footbal matches at the same time (saving use)?

  • Stefan
    1.2.2019 15:37:47

    Read this post: NinjaTrader

    All posts above ninja tool:

    http://bfexplorer.net/Articles/Search?text=ninja

  • Stefan
    8.1.2019 10:10:54

    Bfexplorer uses PayPal subscription system, and once activated by you it is PayPal making recurring payment in set interval and not Bfexplorer. Recurring payment is active till again you cancel it, so your bfexplorer subscription as well.

    Day of betfair api activation in some cases is not the same day when PayPal recurring payment was made, as betfair api activation really takes place only when your betfair subscription code expires, and of course you are still active subscriber, this is set to 30 days.

    For instance, as bfexplorer offers trial period, the first betfair api activation is done automatically when you install bfexplorer app, and login to betfair. Now still in trial period you buy your monthly subscription, activating PayPal recurring payment, as your betfair api access is still valid, it is not generated new subscription code, but it is done later when your befair subscription code expires.

    So in this case your subscription code can be activated later, and the day when your betfair subscription code expires is not the same as the day PayPal recurring payment was done.

    As said before those days could really differ in 30 days. For instance, PayPal recurring payment is done each 30 days, but as your betfair subscription code is really activated by your betfair login, those are requirements from betfair, then when you take some holiday from betfair trading for instance for X days and you did so coincidently at day when PayPal recurring payment was made, then difference between PayPal payment and your betfair api subscription expiration day will differ for these X days, after your will login to betfair with bfexplorer app again, so your new betfair subscription code will be generated again.

    Even users using bfexplorer by running automated trading systems, in fully autonomous mode (24/7) on betfair, must re-login with bfexplorer when betfair subscription code expires. Of course they can do so just by opening second bfexplorer app instance, as bfexplorer subscribers could execute as many of bfexplorer app per betfair user name as needed. For such users, common sense says that better alternative is one year subscription.

  • Stefan
    18.12.2018 16:29:37

    When testing this horse racing strategy on today’s races using Bfexplorer Bot Executor tool, the bot trigger the action bot on 4 markets up till now, all trades in profit. The rest of races where the action bot has not been triggered the favourite were bred in Ireland.

    Testing this horse racing strategy

  • Stefan
    5.11.2018 18:39:38

    This is a tutorial of building betfair bot, and testing trading strategy, therefore I leave many things unanswered, but of course for those who are interested they could draw their own opinion. Here is another video:

    https://youtu.be/HlmTx53oTdY

    1)

    Liability increases from number of bets placed after goal is scored, as in many cases the problem with fake score occurred there were placed two additional bets. This is actually good when testing a strategy as for those who are not able to judge all risks in running such strategies, these fake score bets showed what could go wrong.

    Fakes score can be fixed by double checking score results at set time interval, or by checking/getting scores from more reliable sources than betfair ones.

    2)

    When testing this strategy I did not set closing market bet position when required profit is reached. Actually “Close Market Bet Position” bot was executed but with unrealistic profit target, as I was more interested to learn what maximal liability can be reached just by requiring 2 Euro payout.

    No  0 – 0 correct score bet was placed, again when you think about this strategy you will get maximal profit on matches ended by 0 – 0, I do not have current statistics but depending on league there is around 5 – 8%  games ending with 0 – 0 draw.

    This strategy can be executed by closing 0 – 0 in profit when using reasonable profit, so strategy could end on correct score market, avoiding this way risk of big liability on match odds trading when a lot of goals is scored.

    3)

    When executing this strategy on match odds market only, you can set maximal liability of potential bet, or match time at what bot does not place such bet when first goal is scored, as odds after goal is scored depends not only on team who scored but of course on match time remaining to the match end. If you watched my videos you could see that a lot of such bets introducing big liability were placed at 85 and more minute of the match.

    4)

    None strategy is 100% profitable, you must learn to take loss as well, when I start testing any strategy I do not set Loss parameter, I do so when fine tuning promising strategy, and that can be judged very simply, just by counting number of total trades, and losing ones.

    So bot should be programmed, not just take required profit, but depending on match time, potential liability after next goal is scored, and of course when score is locked in our favor, close bet position in profit can be switched off.

    5)

    As said before most difficult part is to take loss, to judge that you need to execute a lot of trades.

    6)

    In my tests I did not selected matches on which I run this strategy, again it is clear that profitability depends on this selection process as well. I think anyone after reading this post and watching some of my videos should realize that big risk for this strategy are goals scored at the end of the match so after 90 minute. Some statistical methods of choosing “right” matches to trade on could help avoid risk of big bet liabilities.

  • Mir.
    5.11.2018 17:08:08

    ad) Results!
    Yes, it is specific strategy for selected markets, but It is crazy!
    A huge! liability, risky betting on small odds at the end of the matches etc.

    What about liquidity? I doubt that at the last minute one bet can reverse the betting result.

    I wonder how to set the strategy differently to make it profitable, but not so risky (if possible, on real markets)
    Otherwise, thanks for testing this strategy.

  • Mir.
    5.11.2018 12:48:17

    Oh crap!

    I never check the running of the scores...
    Thousands of matches, sorry, not for me. But I can check if score decrease on monitored markets, how many and where.

    After all, it is interesting. Thanks

  • Stefan
    5.11.2018 12:39:10

    Checking results:

    https://youtu.be/RYxd64S1B2s

     

  • Stefan
    5.11.2018 11:11:30

    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.