Depends on exactly what you mean by "so rare". IMO, making an unintended shot actually happens quite often, even at the pro level.It's so rare, at the pro level, that a player makes the intended object ball in a non-intended pocket.
Depends on exactly what you mean by "so rare". IMO, making an unintended shot actually happens quite often, even at the pro level.It's so rare, at the pro level, that a player makes the intended object ball in a non-intended pocket.
Or...Having thought about it some more, an instance where there could still be controversy/confusion are shots where the OB is frozen on the rail, or very close to touching the rail. If the CB contacts the rail first (which is almost always the case when pocketing a ball frozen to the rail), then technically the shot wouldn't be obvious based on the proposed criteria.
Therefore, the most practical solution is simply to call all shots where there is a chance the CB touches the rail before the OB. In other words, call all shots where the OB touches the rail or is very close to it.
First thing they should do is get rid of the term "call shot" and replace it with "call pocket".
I would also add that the ob has to be clear to the pocket. If you have another ball near the pocket, that could be used as a combo even though your object ball also can go without the combo, then you should call which ball you intend to make.
Depends on exactly what you mean by "so rare". IMO, making an unintended shot actually happens quite often, even at the pro level.
I thought that the call-shot rules for 10 ball originated in 2008. When was the tournament you're thinking of?Call shot 10 ball actually originated in Philippines during the time of world 10 ball championships. ....
I thought that the call-shot rules for 10 ball originated in 2008. When was the tournament you're thinking of?
This is a pretty decent compromise for rotation games. In other words, calling a ball is only required if you're planning to pocket a ball that isn't the lowest ball on the table.I also recently played in a 9 ball tournament, where it was call ball, except it was assumed you were calling the lowest ball, which meant you rarely actually called anything. In other words, you only needed to call combinations, or billiards. Caroms, where the ob is made after caroming off another ball, were not necessary to be called, because if you were playing the combination, you would have had to call that. It eliminated much of the luck, especially in reply safeties. However, it was still possible that a player might have shot at the lowest ball, missed, and had it go a few rails into another pocket. I never saw that happen, but it's possible. More importantly, there weren't any complaints or disagreements, which is really nice in a tournament without referees.
But they are NOT clear. Nowhere does it define what an "obvious" shot means.No need to change any rules here, they are clear.
And if there is no referee? It becomes one player's definition of "obvious" versus the other player's definition.It is up to the referee's judgement to ask for a call before the shot is made, if he's not sure about the shot. The opponent has the right to ask for a call as well, again before the shot is made.
It does no such thing.To add the criteria suggested in this thread would contradict the existing rules where shot elements are irrelevant...
Nowhere in this thread have I proposed "calling every detail of the shot". I'm simply defining unambiguously what an "obvious" shot means. That is all. The rest of the rules remain the same.There's also one more thing about not calling every detail of the shot...
Why would there be an argument? If it's part of the rules and the rules are written completely unambiguously, then it's simply a matter of following the rules.Could you just imagine two guys yelling at each other because the shot only satisfied 2 out of 3 on the "obvious checklist"?
Are you an engineer or software developer by chance? This is the same logic that is applied when talking about fixing software problems and it completely ignores the human element. In our case, the human element is that no one remembers all the WPA rules even though we can access them on our phones. There will most definitely be arguments.Why would there be an argument? If it's part of the rules and the rules are written completely unambiguously, then it's simply a matter of following the rules.
With the rules as they are now, I can definitely imagine two guys yelling at each other and arguing whether a shot is "obvious" or not.
What do you have against the American Rotation Rules? I'm essentially proposing the same thing that has already been written down by the American Billiard Club (of which I was initially unaware). The criteria that I proposed simply determines for you whether a shot involves "a bank, kick, kiss, carom, or combination", whereas in the AR rules it is assumed that you know what "a bank, kick, kiss, carom, or combination" means.
... What do you have against the American Rotation Rules? ...
"But they are NOT clear. Nowhere does it define what an "obvious" shot means."
Rules ARE clear, an obvious shot is the one that satisfies the referee's judgement as such.
"And if there is no referee? It becomes one player's definition of "obvious" versus the other player's definition."
The opponent has the right to ask for a call, BEFORE the shot is played. He has also the right to ask for a call when a referee is present, mainly if he feels the referee is not applying the rules properly. Also implied by the rules, remains in referee's judgment if this right is exercized properly.
"It does no such thing."
Yes it does, any discussion on any shot elements in any way does bring them into the equation.
"Nowhere in this thread have I proposed "calling every detail of the shot". I'm simply defining unambiguously what an "obvious" shot means. That is all. The rest of the rules remain the same."
Again, adding criteria to define "obvious" shots does bring shot elements into discussion, and again, rules define properly what an obvious shot is like explained above.
Rules are FINE, what is not fine is they are not applied properly, thus leading to loss of competitive rhythm even in pro level and unclassy loss of frames.
But they are NOT clear. Nowhere does it define what an "obvious" shot means.
And if there is no referee? It becomes one player's definition of "obvious" versus the other player's definition.
It does no such thing.
Nowhere in this thread have I proposed "calling every detail of the shot". I'm simply defining unambiguously what an "obvious" shot means. That is all. The rest of the rules remain the same.
And for that particular shot, it's a shot that is fluked in. The current rules award that particular lucky scenario. My proposed rules do not (only if the shot isn't called).
I think you may have misunderstood what I proposed. I'm not saying we have to call every "kiss and tick" or how many rails, etc. To call a shot, you still only have to call the ball and the pocket. That is wrong.
Going back to Bob's 8-signma example, if that shot was called (meaning only the ball and pocket were designated), then the fluked in shot would be a legal shot. It only becomes an 'illegal' shot if the shot wasn't called, because the shot would not longer be considered "obvious" based on the criteria.
I think most of the responses in this thread are missing the salient difference between "call pocket", which is what the rule is discussing, and "call shot", which is how many of y'all are characterizing it.
Call pocket (indicate the ball to be made and the intended pocket) only requires that you call a ball and a pocket.
Call shot, i.e., call the rails, caroms, combos, rattles, wind gusts, tectonic forces, etc., isn't the rule in any tournaments.
If your object ball is all by itself, then you don't have to call the ball. If you're shooting it straight into a pocket, then you don't have to call the pocket. If either of those aren't true, then clarify what you're doing before you do it. Simple.
If you call a straight-in shot, and you rattle, go four rails, and drop in the same pocket, then... the intended ball went into the intended pocket. Shot made, keep shooting. It's really not that complicated.
Yes, I'm engineer. I guess it's the engineer in me that has a revulsion towards ambiguity. Imagine a civil engineer being asked to build a bridge that would support "heavy loads". Uh, okay.Are you an engineer or software developer by chance?
That's the reason why laws are written down, as detailed and unambiguously as possible. Does it matter that the average citizen hasn't memorized all their state's laws? No, we would rather just have them all clearly written down somewhere when disputes arise.This is the same logic that is applied when talking about fixing software problems and it completely ignores the human element. In our case, the human element is that no one remembers all the WPA rules even though we can access them on our phones. There will most definitely be arguments.
I can deal with the criticism that the 3-point criteria is "wordy" compared to Joe Tucker's. But it's essentially the same thing.I don't have anything in particular against those rules. I believe, however, that it is a solution looking for a problem. At least Joe Tucker expresses it simply. Your 3-point criteria is unnecessarily wordy.