Got to love the inflexibility of TABCORP.
Latest 'feature' is greyhound betting on New Zealand meetings on Monday and Wednesday.
The meetings on these days at Manawatu and Hatrick have 15 races. The NZ TAB offers betting on the 15 races.
Due to (and I am speculating here) limitations to the TABCORP technology - a maximum of 12 races can be schedulted for any meeting / anywhere (as well as a max of 24 runners but that is a different story).
So in their wisdom, they create a dummy meeting called New Zealand with 5 races, which are actually races 10-15 in the NZ meeting, with the actual meeting in Australia set at 10 races. Now if you are a 50c punter, as I think most TAB execs think most putners are, this is no problem - you fill out a ticket or tick some boxes on an app and away you go.
For the sophisticated punter using software - who probably contributes the majority of betting t/o - we have undertake programming contortions to get a bet on these meets on Monday and Wednesday. The situation for NZ putners betting into TAB is even worse as they attempt to decipher the mess dumped on them by TAB.
FWIW - I cannot find any explanations for why this started in the past month and how long it will last.
Never have enough crazy things to fix up.
Mate when you say "the sophisticated punter using software" can I ask for more detail?
Are you talking about someone who is writing their own programs using an API? Or are we talking about some "off the shelf" stuff that the user would typically have paid a lot for and would have to read the manual to know what to do.
From where I sit I am intrigued as to why this would be a problem. For the TAB punters there were two NZ greyhound meetings yesterday morning. One was coded YG and had 10 races and the other JG and had 5 races.
Surely any software would have to receive some input before the day started. And typically it would be meeting codes and race numbers for that upcoming day.
If you explain it a bit further something that isn't obvious on my first read might come to light