krupicka
Double Eagle Member
Exactly. When I raised that point at the rules update, some didn't see as requiring a rethrow to be a "penalty" as it didn't cost any strokes.
Discover new ways to elevate your game with the updated DGCourseReview app!
It's entirely free and enhanced with features shaped by user feedback to ensure your best experience on the course. (App Store or Google Play)
But also, krup's opinion of whether or not he thinks i should be stepping thru from any distance is an not needed, or wanted. Just answer the question, imo, no reason to be a douche about it
I've been saying this since day one. Mostly I've been told that it's a hypothetical scenario. Considering the other hypothetical scenario of calling a stance violation on one self, "required" a rule change, so you couldn't call or second violations on yourself, eliminating the need for a second partly circumvented that change.The more important point is that the rules now allow a warning to be given without being seconded---and that stance warnings come with a penalty (throw doesn't count). It's open for abuse by a single player, who doesn't have to be right about the stance violation---just willing to call it.
Off on the wildly unlikely hypothetical, but if I'm in your group and you ace a hole, can I call a footfault---completely without merit---and invalidate the ace?
Sure, I'll probably get beat to a pulp, and on appeal to the TD be overturned on the simple grounds that I was being a jerk. But, in the meantime, isn't the actual wording of the rule on my side?
Off on the wildly unlikely hypothetical, but if I'm in your group and you ace a hole, can I call a footfault---completely without merit---and invalidate the ace?
Sure, I'll probably get beat to a pulp, and on appeal to the TD be overturned on the simple grounds that I was being a jerk. But, in the meantime, isn't the actual wording of the rule on my side?
If you call me on a foot fault after my disc is in the basket, I'm going to tell you that you did not call it promptly and ignore your call.
Sorry, buddy, you don't have that right; and, unless and until the PDGA restores a time limit, you don't even have that option.
I disagree. Furthermore I would say you don't have the right to wait to see the outcome of my shot before you decide whether or not to call a foot fault. I don't see a valid reason why something like that wouldn't be called immediately, but I definitely see how it could be abused if it's not. Ask yourself whats more fair in that situation. That's why those two sentences are in the rule book. It states explicitly that if you see a foot fault you must call it, and that you must call it promptly. There is no decision to make about whether or not you want to/should call it, and you can't wait and see what happens before you call it.
But you ABSOLUTELY DO NOT have the right to simply ignore a validly made call, even if you think the call is bogus.
I agree completely. In fact, that's the point. If you wait to see the outcome of my shot before you decide whether or not to make a call then it is not a validly made call.
I agree completely. In fact, that's the point. If you wait to see the outcome of my shot before you decide whether or not to make a call then it is not a validly made call.
A VALIDLY MADE call is a call made following the prescribed procedure for making the call. In the case of a stance violation, the technical procedure is simply that someone makes a stance violation call in the first instance of a stance violation, and that the call is made and seconded for subsequent violations.
Clearly, you did't bother attempting to read and comprehend David Saul's post.
A VALIDLY MADE call is a call that conforms to the specified procedure for making a call, without regard to whether the call is correct or erroneous.
A VALID CALL is a call that meets all the specified criteria to be enforceable.
You can dispute whether the call is VALID, but unless you can demonstrate that the MANNER IN WHICH the person made the call did not follow the prescribed procedure, the call is validly made.
There is NOTHING in the rule that requires a call be made within a specified time period to be considered valid. Given that the 2013 rules revision specifically REMOVED the previously existing 3 second time limit from the validating criteria and that the Rules Committee has refused to define or otherwise specify a time- or event-based limit of any sort on what constitutes "promptly," you have neither the right nor the freedom to employ an artificial, time-based criterion such as "knowing the outcome of a throw" as an excuse to ignore a call.
The player has a 10' putt but his lie is on an extreme down slope. He cans it, but he's off balance, arms flailing ... and he falls forward.
A VALIDLY MADE call is a call made following the prescribed procedure for making the call. In the case of a stance violation, the technical procedure is simply that someone makes a stance violation call in the first instance of a stance violation, and that the call is made and seconded for subsequent violations.
Clearly, you did't bother attempting to read and comprehend David Saul's post.
A VALIDLY MADE call is a call that conforms to the specified procedure for making a call, without regard to whether the call is correct or erroneous.
A VALID CALL is a call that meets all the specified criteria to be enforceable.
You can dispute whether the call is VALID, but unless you can demonstrate that the MANNER IN WHICH the person made the call did not follow the prescribed procedure, the call is validly made.
There is NOTHING in the rule that requires a call be made within a specified time period to be considered valid. Given that the 2013 rules revision specifically REMOVED the previously existing 3 second time limit from the validating criteria and that the Rules Committee has refused to define or otherwise specify a time- or event-based limit of any sort on what constitutes "promptly," you have neither the right nor the freedom to employ an artificial, time-based criterion such as "knowing the outcome of a throw" as an excuse to ignore a call.
Then why include the word promptly at all? Removing the three second time limit makes perfect sense because no one is standing there with a stop watch after every throw and there's no sense in trying to enforce a very specific time limit when realistically there is no accurate way for that time limit to be measured or enforced. Thus they simply say that a call must be made 'promptly'. Now that is open to interpretation, and until the PDGA decides to define it more specifically I choose to interpret that as meaning a fault must be called as soon as it is identified as being a fault. By definition if you wait to see the outcome of a throw you have not called it as soon as you identified it as being a fault. 801.01a :"If any point in dispute is not covered by the rules, the decision shall be made in accordance with fairness." I believe this is the fairest interpretation of what a 'prompt' call is.
Too be fair the specific example that started this conversation was as tee shot and I can see how the timing might be less easy to parse on a putt near the circles edge. Also please keep in mind my response was in reaction to the hypothetical situation of someone intentionally calling a foot fault that didn't occur on an ace after it went in in order to abuse the rules. I stand by my assertion that the best way to handle that would be to tell them they didn't call it promptly and ignore it. If they want to appeal that to the TD they are free to but it just makes them look like a D-bag. I also am not advocating using this as an excuse to subvert correct calls. If I am called on a foot fault that was in fact a foot fault I'm not going to give anybody a hard time about exactly when it was called. But if someone is trying to abuse the rules to gain an advantage, different story.