Question around using Stored Values to Influence the Stake Placed

[smgreyuk]

Ah, I didn’t know that.

And as if by magic after doing that, the Column for Counter gets a zero , ha ha.

This now looks promising, there’s a potential race at 18:14 Monmore. Fingers crossed.

One more question (you’ve been so helpful, you’re a credit to the community) as Counter is a Bet Angel SV, if I was to close BA down for the day and say the last race was a loss (Counter= 1 at that point) and then log back in another day, would you expect counter to still = 1 or would I need to manually set it to 1 for when the first race triggered?

[jamesedwards]

Ah, I didn’t know that.

And as if by magic after doing that, the Column for Counter gets a zero , ha ha.

This now looks promising, there’s a potential race at 18:14 Monmore. Fingers crossed.

One more question (you’ve been so helpful, you’re a credit to the community) as Counter is a Bet Angel SV, if I was to close BA down for the day and say the last race was a loss (Counter= 1 at that point) and then log back in another day, would you expect counter to still = 1 or would I need to manually set it to 1 for when the first race triggered?

It will count for that instance of Bet Angel. So if you close and restart Bet Angel the count will start again at 0.

[smgreyuk]

I have tried it yesterday and it hasn't worked as expected. It's doing zero counter triggers but the counter isn't incrementing after a loss (nor resetting after a win):

Screenshot 2024-10-11 200121.png

I thought it could be down to the "Market_P&L" being zero BEFORE the race finishes.

Today I tried to include another Betfair SV "P+L" that took the value of "Market_P&L" and ignored storing "Market_P&L" when it was zero, then used the P+L SV in the increment and reset rules, but it's made no difference.

I'll attach the file in it's current state:

Dutch Favourite 2 with 2.0 to 5.0.baf

I can't seem to figure it out why the "Increment Counter after loss" and Reset Counter after Win" rules are not firing

I even initialised the SV "P+L" (just like the "Counter" SV) but no luck

[jamesedwards]

It's probably due to the other rulesfile that creates the "Market+P&L" SV. Post that file.

[smgreyuk]

Sure, thank you

Display Name of Winner with P&L's.baf

[jamesedwards]

It's all working fine for me, once I remove your "P+L" line and revert it back to using "Market_P&L".

Capture42.JPG

Use these:

Dutch Favourite 2 with 2.0 to 5.0 (1).baf

Display Name of Winner with P&L's.baf

[jamesedwards]

You might also find it easier to manage if you combine your rules into one file rather than two.

Dutch Favourite 2 with 2.0 to 5.0 combined.baf

[smgreyuk]

Wow, thank you ever so much. You’ve gone beyond for me with this and I am so grateful.

I’m currently minding my 7 month old but I shall give this a go over the weekend.

[smgreyuk]

Hi again,

So this time I have taken the combined file from you, I have made no adjustments to it but it still doesn't want to increment or reset the counter for me. Not sure why there is a difference between my attempt and yours.

Screenshot 2024-10-12 221552.png

Could it possibly be a setting difference somewhere?

The version of Bet Angel I am using is 1.62.0 which I believe is up to date.

[jamesedwards]

My fault.

When I merged the two rulefiles I put the counter rules above the P&L rules. I'm guessing Guardian only does one sweep through the rulefile once the market is closed, so the counter rules need to sit below the P&L rules for them to trigger.

Use this version where I've moved them to the bottom.

Dutch Favourite 2 with 2.0 to 5.0 combined v2.baf

I've tested this exact rulefile this evening and it's working fine.

Capture43.JPG

[jamesedwards]

I still don't recommend you trade with this rule however because long term it is doomed to failure. There is no reason why the 1st or 2nd fav is any more likely to win a race just because they failed to win the previous. Doubling your stake after every loss is a sure route to the poor house.

viewtopic.php?t=17623

https://en.wikipedia.org/wiki/Martingal ... ng_system)

[smgreyuk]

Hi,

I hear you and I am mitigating the number of wins and losses in the long run.

That's now working Massive thank you for all of your help!

[smgreyuk]

Hi James Edwards,

I have spotted a slight snag in the setup, I was wondering what your thoughts would be to get around it?

Screenshot 2024-10-14 192042.png

For the blue highlighted race in the screenshot, I would've expected it to fire the bet for the counter being 2, but it didn't, it placed the bet with the counter still being at 1.

After looking at the logs between the race above Monmore (15:01) and the highlighted blue race of Oxford (15:03) I spotted where this file can still got slightly wrong:

Screenshot 2024-10-14 192356.png

In the above screenshot the log to increment the counter happens at 15:03 and 58 seconds at Monmore (the earlier race)

Screenshot 2024-10-14 192521.png

However for the next race it has calculated the stake at 15:02 and 58 seconds which is a minute earlier than when the counter is incremented despite the race time being 2 minutes after, therefore the Oxford race gets the wrong counter integer applied (1 instead of the expected 2)

I suppose it was by chance for two races to be very close in times and for both to be candidates for the file to trigger.

Maybe a delay somehow until the counter integer has changed from the last race? Unless there is a clever method in the general tab to overcome this eventuality? (Would using the add market's betting delay be the answer?)

[jamesedwards]

Hi James Edwards,

I have spotted a slight snag in the setup, I was wondering what your thoughts would be to get around it?

Screenshot 2024-10-14 192042.png

For the blue highlighted race in the screenshot, I would've expected it to fire the bet for the counter being 2, but it didn't, it placed the bet with the counter still being at 1.

After looking at the logs between the race above Monmore (15:01) and the highlighted blue race of Oxford (15:03) I spotted where this file can still got slightly wrong:

Screenshot 2024-10-14 192356.png
In the above screenshot the log to increment the counter happens at 15:03 and 58 seconds at Monmore (the earlier race)

Screenshot 2024-10-14 192521.png
However for the next race it has calculated the stake at 15:02 and 58 seconds which is a minute earlier than when the counter is incremented despite the race time being 2 minutes after, therefore the Oxford race gets the wrong counter integer applied (1 instead of the expected 2)

I suppose it was by chance for two races to be very close in times and for both to be candidates for the file to trigger.

Maybe a delay somehow until the counter integer has changed from the last race? Unless there is a clever method in the general tab to overcome this eventuality? (Would using the add market's betting delay be the answer?)

You have to wait for Betfair to close the race before Bet Angel knows your P&L from that race. Therefore it's possible the updating of the counter don't follow the scheduled order of the races.

[smgreyuk]

Hmm

Could this work?

Screenshot 2024-10-14 212159.png

It's a Stored Value Changed Condition on the actual dutching rules. I am thinking that it checks to see if the "Counter" SV has changed in the last hour (1 second to 3600 seconds, or maybe even 99999 seconds, whatever the highest value can be used) only if it has changed then it puts the dutch back bets on... granted some races will be missed with this approach but at least it avoids putting incorrect stakes on

... I am not sure if this would work for when Counter is initialised at the start of the session (as in it's the first race of the day, Counter is initialised to 0, would it consider NULL to 0 as a change?) -

ADDITIONAL
According to the user guide:

"Note: The creation of a Stored Value will be considered as a ‘change’"

So this does sound promising, I just want to get your take on the approach first