Forum Discussion

UtahUtes32's avatar
UtahUtes32
Seasoned Ace
1 year ago

:02 left in half, down 17-7 on my own 27, CPU NEEDS to call prevent, not a blitz

Heisman difficulty (default sliders), 5 minute quarters in Dynasty. 

With :02 seconds left in the half, I'm down 17-7 on the road to Michigan State and on my own 27 yard line: CPU NEEDS to run prevent defense.

Instead they chose to run a blitz with a safety covering my 98 speed WR down the field.  Result is an easy TD.  This is not the first time I've seen this before.

Please IMPROVE THE CPU defensive playcall logic for END OF HALF SCENARIOS.

https://youtu.be/a2tintTmnuk

discussion

6 Replies

  • sdzald's avatar
    sdzald
    1 year ago

    I'm not disagreeing with you guys but I've seen coaches in real games make calls like that.  No I won't call a blitz in cases like that but I don't like calling prevent defense in any situation.  There is an old saying, "all the prevent defense does is prevent you from winning."

  • UtahUtes32's avatar
    UtahUtes32
    Seasoned Ace
    1 year ago
    @sdzald You are correct but it is RARE that prevent is not called in real life. This should be the exception, not the rule in CFB25. 9/10 times prevent should be called.
  • Anobix's avatar
    Anobix
    Seasoned Ace
    1 year ago
    @sdzald wrote:

    I'm not disagreeing with you guys but I've seen coaches in real games make calls like that.  No I won't call a blitz in cases like that but I don't like calling prevent defense in any situation.  There is an old saying, "all the prevent defense does is prevent you from winning."

    Prevent for more than 1-2 plays I agree. With 2 seconds left and only a single play that can be done, I could see doing prevent or something similar vs blitzing where if you get the pass off it's an easy TD.

Recent Discussions