Why is it under 'parameters' you can easily stipulate placing a bet a percentage under or over the actual SP, yet when you go into conditions, you can't do it? For example if I want a condition to be that the favourite is a certain percentage less than the second favourite, why can't I stipulate that by a percentage?
If you choose 'relative odds condition', you can say the actual SP of the selection in position 1 (sorted by favouritism) is less than the actual SP in position two (sorted in order of favouritism) minus or plus but it doesn't allow a percentage there, only ticks, or odds, which are no use to me. So the only way I have found to do it is use historic relative odds condition, then you can choose position 1 in order of favouritism vs position 2 in order of favouritism but you can't use actual SP there so you have to use 'last traded price' - then it allows percent, odds, tick or amount or percent using minus 1.0. The problem is this isn't the same as the SP. Why can't I do it with the SP?
Please help someone.
Many thanks
Can't use percentage as a condition with regard to BFSP?
- jamesedwards
- Posts: 4541
- Joined: Wed Nov 21, 2018 6:16 pm
You can find the % variance using custom ranking and a stored value then test that SV against the required condition.bests3lleruk wrote: ↑Fri Oct 03, 2025 7:46 pmWhy is it under 'parameters' you can easily stipulate placing a bet a percentage under or over the actual SP, yet when you go into conditions, you can't do it? For example if I want a condition to be that the favourite is a certain percentage less than the second favourite, why can't I stipulate that by a percentage?
If you choose 'relative odds condition', you can say the actual SP of the selection in position 1 (sorted by favouritism) is less than the actual SP in position two (sorted in order of favouritism) minus or plus but it doesn't allow a percentage there, only ticks, or odds, which are no use to me. So the only way I have found to do it is use historic relative odds condition, then you can choose position 1 in order of favouritism vs position 2 in order of favouritism but you can't use actual SP there so you have to use 'last traded price' - then it allows percent, odds, tick or amount or percent using minus 1.0. The problem is this isn't the same as the SP. Why can't I do it with the SP?
Please help someone.
Many thanks
You do not have the required permissions to view the files attached to this post.
-
- Posts: 36
- Joined: Wed Apr 01, 2020 7:58 pm
jamesedwards wrote: ↑Fri Oct 03, 2025 8:17 pmYou can find the % variance using custom ranking and a stored value then test that SV against the required condition.bests3lleruk wrote: ↑Fri Oct 03, 2025 7:46 pmWhy is it under 'parameters' you can easily stipulate placing a bet a percentage under or over the actual SP, yet when you go into conditions, you can't do it? For example if I want a condition to be that the favourite is a certain percentage less than the second favourite, why can't I stipulate that by a percentage?
If you choose 'relative odds condition', you can say the actual SP of the selection in position 1 (sorted by favouritism) is less than the actual SP in position two (sorted in order of favouritism) minus or plus but it doesn't allow a percentage there, only ticks, or odds, which are no use to me. So the only way I have found to do it is use historic relative odds condition, then you can choose position 1 in order of favouritism vs position 2 in order of favouritism but you can't use actual SP there so you have to use 'last traded price' - then it allows percent, odds, tick or amount or percent using minus 1.0. The problem is this isn't the same as the SP. Why can't I do it with the SP?
Please help someone.
Many thanks
z253.jpg
Okay I have had some difficulty with this, but I entered the stored value exactly as you showed, and then I updated custom ranking to in order of SP ascending. Then I went into conditions and I couldn't see the SP var% stored value I'd created so I entered the name manually under stored value name. Then I put the amount as 0.70 as I want the fav to be 30%+ lower than the second fav, is this right?
You do not have the required permissions to view the files attached to this post.
- jamesedwards
- Posts: 4541
- Joined: Wed Nov 21, 2018 6:16 pm
Sounds good. Recommend you try these things in practice mode so you can learn and try things out without fear of mistakes.bests3lleruk wrote: ↑Fri Oct 03, 2025 10:03 pmjamesedwards wrote: ↑Fri Oct 03, 2025 8:17 pmYou can find the % variance using custom ranking and a stored value then test that SV against the required condition.bests3lleruk wrote: ↑Fri Oct 03, 2025 7:46 pmWhy is it under 'parameters' you can easily stipulate placing a bet a percentage under or over the actual SP, yet when you go into conditions, you can't do it? For example if I want a condition to be that the favourite is a certain percentage less than the second favourite, why can't I stipulate that by a percentage?
If you choose 'relative odds condition', you can say the actual SP of the selection in position 1 (sorted by favouritism) is less than the actual SP in position two (sorted in order of favouritism) minus or plus but it doesn't allow a percentage there, only ticks, or odds, which are no use to me. So the only way I have found to do it is use historic relative odds condition, then you can choose position 1 in order of favouritism vs position 2 in order of favouritism but you can't use actual SP there so you have to use 'last traded price' - then it allows percent, odds, tick or amount or percent using minus 1.0. The problem is this isn't the same as the SP. Why can't I do it with the SP?
Please help someone.
Many thanks
z253.jpg
Okay I have had some difficulty with this, but I entered the stored value exactly as you showed, and then I updated custom ranking to in order of SP ascending. Then I went into conditions and I couldn't see the SP var% stored value I'd created so I entered the name manually under stored value name. Then I put the amount as 0.70 as I want the fav to be 30%+ lower than the second fav, is this right?