I want to at a Contexual price but only if there is less than a certain amount laying.
Can this only be achieved via a Stored Value?
If so how do it to i have to set up the 1st part of the rule to set the contexual price and then use that to check the amounts laying?
Laying if under a certain amount is laying?
So these are the elemnts of the rule but its still placing bets where there are larger amounts laying.
Obviously im doing something wrong.
As always any help is much appreciated!
Obviously im doing something wrong.
As always any help is much appreciated!
You do not have the required permissions to view the files attached to this post.
So i have used this (and it works) to only place a lay if there is Under 1000 laying
What i would like to do is extended this to a range. Ideally i want to use a shortcut fpr example laying top price 1.50 (if under £100 is laying) and all prices down to say 1.45. So if there is £500 laying at 1.49 no bet would go in but if 1.48 had £10 laying it would place a bet.
I tried using the orginal contexually price -1 but in the conditions you can see im using the how much is at that price as the test. This means that each price is not tested it just tests the orginal price.
So i assume i need to when selecting the original price i need to say this as a stored valebut how then to i attach this to the other elemnts of the rule laying at different prices?
I do hope this make sense
I tried using the orginal contexually price -1 but in the conditions you can see im using the how much is at that price as the test. This means that each price is not tested it just tests the orginal price.
So i assume i need to when selecting the original price i need to say this as a stored valebut how then to i attach this to the other elemnts of the rule laying at different prices?
I do hope this make sense
You do not have the required permissions to view the files attached to this post.
You will need to make a scanner type bot, that will look at one price at a time.
This should point you in the right direction.
Rule 1 , this will just set the range. Sv (start range) = context price 1.7 .
SV (end range) context price -5 ticks.
No conditions, no bets placed, trigger 1 time.
Rule 2 this will be the same as the rule you already have, but looking at the SV (start range) instead of the context price. You will place your bets at SV (start range)
Add a condition that the SV (start range) is=> SV (end range)
Then add a SV to this rule , SV (start range) , SV (start range) - 1 = 1.69.
Trigger unlimited.
Rule 3 will same as rule 2 but false, money available is > 1000
Add a condition that the SV (start range) is=> SV (end range)
Then add a sv to this rule , SV (start range) , SV (start range) – 1 tick = 1.68
no bets placed. trigger unlimited.
At this point it should keep looping back to rule 2
Rule 4 ,You might want to add a stop servant rule, with the condition,
SV (start range) is < SV (end range)
It will probably need some extra logic in places but that’s a rough road map.
Then I had this thought.
There are similar other ways of doing it, you could have multiple back rules, but each looking a different SV.
Eg sv 1= 1.7,
sv 2= sv1 – 1 and so on.
Thinking about it, this might actually be an easier way of doing it.
Have a think what’s best for you.
This should point you in the right direction.
Rule 1 , this will just set the range. Sv (start range) = context price 1.7 .
SV (end range) context price -5 ticks.
No conditions, no bets placed, trigger 1 time.
Rule 2 this will be the same as the rule you already have, but looking at the SV (start range) instead of the context price. You will place your bets at SV (start range)
Add a condition that the SV (start range) is=> SV (end range)
Then add a SV to this rule , SV (start range) , SV (start range) - 1 = 1.69.
Trigger unlimited.
Rule 3 will same as rule 2 but false, money available is > 1000
Add a condition that the SV (start range) is=> SV (end range)
Then add a sv to this rule , SV (start range) , SV (start range) – 1 tick = 1.68
no bets placed. trigger unlimited.
At this point it should keep looping back to rule 2
Rule 4 ,You might want to add a stop servant rule, with the condition,
SV (start range) is < SV (end range)
It will probably need some extra logic in places but that’s a rough road map.
Then I had this thought.
There are similar other ways of doing it, you could have multiple back rules, but each looking a different SV.
Eg sv 1= 1.7,
sv 2= sv1 – 1 and so on.
Thinking about it, this might actually be an easier way of doing it.
Have a think what’s best for you.