Jump to content


Established Member
  • Posts

  • Joined

  • Last visited

  • Days Won


beerguy55 last won the day on May 3

beerguy55 had the most liked content!

More information about you

  • How did you hear about Umpire-Empire?
    Search Engine (Google, Yahoo, Bing, ...)

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

beerguy55's Achievements




Community Answers

  1. 30 seconds is an eternity for a bat boy to come over, even from the opposite dugout, to get the gear - either when the triple ended, or the very next play after the run scores. You think 30 seconds is fast? Stand outside in -40 for 30 seconds. Hold onto a one-goal lead in hockey for 30 seconds. Or the next time you're driving when the light turns green, wait for 30 seconds before you leave. You'll see how long 30 seconds really is. Football teams call plays, have huddles and substitute players in under 40 seconds, sometimes even running out a punting or placekicking unit. It's forever. Pockets, under back of shirt, use your other hand, etc. These are very minor obstacles and problems that anyone with two brain cells to rub together can solve. I simply go back to the lifetime you have for the bat boy to come get the gear from you. As far as signals to the batter/runners - I can do the most complicated signals with one arm tied behind my back. If their signals are so complex that they can't have an amputee coaching, the problem is the coach, not the lack of an arm. If a coach can't figure this out he's either short on cognition, or awfully lazy.
  2. I have two answers - one as a coach and one as a half-assed interpreter of rules. From a rules basis, I would say it's nothing until it's something. If the player successfully crosses home plate and there is indeed no play, then it's nothing. If something happens with the gear he's carrying to impact the play, especially if he drops something, it might be something. As a coach, this is one of the most patently stupid things a coach could do. Not only to distract his own player, in the middle of a live play...to open the potential of something like the kid dropping the elbow bad, and then tripping on it...but what kind of message do you think you're setting for your players? If you're too F*#King lazy to trot this over to the dugout after the play, or hold onto it for a few more minutes, then call the batter who just got out over...or another player...or just wait until the inning is over you asshole.
  3. This, like anything else is a "judgment" call. Just like those times where you didn't see a tag...it doesn't matter if everyone else in the park saw the tag, your judgment stands. You don't have to change any rules...if you didn't hear him swear you didn't hear him swear.
  4. To add to the correct answer above, the runner can be tagged at any point before he gets back to first - including while he is on third base, or while he is on second base, on his way back to first. Now, practically speaking, if F4 is standing on second base with the ball, and R1 is still between second and third, he's going to have a hard time getting back to first. If he decides to take a shortcut across the infield, now you can appeal the runner missing second base by tagging second base.
  5. No, but it doesn't really matter. MLB doesn't have pitch count restrictions. The only reason MLB coaches track pitches is to track the stamina of their player...so it would be pretty pointless to add four pitches for a no-pitch IBB. An intentionally walked batter is, however, counted for the 3-batter minimum.
  6. How fast people are is relevant in determining where R2/R3 were at TOI. As described, R2 and R3 likely reached their next bases before R1 reached his next base (and interfered with F6). My "judgment" is likely that they did not, and unless we're playing under replay review rules, that's how it stands.
  7. The way I try to explain it to younger players and coaches (and their parents) is "force" is NOT how you put the runner out...it is a status placed on the runner. As stated above, the runner on second is forced, because the runner on first is forced, because the batter is now a runner. If the batter or R1 is put out, then R2 is no longer forced. Otherwise, if R2 is put out in ANY method while he is forced, it is a force play.
  8. It's no different than a banger - is he 2'10" away or 3'2"? Arguing it is pointless and it should really not happen. Ump saw likely what I saw...starting on dirt on fair side of running lane, and ended on left chalk of running lane. it's his judgment and outside official replay review (this one is not reviewable) his judgment is right...always. Argue egregious misses not 50/50 calls. If your argument is it needs to be more "obvious"...fine, argue it. U1 felt it was obvious, and he made his call "big" to illustrate it.
  9. This isn't batter's interference. He's not a batter anymore. This is about the bat, not the batter.
  10. Or just be really good. I was once picked off at third base by a catcher who threw the ball between the batter's arms, bat and head (a space not much bigger than the ball) - I literally watched the ball come out of that chute, go directly past my eyes, and into the third baseman's glove for the third out. Still standing there with a stupid look on my face, not yet understanding what happened, as the defense left the field.
  11. So, what if he said forking, farging (Johnny Dangerously, anyone?), fricking or frigging? I get it, there's a rule about indecent language, and it needs to be enforced - not poking at you, but the system...and I wonder what leeway of judgment you get to have. I'm just wondering when we are going to stop pretending that the f word is so dangerous, and that those 8/9 year old kids aren't firing f-bombs at each other all day long. If someone says "shut the front door" to you, are you ignoring it? Is subtext allowed? See You Next Tuesday.
  12. beerguy55

    Bat Flips

    I've said it before and I'll say it again - I don't give a SH*# if you think a bat flip is unsportsmanlike...safety is the issue, not whether or not it's nice. Bat Flip Gone Wrong
  13. If it doesn't end an inning or game it doesn't matter, for the purposes of "does the run score?" And in OBR, on a game-ending walk only BR and R3 have to touch, so order doesn't matter. I would love to see a bases loaded walk in the third inning where R1 and R2 refuse to advance...and would further love to see what happens if R1 is called out first. Is this even an appeal play, or is this an umpire instruction play? So, give me your answers for these scenarios - in all cases R1 is forced at time of miss. In all cases R1 will be the third out, so it will matter to whether or not R3's run counts. (ie. if the force is removed, the run counts as R3 scored before third out) Is the force removed in all four scenarios? If not, which ones? I'm also considering continuous action, and live activity after the play is finished - after all runners have stopped trying to advance - to be the same (ie. the ball was never made dead). If they are different for the purposes of these rulings, let me know. 1. B/R and R1 both miss their forced bases - after live action, B/R is appealed, then R1. Yes 2. B/R and R1 both miss their forced bases - during live action B/R is appealed, then R1. 3. B/R and R1 both miss their forced bases - during live action B/R is appealed, R1 is appealed after live action. 4. Hit and run, R1 rounds and misses second & B/R is thrown out before reaching first; R1 advances to third on the throw. R1 then appealed. Does it matter whether any or all of the appeals are made during continuous action, during live action after the play, during a dead ball (FED), or after play is live again? It may be a corner play for consecutive appeals, but not sure about the "following live action" part, but would like to know your insight. Now, what are your answers with these slight changes - order of outs/appeals the same, R1 still misses second: 1. BR misses second base, not first 2. BR misses second base, not first 3. BR misses second base, not first 4. BR touches and rounds first, and is subsequently thrown out Because right now, unless I'm misunderstanding something, I'm now seeing three assertions here about when the force is removed: You - WUM is correct, except for consecutive appeals, which must be done in proper order? TomUIC - WUM is correct, except when following runner is put out while forced, whether "naturally" or by appeal (yes to first four, no to second four)? Me - WUM is incorrect, following runner being put out always removes force (yes to all eight) - my caveat here is, if WUM is correct, then it's 'no' to all eight....ie. either "time of miss" always dictates the force or "following runner out first" does
  14. Not exactly. The scenario talks about the players "missing" or "never having arrived" to their forced bases, but the section is meant to address both game ending AND inning ending scenarios (and R1/R2 wouldn't walk off the field to celebrate the end of the inning - unless you really want to get into inning-based run limits) - the section concludes with a very definitive statement that appeals on game-ending AND inning-ending force situations must be done in the proper order, in order to keep the force alive. Again, it's just an example scenario (in fact, the section starts with "Let's say") - it is meant to be illustrative, not exclusive. I'm speculating this example is used simply to build on the example in scenario 2. But all other language in the section makes it pretty clear that it would also apply if R2/R3 simply missed their forced bases, which would be a more likely and relevant scenario for an inning-ending situation. I would also posit that the scenario presented is more likely than TWO players simply missing their forced base at the same time. The section very clearly says that if the following runner is put out first, the force on the preceding runner is negated (directly contradicting WUM)...what it does NOT say is that it is conditional on the following runner being forced when they are put out. The bottom line is one of these two positions is wrong.
  • Create New...