Projected SP price range is different

[Luke.B]

Hi,
Betfair Projected SP doesn't follow the standard betting price brackets so in automation you can capture a projected SP price range correctly
Eg Projected sp might be 5.04
But if i want to capture 4 - 5 in a lay bet
it looks like this in automation >4 and less than 5.1
And if i want to back 5-6 it looks like >5 and less than 6.1

Because projected sp doesn't follow these brackets my bet triggers for both back and lay...or in some other variation i do it double backs a runner.

For projected SP price range can we make it .01 increments please?

[gazuty]

Hi,
Betfair Projected SP doesn't follow the standard betting price brackets so in automation you can capture a projected SP price range correctly
Eg Projected sp might be 5.04
But if i want to capture 4 - 5 in a lay bet
it looks like this in automation >4 and less than 5.1
And if i want to back 5-6 it looks like >5 and less than 6.1

Because projected sp doesn't follow these brackets my bet triggers for both back and lay...or in some other variation i do it double backs a runner.

For projected SP price range can we make it .01 increments please?

Don't go for 5.1. Just stick with 5. You'll then get the back and not the lay.

[Luke.B]

No cant i need to capture 5 there are alot of settles at sp at that price.
There is no >= only greater than and less than so to capture 5 you need to go next bracket up.
Maybe that is easier solution.
Adding >= and <= to the automation functions.

[Dabbla]

Store the projected SP as a SV.
Then use a SV condition to determine if the SPSV is less than <= to 5

[Luke.B]

Hi dabbla.
Can you use muliple sv on same runner.
Currently using sv to work out stake as i use level stakes not set limits as my staking plan

[Dabbla]

Yes , you can use as many as you like.

[Luke.B]

Ok sounds like i need to get my head around Stored values. I must admit in my head i cant see how all the automation rules fit together yet..and what the capabilities are.