Bet type not available(td)
- johnnycomelately
-
Topic Author
- Platinum Member
-
- Posts: 3211
- Thanks: 295
Re: Re: Bet type not available(td)
11 years 10 months ago
Possibly something positive to come from this thread then(tu)
Please Log in or Create an account to join the conversation.
- Thor
-
- Platinum Member
-
- Posts: 2783
- Thanks: 468
Re: Re: Bet type not available(td)
11 years 10 months ago
Dev Wrote:
> With regards to Doncaster Race 4, we did not lay
> quartets as there were more than 20 runners in
> that race.
>
> When there are more than 20 runners, we don't lay
> any open bets (tote
> win/place/exacta/swinger/trifecta/quartet etc.).
>
> The reason for this is that the tote couples every
> runner over the number 20 as runner number 20.
> Therefore horses 21, 22, 23, 24 - should any of
> these run in the top 4, that number will be
> replaced by 20. So if 22 wins the race, 20 is
> shown as the runner on the tote.
>
> We can only result the race with the order the
> actual carded horses finished in. We cannot
> result it with what the tote publishes. If two or
> three horses over the number 20 finish in the top
> 4, then the result the tote publishes does not
> reflect the actual finishing positions of the
> horses. They can only put 20 once, and then they
> take the horse number following the next runner
> over 20.
>
> So if the actual results was: 21, 16, 23, 4, 7, 8
>
> The tote would publish: 20, 16, 4, 7
>
> This is the reason why we haven't laid the tote
> bets for this race.
>
> However it has sparked an idea from my side, and
> we will be investigating a way to offer tote bets
> on these races with more than 20 runners.
do share your sparked idea with the rest of us.
> With regards to Doncaster Race 4, we did not lay
> quartets as there were more than 20 runners in
> that race.
>
> When there are more than 20 runners, we don't lay
> any open bets (tote
> win/place/exacta/swinger/trifecta/quartet etc.).
>
> The reason for this is that the tote couples every
> runner over the number 20 as runner number 20.
> Therefore horses 21, 22, 23, 24 - should any of
> these run in the top 4, that number will be
> replaced by 20. So if 22 wins the race, 20 is
> shown as the runner on the tote.
>
> We can only result the race with the order the
> actual carded horses finished in. We cannot
> result it with what the tote publishes. If two or
> three horses over the number 20 finish in the top
> 4, then the result the tote publishes does not
> reflect the actual finishing positions of the
> horses. They can only put 20 once, and then they
> take the horse number following the next runner
> over 20.
>
> So if the actual results was: 21, 16, 23, 4, 7, 8
>
> The tote would publish: 20, 16, 4, 7
>
> This is the reason why we haven't laid the tote
> bets for this race.
>
> However it has sparked an idea from my side, and
> we will be investigating a way to offer tote bets
> on these races with more than 20 runners.
do share your sparked idea with the rest of us.
Please Log in or Create an account to join the conversation.
- naresh
-
- Platinum Member
-
- Posts: 6390
- Thanks: 1499
Re: Re: Bet type not available(td)
11 years 8 months ago
True to his words tote bets are available with 20 or more runners now. Thanks Dev
-D

Please Log in or Create an account to join the conversation.
- johnnycomelately
-
Topic Author
- Platinum Member
-
- Posts: 3211
- Thanks: 295
Re: Re: Bet type not available(td)
11 years 8 months ago
naresh Wrote:
> True to his words tote bets are available with 20
> or more runners now. Thanks Dev
-D
Great news(tu)
> True to his words tote bets are available with 20
> or more runners now. Thanks Dev

Great news(tu)
Please Log in or Create an account to join the conversation.
- smashley
-
- New Member
-
- Thanks: 0
Re: Re: Bet type not available(td)
11 years 8 months ago
Calling Dev. I assumed all races with over 20 runners now were now available for tote betting with hollywood. Can you implement this facility for Cork Race : 6 later on today?
Please Log in or Create an account to join the conversation.
Time to create page: 0.096 seconds