Warrior General Games

http://glb2.warriorgeneral.com/game/replay/14859/2962702

Doesn't make a lot of sense to Spike it on 3rd and Long and to turn around and punt. This cost me a shot at a game winning FG in a League game.

The worst part about it is that hte ball is on the 32, so +17 is 49 yards and my max FG range is set to 50 yards.

you ran the ball the play before, time probs would have ran out if you ran again, hence the spike.

Originally posted by Jampy2.0
you ran the ball the play before, time probs would have ran out if you ran again, hence the spike.

The point is that it went from a Spike to a Punt. At the very worst it should have ran another play on 4th down, not punted. However, the distance was still within my Max FG range so there is no reason I shouldn't have attempted the 50 yarder.

Originally posted by Parab00n
The point is that it went from a Spike to a Punt.

Yeah I think that was just bad luck.

My only problem with this 'bug' is if it would be here if they spiked and then your team goes on to make the game winner?
i doubt it.

Originally posted by Jampy2.0
Yeah I think that was just bad luck.

My only problem with this 'bug' is if it would be here if they spiked and then your team goes on to make the game winner?
i doubt it.



Of course not, the entire point is that I wasted a down to stop the clock to go into a punt. If it was a spike that turned into a FG attempt it would be working exactly how it should be.

The real question is does the sim take into account the next plays playcall before spiking...
And does the sim take into account distance from endzone when spiking?

OT: If you ran 2 plays in a row you probs would have run out of time...

If this is a common thing for I'd say get clock manager and pass when you're losing late...

This seems borderline buggy, but there were some tactical possibilities that could have set you free,
which is why i don't think this is a bug.

Originally posted by Jampy2.0
The real question is does the sim take into account the next plays playcall before spiking...
And does the sim take into account distance from endzone when spiking?

OT: If you ran 2 plays in a row you probs would have run out of time...

If this is a common thing for I'd say get clock manager and pass when you're losing late...

This seems borderline buggy, but there were some tactical possibilities that could have set you free,
which is why i don't think this is a bug.

There is actually 2 Bugs here or at the very least should be.

1. You don't spike the ball on 3rd down if you are going to punt on 4th under any circumstance.

2. It would have been a 49 yard FG attempt, my Max setting was set to 50 yards.

http://glb2.warriorgeneral.com/game/forum/thread/5149837

There was another thread made about the same issue a while back as well, from what I could gather the common thing between the games this has happened in is that they were all within 3 points when the game decided to punt instead of going for it or kicking the field goal.

Originally posted by Parab00n
1. You don't spike the ball on 3rd down if you are going to punt on 4th under any circumstance.

Unless you are going to run out of time.

Originally posted by Jampy2.0
Unless you are going to run out of time.

In what situation would you ever need to spike the ball to make sure you have time to get off a punt?

Lol

Originally posted by hiimjake
In what situation would you ever need to spike the ball to make sure you have time to get off a punt?

Originally posted by Jampy2.0
The real question is does the sim take into account the next plays playcall before spiking...
And does the sim take into account distance from endzone when spiking?

Do we know that the sim knows a punt is coming? Or is the sim spiking because it is in FG range and it wants to stop the clock for a FG attempt.

Think about it.

It has to be coded in to spike there so it doesn't matter If the sim knows a punt is coming up. It woulda been fine if it kicked the fg though.

Before I had thought Jampy was possibly just trolling people, after some of his replies in this thread I have narrowed my guesses down to 2 options:

1. He is 12 years old and hasn't developed any type of common sense yet.

2. He is a window licker.