Re: Another pick-rule question



On Jun 21, 12:23 pm, Flo <Flo.Pfen...@xxxxxxxxxxxxxx> wrote:
The shift from the 10th, essentially, is that the 10th said to stop as
soon as you hear the call (unless the shot is in progress)

no, this is what WFDF says. The 10th said to the offense "continue
playing if the thrower might be in the process of deciding to throw it
to you and not be able to hold back, as stopping would risk a turn
over. But don't start any new cuts. Echo the call." It told the
defense "keep on playing defense, do not echo the call, maybe the
thrower will throw it and you get a free shot at a d."

Ok, yes, I was thinking of just the offense, as always.

while the
11th says to stop as soon as the thrower hears the call.

The 11th says to the offense "continue playing if you think you will
be easy to throw to and you are not anywhere near the pick. Also
continue playing if the thrower might be in the process of deciding to
throw it to you and not be able to hold back, as stopping would risk a
turn over. But don't start any new cuts anywhere near the picked
player. Echo the call." It tells the defense "keep on playing defense,
maybe the thrower will throw it. Echo the call."

So, you are agreeing that a cutter is encouraged to make a new cut
just as long as the picked player would not have had a play on the
disc.

And the 11th tells players to echo the call only if the particulars
favor their team. A beat defender (away from the play) will want to
echo the call, a cutter with an opening will not. (Both sets of rules
say (in Etiquette) that all players should echo calls.)

Anyway, what this tells me is to continue cutting so as to lessen the
chance that we'll turn it over, even if he is not currently trying to
throw it to me, especially if it's at stall 6 or higher. In that
case, there is a good chance that the thrower will throw it in the
next few seconds before he acknowledges the call, and I would rather
present him with a good target.

The 10th is somewhere in between WFDF and the 11th, but giving all the
advantage of continuation to the defense (not talking about
continuation on calls during the throw). Since the players wanted
continuation when it was introduced in the 90s, we chose the balanced
version with more continuation of the 11th over the balanced WFDF
version with less continuation and the unbalanced version in the
10th.

Anyway, my main objection is that in the majority of cases, a
completion counts when (according to me and therefore to any rational
person) it shouldn't because play should have stopped already but the
rules as they're written say to keep on playing.

.



Relevant Pages

  • Re: Another pick-rule question
    ... echo the call and continue playing until the thrower ... I think the thrower acknowledgment was in the 10th, ...
    (rec.sport.disc)
  • Re: New pick rules with 11th edition
    ... Well that's cheating, and the rules are written with the assumption ... they can rule to bring it back if they believe the thrower knew there ... should hand out a TMF to the offense (yellow card if anyone is still ... creates a situation where you simply don't stop playing on a call. ...
    (rec.sport.disc)
  • Re: Another pick-rule question
    ... playing if the thrower might be in the process of deciding to throw it ... defense "keep on playing defense, do not echo the call, maybe the ... The 10th is somewhere in between WFDF and the 11th, ... continuation on calls during the throw). ...
    (rec.sport.disc)
  • OT: preprocessing a mp3 file for playing in high noise environment.
    ... Preprocessing a mp2 or mp3 file for playing in high noise environment. ... It accepts a mp3 audio file, and first decodes it to wave, ... echo "Getting max amplitude." ... echo "Deleting temp file." ...
    (sci.electronics.design)
  • Cont. FP 2002 & Discussion Form
    ... This is a continuation of an earlier post that I reported as resolved but is ... I used FP 2002 to build a discussion forum (mostly playing around) and so ... minor modification to make this work, but I don't want to give everyone on ...
    (microsoft.public.frontpage.client)

Loading