ricka56

Another technique is to use the umpire clock in your head (developed with experience). Back up to lessen the angle between where the ball is and 3B. The umpire clock in your head knows when the ball is going to reach the ground/fielder. Glance back/forth, then watch R3 until right before the clock says the ball will arrive, then turn to watch (and stay with) the catch/no-catch. If R3 hadn't left before you turn your attention to the ball, then he hadn't left early enough to uphold a tag-up appeal. I wouldn't suggest using this technique if F/F is in question because you may need to see the ball longer to decide F/F. You don't want to miss the critical time when the ball reaches the field(ers). With 2-man, this situation is tough on the crew. It is a topic in my pre-game. Whichever way you want to cover it, talk about it pregame (refer to my signature line).

I pregame this and have the BU stay with the catch/no-catch while the PU looks for the tag-up. BU doesn't have much to do and staying with the trouble ball and freeing up PU to take a peak at 3B makes sense to me.

But what if you enforce the illegal bat out (BOO not yet discovered), then before the next pitch, the defense appeals BOO.

This one is from the FB umpire page. Kind of a TWP, but maybe a good exercise on competing rule applications. Batter with a 1-1 count less than 2 outs is found to be batting out of order with an illegal bat. How do you rule. ? If you rule the batter out for an illegal bat, his AB has ended and the BOO is viable and can be enforced ... 2 outs. But we never get 2 outs on a BOO. Would you get the two outs or could you justify (by rule) to get only one out. And if so, who's out. Please justify your ruling.

PU is supposed to have fair/foul, catch/no-catch and the tag-up. But this sounds like a trouble ball. I was taught that all umpire eyes watch the trouble ball (probability of $#!+ happening near the trouble ball is much greater than BR missing 1B). So, if I am BU, I am staying with the catch/no-catch.

I have no problem with what you did. The spirit of the balk rules is to prevent cheating. If F1 doesn't have the capability to deceive a runner (legally or otherwise), then let the boys play out the game. BTW, no explanation is needed...everyone knows what's going on. How much slack from this point forward is a constant game management judgement call.

I ask Jobu to come ... take away bad timing. I offer him cigar and rum ... he will come.

Does a batter usually fall across HP during a swing ? not in my experience. Does a batter fall across HP much more often when R1 is stealing ? yes, in my experience. F2 may have seemed unaffected by batter's presence, but you can't know how much better a play he could have made absent the cheating batter. I penalize this behavior and get BI more often than not. And I'd rather deal with OHC than DHC (one of them is going to challenge your call). That said, if there is no interference, there is no interference (i.e. a pitch out where B was nowhere near F2).

I'll answer this question...even if asked/answered across the field No ejection required. What is required is no response, none. Your plead to not argue is diminished by your arguing back and wanting the last word on the matter. He didn't ask another question. No response is needed. Keep quiet and watch for him to do/say something stupid.

I learned it on a rugby pitch, so probably.

We umpire the game...we don't keep the score...though if put to a vote, I'd vote end the game 10-0. But this is not up for a vote. This is between the teams and the score keeper. Not My Circus, Not My Monkeys

This explanation alone shouldn't result in a ball call (perhaps you inadvertently left something out). I have kept the batter in the box and called ball on such a play when the batter moved/leaned into the path of the ball not in the strike zone when the pitch would not have hit him absent of him moving into the pitch.

... because you know that the other team is going to be want you to do something about it.

Can't fix stupid nor lazy. Do your job, and pray he doesn't put you in a jackpot. Personally, I drink (editted...I mean after the game). Bet your assigner knows all about his laziness. He needed a warm body and it was your turn to suffer. Beimid ag ól!.

My wife so wishes she hadn't either.

https://en.wiktionary.org/wiki/have_a_bone_in_one's_leg https://en.wiktionary.org/wiki/fatuous

oh, you poor bastid...and you finished them all ? ...you stud.

But this highlights a good reason for verbalizing the ball call. F2 doesn't need to take the risk of throwing the ball away if it is ball-4 (and he can't be waiting for my slow-ass strike mechanic). Personally I think that this R1 stealing, ball-4 call should be loud enough for everyone in the ballpark to know the status of the runners. Players shouldn't have to wait for the non-verbalized ball wait time to know the status of the play.

I think the OP's question was (I'm sure I'll be corrected if not), what is the BU to do if he doesn't know whether R1 is entitled to 2B on ball-4. Should R1/R2 be somehow protected from PU's ambiguous ball non-mechanics.

If the ball call was loud enough for the dugout to hear, how would BU not ? And what is your point ? My point was that knowing whether it was ball-4 or strike x was immaterial.

Wow ...that would have had me . Would like to see his pick off move to 2B, and his disengagement. If pitching doesn't work out for him, maybe he can find work with Cirque du Soleil.

Dunno what BU could do, other than watch what happens at 2B. I have had no-ball vocalizing PU and on a 3-x count, with R1 stealing, the throw comes down to 2B and I have no idea if partner has gotten a strike or ball 4. And even if I knew that it was ball-4, I'm not saying anything to anyone. I'm watching what happens. Alternate scenario, R1 slides past 2B without touching it : if R1/R2 takes off for 3B, you have to wait for the missed base appeal. if R1/R2 is obstructed going back to 2B by F6, then you have obstruction. Probably award 3B.

I once had a bone in my leg...gutted it out the last 4 innings.

It could be worse... At least you're not in Cleveland...or Detroit