The headline says it all. If you don't want to read a long vent post, that's what happened.
My team is The New Kids. We're 0-3 and are up against a really good 2-1 team in The Beaufort Zebras. The CPU simulated a pretty good game that went into overtime off of a solid 2-minute drill and a long kick. The climax of this game was so suspenseful. Although I struggled to wonder why my team was spamming HB Sweep strong, and why my outside run defense never fired in SB Trips, I chalked that up to tactical mistakes I've been making for years when I over plan.
Anyways, it's overtime. My team is 0-3. It's 17-17. 3:37 on the clock I'm on defense, check this out;
" 1st & 10, OPP 24, QB Major Tom handed off to HB Jerome Bettis for a 1 yard gain before a forced fumble by DT1 Bubba Finklestein! LOLB Deadlif Jones recovered the fumble and returned it 1 yards. Tackled by LOT Junior Samples." https://glb2.warriorgeneral.com/game/replay/729211/319284
I was so juiced I jumped! NOw it's 3:33 seconds left and we have 76 yards to go. This is when the game gets really good! https://glb2.warriorgeneral.com/game/replay/729211/319288
Well, we got 3 and out' ed and have to punt at the 2-minute warning (keep the time in mind). I told the team "don't give up!" Here is what happens next;
"1:50, 1st & 10, OWN 45, QB Major Tom threw a pass to WR3 Lamb Shank, who made the catch for a 10 yard gain. Tackled by CB3 Tireda Dishette. "
Here is where spike the ball football logic seems to have been overlooked.
It's 17-17. Neither team has timeouts. My opponent's QB throws a 10-yard pass which is short of the first down. Next his QB does not spike the ball to stop the clock. Instead, he wastes about 36 seconds to hike the ball to go for a 1st down on a singleback sweep right. Look what happens;
"1:14, 2nd & inches, OPP 45, QB Major Tom pitched to HB Jerome Bettis for a 2-yard loss before a forced fumble by MLB Martin Milk Money! NT Bubba Finklestien recovered the fumble and returned it -1 yards. Tackled by QB Major Tom".https://glb2.warriorgeneral.com/game/replay/729211/319312
I was like, ARE YOU KIDDING ME!!! YES!!! (I really cursed and called the apposing runningback all kinds of the demeaning name as I celebrated a chance for a win).
Before I go on, what was my opponent's QB doing? Running the clock in a tie overtime game? Going for the tie? Were are the tactics for that? That has to be addressed. I think its just a bug in the Overtime spike the ball script (or whatever).
But it gets worse.My team has the ball now;
"1:09, 1st & 10, OWN 48, QB Jamani Jackson threw a pass to BTE Owen "open-end" Edwards, who made the catch for a 14 yard gain and a first down! Tackled by ROLB Buddy Holly Jr.."
LOOK<<< That play happened at 1:09. IT was a 14-yard pass. First down. The play took 4 seconds. It's 1:05 when the play was called dead but for some reason, my team just chills on the field, with no time outs, in OVERTIME, and runs the clock down to 32 seconds??!?. Why didn't either of our QBs spike the ball to stop the clock in these game-winning situations? It's a cold-blooded occurrence that has to get fixed. IF we can run a 14 yard play in 4 seconds my special teams could have ran to the middle of the field and back in the 36 seconds that my team wasted in the most time-sensitive moments. Its called, "overtime", time is the root word. All aspects of time have to be taken into account in overtime. And I know you all know this, its a bug, not a feature. But still, it sucks to have experienced this.
Watch the entire overtime if you wish and tell me I'm tripping.
Thanks for reading. https://glb2.warriorgeneral.com/game/replay/729211/319166
My team is The New Kids. We're 0-3 and are up against a really good 2-1 team in The Beaufort Zebras. The CPU simulated a pretty good game that went into overtime off of a solid 2-minute drill and a long kick. The climax of this game was so suspenseful. Although I struggled to wonder why my team was spamming HB Sweep strong, and why my outside run defense never fired in SB Trips, I chalked that up to tactical mistakes I've been making for years when I over plan.
Anyways, it's overtime. My team is 0-3. It's 17-17. 3:37 on the clock I'm on defense, check this out;
" 1st & 10, OPP 24, QB Major Tom handed off to HB Jerome Bettis for a 1 yard gain before a forced fumble by DT1 Bubba Finklestein! LOLB Deadlif Jones recovered the fumble and returned it 1 yards. Tackled by LOT Junior Samples." https://glb2.warriorgeneral.com/game/replay/729211/319284
I was so juiced I jumped! NOw it's 3:33 seconds left and we have 76 yards to go. This is when the game gets really good! https://glb2.warriorgeneral.com/game/replay/729211/319288
Well, we got 3 and out' ed and have to punt at the 2-minute warning (keep the time in mind). I told the team "don't give up!" Here is what happens next;
"1:50, 1st & 10, OWN 45, QB Major Tom threw a pass to WR3 Lamb Shank, who made the catch for a 10 yard gain. Tackled by CB3 Tireda Dishette. "
Here is where spike the ball football logic seems to have been overlooked.
It's 17-17. Neither team has timeouts. My opponent's QB throws a 10-yard pass which is short of the first down. Next his QB does not spike the ball to stop the clock. Instead, he wastes about 36 seconds to hike the ball to go for a 1st down on a singleback sweep right. Look what happens;
"1:14, 2nd & inches, OPP 45, QB Major Tom pitched to HB Jerome Bettis for a 2-yard loss before a forced fumble by MLB Martin Milk Money! NT Bubba Finklestien recovered the fumble and returned it -1 yards. Tackled by QB Major Tom".https://glb2.warriorgeneral.com/game/replay/729211/319312
I was like, ARE YOU KIDDING ME!!! YES!!! (I really cursed and called the apposing runningback all kinds of the demeaning name as I celebrated a chance for a win).
Before I go on, what was my opponent's QB doing? Running the clock in a tie overtime game? Going for the tie? Were are the tactics for that? That has to be addressed. I think its just a bug in the Overtime spike the ball script (or whatever).
But it gets worse.My team has the ball now;
"1:09, 1st & 10, OWN 48, QB Jamani Jackson threw a pass to BTE Owen "open-end" Edwards, who made the catch for a 14 yard gain and a first down! Tackled by ROLB Buddy Holly Jr.."
LOOK<<< That play happened at 1:09. IT was a 14-yard pass. First down. The play took 4 seconds. It's 1:05 when the play was called dead but for some reason, my team just chills on the field, with no time outs, in OVERTIME, and runs the clock down to 32 seconds??!?. Why didn't either of our QBs spike the ball to stop the clock in these game-winning situations? It's a cold-blooded occurrence that has to get fixed. IF we can run a 14 yard play in 4 seconds my special teams could have ran to the middle of the field and back in the 36 seconds that my team wasted in the most time-sensitive moments. Its called, "overtime", time is the root word. All aspects of time have to be taken into account in overtime. And I know you all know this, its a bug, not a feature. But still, it sucks to have experienced this.
Watch the entire overtime if you wish and tell me I'm tripping.
Thanks for reading. https://glb2.warriorgeneral.com/game/replay/729211/319166
