Sliding Errors - CPU Runners cost runs.

Collapse

Recommended Videos

Collapse
X
 
  • Time
  • Show
Clear All
new posts
  • cwilli28
    Rookie
    • Jun 2010
    • 11

    #1

    Sliding Errors - CPU Runners cost runs.

    Since the last update, I noticed this error in CPU controlled baserunning, when I'm on offense. I use assist on baserunning fyi. The CPU will force players to slide into 2nd and 3rd base on groundballs regardless of where they're hit. This is a problem on hit and runs, or ground balls through the middle, trying to get a score a runner from 2nd.

    Here was a recent frustrating situation that happened to help illustrate my point.

    - Top of 3rd. The score is 1-0. In Diamond Dynasty
    - Runner on second (Starling Marte 95 speed)
    - Runners moving on contact, don't run into an out.
    - Ground ball pulled hard down first base line.
    - Take control of Runner on 2nd, send home. (Batter told go to 1st)
    - First baseman dives, gets glove on it, pops out of glove.
    - Batter is going to be safe at 1st.
    - Runner was sent home but slid into 3rd. Slowed all momentum home.
    - 1st basemen able to get to ball and throw home.
    - Play at plate, runner is out.

    I've played, coached and watched baseball most of my life, but correct me if I'm wrong. There is absolutely no reason to slide into 3rd, with 2 outs, and ground ball hit right side of the infield. There would never be a play at 3rd, as a fielder, with no forceout at 3rd, and 2 outs, your play is at 1st. As a runner, you're running on contact on any ball behind you. I always send the runner home, because if there is an overthrow, the runner is easily safe. If the runner is out at 1st, it doesn't matter.

    This isn't an isolated incident either. I use a quick top of the lineup, Dee Gordon (98) Jean Segura (86?) and Marte (95) I like to hit and run, and steal bases (don't get me started on CPU pitchouts). With directional hitting, you can aim to hit behind runners, if executed properly, your runners can go 1st to 3rd easily. But, the CPU forces the runner to slide into second if its a ground ball, essentially negating the hit and run.

    And the last instance I've noticed is ball hit up the middle, with runner on second. On a ball that splits the SS 2B, rolling towards the CF, early in the game, I will opt to have my runner go 2nd to home, maybe get an early run. But, this 'groundball' issue forces any runner to slide into 3rd, cancelling any chance of going 2nd to home. Forcing you go station to station. Vasgersian even says, "looks like they're trying to turn this into a big inning", just to rub it in.

    I've searched through the forum and haven't seen anyone posting about this, so I hope this isn't a repeat, or even worse, something that only happens to me.
  • squashbuggie
    Banned
    • Dec 2016
    • 371

    #2
    Re: Sliding Errors - CPU Runners cost runs.

    Originally posted by cwilli28
    Since the last update, I noticed this error in CPU controlled baserunning, when I'm on offense. I use assist on baserunning fyi. The CPU will force players to slide into 2nd and 3rd base on groundballs regardless of where they're hit. This is a problem on hit and runs, or ground balls through the middle, trying to get a score a runner from 2nd.

    Here was a recent frustrating situation that happened to help illustrate my point.

    - Top of 3rd. The score is 1-0. In Diamond Dynasty
    - Runner on second (Starling Marte 95 speed)
    - Runners moving on contact, don't run into an out.
    - Ground ball pulled hard down first base line.
    - Take control of Runner on 2nd, send home. (Batter told go to 1st)
    - First baseman dives, gets glove on it, pops out of glove.
    - Batter is going to be safe at 1st.
    - Runner was sent home but slid into 3rd. Slowed all momentum home.
    - 1st basemen able to get to ball and throw home.
    - Play at plate, runner is out.

    I've played, coached and watched baseball most of my life, but correct me if I'm wrong. There is absolutely no reason to slide into 3rd, with 2 outs, and ground ball hit right side of the infield. There would never be a play at 3rd, as a fielder, with no forceout at 3rd, and 2 outs, your play is at 1st. As a runner, you're running on contact on any ball behind you. I always send the runner home, because if there is an overthrow, the runner is easily safe. If the runner is out at 1st, it doesn't matter.

    This isn't an isolated incident either. I use a quick top of the lineup, Dee Gordon (98) Jean Segura (86?) and Marte (95) I like to hit and run, and steal bases (don't get me started on CPU pitchouts). With directional hitting, you can aim to hit behind runners, if executed properly, your runners can go 1st to 3rd easily. But, the CPU forces the runner to slide into second if its a ground ball, essentially negating the hit and run.

    And the last instance I've noticed is ball hit up the middle, with runner on second. On a ball that splits the SS 2B, rolling towards the CF, early in the game, I will opt to have my runner go 2nd to home, maybe get an early run. But, this 'groundball' issue forces any runner to slide into 3rd, cancelling any chance of going 2nd to home. Forcing you go station to station. Vasgersian even says, "looks like they're trying to turn this into a big inning", just to rub it in.

    I've searched through the forum and haven't seen anyone posting about this, so I hope this isn't a repeat, or even worse, something that only happens to me.
    I use auto for cpu and I never bat. things seem ok

    Comment

    • cwilli28
      Rookie
      • Jun 2010
      • 11

      #3
      Re: Sliding Errors - CPU Runners cost runs.

      I never bat. things seem ok
      You don't hit? So do you have a chance to take control of runners and see that they don't respond to you sending them home?

      Comment

      • squashbuggie
        Banned
        • Dec 2016
        • 371

        #4
        Re: Sliding Errors - CPU Runners cost runs.

        Originally posted by cwilli28
        You don't hit? So do you have a chance to take control of runners and see that they don't respond to you sending them home?
        never dude

        Comment

        Working...