Race Type Condition

Help improve Bet Angel.
Post Reply
scribbles
Posts: 34
Joined: Mon Jul 02, 2012 9:04 pm

Quick Suggestion.

In a similar way to race length condition.

How about a simple market condition we can set (Equals / Does not Equal) for;

hcap
nov
mdn
etc

chs
hrd
etc

and maybe a custom txt field as well as an alternative, so we can use for different races, or even different (non racing) markets.

Thanks
welshboy06
Posts: 165
Joined: Wed Mar 01, 2017 2:06 pm

I've not tried it myself but you could do this in excel easily. Just check if the race info contains one of the above words.
scribbles
Posts: 34
Joined: Mon Jul 02, 2012 9:04 pm

Thanks for the response

Yes I could do it, and would consider doing so if I needed this in isolation, but if you have advanced bots running, it means porting all of the additional settings to excel too..
dm1900
Posts: 71
Joined: Sun Jan 15, 2017 10:02 pm

I would 100% be in favour of this! A 2m4f hcap is so different to 2m4f turf
ricardodeano
Posts: 205
Joined: Tue Oct 06, 2015 2:03 pm

I don't suppose this is on the "to do" list is it?
sionascaig
Posts: 1053
Joined: Fri Nov 20, 2015 9:38 am

+1

This would be a really handy condition.

At present you have to apply rules to appropriate race types which is a manual process. Would be really handy if it could be captured in conditions.
User avatar
jimibt
Posts: 3641
Joined: Mon Nov 30, 2015 6:42 pm
Location: Narnia

sionascaig wrote:
Thu Jul 02, 2020 12:21 pm
+1

This would be a really handy condition.

At present you have to apply rules to appropriate race types which is a manual process. Would be really handy if it could be captured in conditions.
+2

as suggested in the OP, this condition could simply be a freeform text field that targets the event description using a contains or not contains matching, so, you'd have the ability to discrern a 2m2f hcap chs from a 2m2f nov chs (i.e. NOT CONTAINS 'nov chs') or for very explicit -> (CONTAINS 'hcap chs') etc...

this would mean that the generics were still maintained as the same freeform text field could be used on Tennis, Cricket, Football etc as it's not tied to Horse Racing event descriptions directly.
sionascaig
Posts: 1053
Joined: Fri Nov 20, 2015 9:38 am

jimibt wrote:
Thu Jul 02, 2020 12:27 pm
sionascaig wrote:
Thu Jul 02, 2020 12:21 pm
+1

This would be a really handy condition.

At present you have to apply rules to appropriate race types which is a manual process. Would be really handy if it could be captured in conditions.
+2

as suggested in the OP, this condition could simply be a freeform text field that targets the event description using a contains or not contains matching, so, you'd have the ability to discrern a 2m2f hcap chs from a 2m2f nov chs (i.e. NOT CONTAINS 'nov chs') or for very explicit -> (CONTAINS 'hcap chs') etc...
I appreciate that BF does not always use consistent names, e.g. "Nov Stks" could be "Nov Stakes" but Jimbits idea works fine for me... Incidences of these inconsistencies are v low...
Atho55
Posts: 637
Joined: Tue Oct 06, 2015 1:37 pm
Location: Home of Triumph Motorcycles

+1 from me
User avatar
megarain
Posts: 2040
Joined: Thu May 16, 2013 1:26 pm
Contact:

+1

Would b v useful to sort out maidens etc
User avatar
jimibt
Posts: 3641
Joined: Mon Nov 30, 2015 6:42 pm
Location: Narnia

megarain wrote:
Thu Jul 02, 2020 1:11 pm
+1

Would b v useful to sort out maidens etc
likewise, on the greyhounds you could target only certain grades, i.e. A5, D2, NOT D8 etc, etc
User avatar
jimibt
Posts: 3641
Joined: Mon Nov 30, 2015 6:42 pm
Location: Narnia

jimibt wrote:
Thu Jul 02, 2020 1:50 pm
megarain wrote:
Thu Jul 02, 2020 1:11 pm
+1

Would b v useful to sort out maidens etc
likewise, on the greyhounds you could target only certain grades, i.e. A5, D2, NOT D8 etc, etc
i think what I'm saying is that by allowing the input to be freeform (but with strict rules), it means that the nuances of different sports can be captured as required, without having to present a ton of dropdown list options.

looking fwd to seeing this in next version -lol
User avatar
firlandsfarm
Posts: 2688
Joined: Sat May 03, 2014 8:20 am

sionascaig wrote:
Thu Jul 02, 2020 12:36 pm
I appreciate that BF does not always use consistent names, e.g. "Nov Stks" could be "Nov Stakes" but Jimbits idea works fine for me... Incidences of these inconsistencies are v low...
Agreed, but … if it had operators such as AND and OR you could build a library of Betfair nuances and have …

Contains: Nov Stks OR Nov Stakes

… or maybe with wildcards just …

Contains: "Nov *"
User avatar
jimibt
Posts: 3641
Joined: Mon Nov 30, 2015 6:42 pm
Location: Narnia

firlandsfarm wrote:
Sat Jul 04, 2020 6:51 am
sionascaig wrote:
Thu Jul 02, 2020 12:36 pm
I appreciate that BF does not always use consistent names, e.g. "Nov Stks" could be "Nov Stakes" but Jimbits idea works fine for me... Incidences of these inconsistencies are v low...
Agreed, but … if it had operators such as AND and OR you could build a library of Betfair nuances and have …

Contains: Nov Stks OR Nov Stakes

… or maybe with wildcards just …

Contains: "Nov *"
this all looks to be headed in the right direction with enough freeform input to capture complex market mixes but with a simple and recognisable *syntax* that is used already in other parts of the application (market filters/quick picks etc)....
CallumPerry
Posts: 575
Joined: Wed Apr 19, 2017 5:12 pm
Location: Wolverhampton

+1

Always educated to choose markets carefully, heck Peter's mantra, "Every strategy a market and every market a strategy" means this would be a big improvement to an already amazing piece of software.
Post Reply

Return to “Suggestions”