Alert to unmatched Big Bet £10k+
Ezpz with stored values –
Have rule firing every x sec (money available to back/lay) stored as SV st x ticks away
Make as many as you want both sides in one rule (e.g. 25 back 25 lay = 50 SV's)
Make another 50 new SV with prefix like Previous_[SV name 1-50] and chuck them before the 50 current values
Now in 2nd rule u just check if current value - Previous value is > £10,000 to signal an increase of 10k+ versus the last refresh
You may also want to confirm it stays there for y seconds or whatever other confirmation rules
It's not guaranteed one person but if its a market with just 0-2000 at prices then suddenly 10k+ at a value within a few sec it's like just one acc in pre race horses for example
Have rule firing every x sec (money available to back/lay) stored as SV st x ticks away
Make as many as you want both sides in one rule (e.g. 25 back 25 lay = 50 SV's)
Make another 50 new SV with prefix like Previous_[SV name 1-50] and chuck them before the 50 current values
Now in 2nd rule u just check if current value - Previous value is > £10,000 to signal an increase of 10k+ versus the last refresh
You may also want to confirm it stays there for y seconds or whatever other confirmation rules
It's not guaranteed one person but if its a market with just 0-2000 at prices then suddenly 10k+ at a value within a few sec it's like just one acc in pre race horses for example
I would have to make 190 stored values for a start.eightbo wrote: ↑Fri Aug 28, 2026 10:34 amEzpz with stored values –
Have rule firing every x sec (money available to back/lay) stored as SV st x ticks away
Make as many as you want both sides in one rule (e.g. 25 back 25 lay = 50 SV's)
Make another 50 new SV with prefix like Previous_[SV name 1-50] and chuck them before the 50 current values
Now in 2nd rule u just check if current value - Previous value is > £10,000 to signal an increase of 10k+ versus the last refresh
You may also want to confirm it stays there for y seconds or whatever other confirmation rules
It's not guaranteed one person but if its a market with just 0-2000 at prices then suddenly 10k+ at a value within a few sec it's like just one acc in pre race horses for example
Ok this is what I am looking for:eightbo wrote: ↑Fri Aug 28, 2026 10:34 amEzpz with stored values –
Have rule firing every x sec (money available to back/lay) stored as SV st x ticks away
Make as many as you want both sides in one rule (e.g. 25 back 25 lay = 50 SV's)
Make another 50 new SV with prefix like Previous_[SV name 1-50] and chuck them before the 50 current values
Now in 2nd rule u just check if current value - Previous value is > £10,000 to signal an increase of 10k+ versus the last refresh
You may also want to confirm it stays there for y seconds or whatever other confirmation rules
It's not guaranteed one person but if its a market with just 0-2000 at prices then suddenly 10k+ at a value within a few sec it's like just one acc in pre race horses for example
In the last 10 secs before the off until -1min if a stake appears => £600 on any runner i would like to place 7 liability staked lay bets at and including the 7 ticks above that stake, unless there is not enough space bewteen the big stakes price and the current touch lay price (best reverse market price) for example if there is only 3 ticks then just fill the 3 ticks between the stake and the touch price. I have started a .baf file but it is quite elaborate only for the first part of the idea. I have servants which are easy to use but as soon as you try to turn it into an automation file you descover that a human can do so many complex things really easily. But trying to transfer your idea to work with Bet Angel seems impossibly hard.
- jamesedwards
- Posts: 6134
- Joined: Wed Nov 21, 2018 6:16 pm
You can use a stored value to cycle up through and check the volume at each price tick.
This will only check one price per refresh, but if you duplicate the relevant rulelines you can increase the number of prices checked per refresh to as many as you like. Also you could start from higher than 1.01 from wherever you wish. But you get the idea.
This will only check one price per refresh, but if you duplicate the relevant rulelines you can increase the number of prices checked per refresh to as many as you like. Also you could start from higher than 1.01 from wherever you wish. But you get the idea.
You do not have the required permissions to view the files attached to this post.
