Comments

Despite this existing solution, I would like to return to the original intent.

Switch the bots only by win/loss criteria.

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

I make simple bot (used Execute Trigger bot with MiroBotTrigger - I can set many others parameters in one bot) and therefore it is difficult to set criteria - such as the Selection Profit Balance.

Streak L-L-W is can be still negative by ProfitBalance, but for staking plan situation can be different

I want to make one universal bot (triggers - with different CSV files) cover all selections.

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

I want to use only "Place Bet and Close Selection Bet Position" because there is finished trading cycle (open bet -> close bet).

Selection variable:
I think that we need selection variable with result of the finished trading cycle. This result will be new criteria for switching a bots by the bot "If then Else"

Paul, bfexplorer (Professional) allows monitoring hundreds of betfair markets, therefore I did not implement any notification system as a core feature to the application user interface (UI) but instead such notification system is implemented by different bfexplorer bots.

This approach allows switching notifications on just for selected markets, well by executing a notification bot/s on such markets. Using bot executor tool you can automate this approach, for instance automatically open a race 10 minutes before race start time, and executing “Horse Racing Race Status” if you want to be informed about a race status.

Why I think is this approach better?

Well, you asked for market status notification changes (open, suspended, open in-play, closed), but someone else could ask for bet matching notification, or football/tennis score notification, and so on, you name it.

If such notification system had been built in the core application UI, then in the application setting I should add different settings for different notification systems. On the other hand a bot approach allows me to extend the bfexplorer features without adding new features to core bfexplorer backend, as bots or custom triggers are plugins/extensions.

I added video to your article showing how you can use “Horse Racing Race Status Bot”.

Hi Stefan:

I've been a few weeks without access to the forum and BFE for personal reasons. Now I look back and I no longer have access to pro subscription. Nor does it provide me a key to access the free. I bought a basic subscription.

In another order of things, the solutions to the case studies are available?

Thanks in advance

 Thank you for your help.

Yes, PreviousSetIndex set to 1 will evaluate the first set result.

Just think about it, and different possibilities you have got when using all parameters. You can set SetsScore for instance to 1 – 1, so now if you want you are able to setup a bot to trigger bot execution depending on how was played the first or second set.

Similar like for SetsScore, you can use more scores for PreviousSetGamesScore separating them by ;

If I understand correctly, the parameter PreviousSetIndex should be set to 1:

The tennis bot must know which previous set should be evaluated, and that is set by parameter PreviousSetIndex.

A zero in a parameter value is generally used as not used bot parameter feature, and this approach is used through all bfexplorer bots.

You can use the tennis bot without requiring previous set feature, right? Or you can use the tennis bot without sets score, right? So not setting SetsScore, or leaving not valid value for PreviousSetIndex, switches off the parameter/feature evaluation.

6-3 - this is the result of the first set.

Have we got a zero set in a tennis match?

You please see whether I have properly set parameters:

If in the 1st set result is 6-3 then buy bet

Why does not work this setting?

Last days I had been working on racingpost data provider, you can see it in my test bot using spreadsheet.

The racingpost data provider extends a set of data providers I developed before for some betfair bot projects: timeform, olbg, sportinglife.

I have just released the latest version of bfexplorer adding PreviousSetGamesScore parameter.

I renamed some parameters so change your bot settings to reflect new parameters. SetsScore and PreviousSetGamesScore parameters support multi value settings, used separator is ;

For now the tennis bot supports two parameters SetScore and GameScore, only GameScore parameter is mandatory.

GameScore defines current set score. What you suggest could have more general use if we introduce on which set the game score should be applied.

So I would suggest using: PreviousSetGameScoreIndex parameter and PreviousSetGameScore parameter.

What do you think about it?

Eduardo, I do not know from which comment you started to follow that debate, but as you could maybe notice after 20 or so comments, all that was just chitchat. Why I call it chitchat? Because from what was said, I created two other articles with videos, and Ilya did not bother to comment that or mentioned it in his further debate.

My conclusions:

1) It is impossible that whenever someone from this forum will cooperate with other member to make anything which could be shared.

2) The level of understanding of the base features any betfair trader needs to manage is very poor.

3) I am sure now that right naming of essential features is very important. It is pity that on this forum there is actually no member now, who natively speaks English and would be willing to correct us all. For instance the name bot, from my understanding now it was unfortunate to call it bot, maybe order, rule, or something like that would be more appropriate. I already renamed “My Bots” view to: “My Orders/Bots to Execute”.

Eduardo, your concern was subscription level and amount of features you can buy for your subscription, but you know that it was never a problem. Whenever someone asks me for Professional subscription for an amount he/she is willing to pay or donate I did/do so, but he/she should be at least an active bfexplorer forum user.

Eduardo, I am sorry to hear that you lost some money just because you did not understand what staking plan you actually execute with your strategy and what maximal liability could be reached by your bot settings.

I think you used some of bot triggers from My Staking Plan series, describing how to program a bot trigger with a custom staking plan:

The staking plan was implemented by Eric’s requirements for his betting strategy:

If there is a loss, double my stake and add previous loss to my stake.
If there is a loss and my previous bets are in profits, then double stake only.
If there is more than 3 consecutive losses then bet with default stake. 

So the bot trigger implemented two parameters: Stake and NumberOfRecoveryBets. Depending on what betting strategy was executed, we do not know if his action bot placed back or lay bets on selected horses and at what average odds range, only he knew what could be his maximal labiality on his final bet placed at the recovery plan.

Knowing what you actually do and what could be maximal liability bet when executing any staking plan is absolutely crucial for any successful strategy.

The worst case scenario is when all goes well when testing and without aware of the risk you switch to execute your strategy with real money too soon. That is a price you paid to learn that you must test weeks and not days to test your strategy.

Here are my answers to your original question:

First of all, you already used a bot trigger with staking plan implementation, so if you wanted to add some stop criteria for your action bot, for instance when total target loss is reached then such criteria should be added to the bot trigger code.

You tried to use “Execute Till Target Profit” bot setting the bot parameter: TargetProfit to -10.0 (minus ten), hoping that such bot setting will stop your action bot execution when loss is reached.

Such settings cannot definitely work, and there 2 reasons why it cannot work.

The bot implementation works only with profit, if bot would implement target loss then you could find it in bot parameters listing, for insistence the parameter would be named: TargetLoss.

The bot checks if target profit is reached by comparing the current profit with the target parameter value. When current profit is bigger or equal to set target profit then action bot execution is stopped.

In school we learned that zero or positivity value is bigger than any negative value, right? Even minus one is bigger than minus two, therefore your bot stopped action bot execution at first execution, as 0 is bigger than -10.

I can update the bot: “Execute Till Target Profit” to work with a target loss in my next bfexplorer release.

 Hi Stefan:

A few days ago I lost € 240 with a stake of 1 €, I used the robot "Lay favorite with my staking plan. -10"

I had four straight losses and did not stop when the robot lost 10 €.

Please, Stefan, how can I do so that the robot stops when it reaches the established loss?

It would be possible to divide the bankroll into several parts and using only a part and if anything is unsettles, which lost only one of the parts and not all parts?

Thanks in advance.

Please translate to Spanish what it means “Entry Criteria”.

Those parameters, if set then refer to the current market ProfitBalance, so your action bot will continue its execution only if current Profit Balance on the market is greater or equal 10, that means that on this market you already placed bets and your current profit balance is >= 10.

It would be really great if you mention which bot you are using, and if you refer to some article on forum, then add link to this article.

Sorry Stefan, but I had not seen "Trigger Parameters"