COUNT OF MATCHED BETS WHEN USING OFFSETS

[Dr Ginhog]

Hi all,
Can anybody help?
I have been looking at laying the three favs by offset varying my ticks for each and even after a few days I cannot believe the number of changes I have had to make due to mistakes made. Who said writing a Rule file was easy ?
Only sometimes Peter!!!!! The program is proper awesome but learning curve is steep.
A number of issues arise in regard to limiting my bets to 1 for each of the 3 favs in that if I use the number of matched bets filter do offset bets count as 1 or 2
Also when bets are matched partially each partially matched bet is counting in the guardian screen with the same reference.
To limit to 3 offset bets is number of Matched bets = 0 correct?
2 other issues arise -
(a) I fixed the order to prevent same selection twice on fav flip flop . If I put fix order allowed to trigger
20 times would the order potentially change at every trigger instance or does the first one stick.
(b) You nominate your favouritism in the "Applies" to in general parameters. In conditions do you have to then stick to
the "Nomination- applies to position (x) sorted in order of favouritism" . Presumably if instead you used Current(in position x in order of favouritism.) does this overwrite the previously fixed order to current order of favouritism at that instant or instant of triggering of bet?
Mike

[Dallas]

You could look at using 'Number of place bets triggered' and/or 'Matched bets amount' either with or instead of your number of matched bets.

https://www.betangel.com/user-guide/num ... 3D&mw=MzIw
https://www.betangel.com/user-guide/mat ... 3D&mw=MzIw

Between these 3 conditions you should have full control over how/when bets are triggered for any setup you might be using

[Dr Ginhog]

Hi
Top Man thank you Dallas. I get it use all three but it seems to me Place bet trigger is the Unmatched/Matched combined
anyway. No harm in using whatever works though.
I was wondering if there is a possible issue with using Place bet trigger and Fill/kill.
If say you were to use Place bet trigger = 0 as your filter.
If bets were killed would not the Place bet trigger count increase leaving you with no chance of a placed bet after that.
I gather Fill/kill time condition is needed to avoid the the gap in time when an additional bet might be placed due to the
refresh rate and Betfair bet registering delays but I suppose you need an extended Fill/Kill interval to ensure no kill yet still avail of the Fill part and use of the Fill/* time condition. Does that make sense.?? Sorry about complicating things im just trying to get a full picture of whats going on.

[Dallas]

The fill/kill bet time is mainly used on in-play markets were there is a delay on bets so as to avoid additional bets being triggered while the offset of the first bet is waiting for the delay to pass.

Using place trigger equals 0 if your first bet on a selection is killed (not fully filled) then it wont allow further triggers, so in this situation this would nt be required. Instead either number of matched bets or amount of matched bets will do the job

One thing to be aware of and that you'll need to decide in advance is - Assume your stake is £100 and only £44 is matched before the remainder is killed you would need to decide if you want to set your rule up to allow a further £100 stake to be triggered meaning you could have far more than the initial £100 eventually matched or accept that this selection has only had £44 matched (trying to add a further £56 to make it up to £100 is not possible).

Assuming that selection and your looking for 1 bet only on a selection and if you get it only part matched then you'll leave it at that then use either;- number of matched bets or amount of matched bet = 0, depending on the price your asking for (ie best reverse price or several tick away from current price) it may be better to increase you fill/kill to allow a little more time for it to be matched
Assuming you have your fill/kill time set to 60 secs you could set your rearm time to 65 secs to avoid double bets
or
you could set your re-arm time faster than your fill/kill time if also using a number of unmatched bets cond = 0 as this will prevent it from triggering.

Then if its being used in-play look at using the conditions detailed at the top of this post.

Sounds a lot to take in but once it all falls into place you'll see why there is the number of options - each does serve a purpose

[Dr Ginhog]

Hi Dallas,
Thats excellent thanks. That covers it Brilliantly .
Another question though to what extent if any does using signals help in this betfair delay problem.
I imagine it reduces the initial delay time to some degree as were not waiting for unmatched/unmatched bets to be registered by betfair.
Is that fair comment.

[Dallas]

Hi Dallas,
Thats excellent thanks. That covers it Brilliantly .
Another question though to what extent if any does using signals help in this betfair delay problem.
I imagine it reduces the initial delay time to some degree as were not waiting for unmatched/unmatched bets to be registered by betfair.
Is that fair comment.

Signals are very flexable and can be used in countless situations, they wont get you past the Betfair delay any faster but as there set locally they can be tested against straight after being set without having to wait for the delay and any triggered bets to be in the market.