1.088 observations

[darrellb9]

Playing Quick game, US rules.

1) Interceptions - had 4 in the first 8 min. of the 1st quarter, seems like a little too many now. [;)]

2) Penalties - have seen several times where the down and the yardage to go are missing from the penalty message. End zone ball placement seems fixed though.

3) AI - the computer was on the 22 yd line and elected to punt rather than kick a FG?!? Good for me, but realistic?

4) Not sure if this is a bug or just the 'mixture' of rules. In US rules (at least NFL and I believe college) when a player runs out of bounds the clock should stop.

5) I had an instance of the computer team running a regular play on 4th down (I was only offered punt formation on defense) which I thought, incidentally, was cool that they would go for it on 4th and short. The computer team gained 50+ yds but instead of getting the first down (it was 4th and 2) I got the ball at the line of scrimmage. No penalties were called that might have given me the ball in this instance BTW.

Only had time to play a half last night but those are the things I found.

Definately some improvements over initial release.

David, I'd just like to commend you on your responsiveness on these forums. I haven't owned too many games where the developer took the time to read and answer as many posts as you do. Especially considering some of the 'abuse' you took just prior to release...

[Magnum357]

3. Ya, I have notice that a couple of times aswell with Feildgoal attempts. But the way the FG Kicking system is now, its probably better to punt because I hardly ever get many Feildgoals succeed even with Highly rated Kickers. Also, the Feildgoal attempts hardly get any height at all (barely above the crossbar at times) and usually results in misses. I use to Feildgoal kick a lot. I don't consider myself that good at it (maybe at Highschool level at best) but even I could kick a FG attempt at least 25 to 30 feet in the Air. The best this game seems to offer in FG attempts is barely above 10 feet.

4. Ya, I have notice this aswell. A few times, I had receivers catch the ball before they went out of bounds, but the clock would still keep running. I'm not CFL expert, but I thought Completed Passes that go out of bounds do stop the clock like in the NFL.

[Marauders]

4) Not sure if this is a bug or just the 'mixture' of rules. In US rules (at least NFL and I believe college) when a player runs out of bounds the clock should stop.

In the NFL, the clock only stops from out of bounds plays in the last two minutes of the first half and last five minutes in the game, otherwise it only stops until the ball is set in play.

[firebirds]

Marauders, My understanding of the NFL rules is that the game clock stops on any play at any time of the game when the result of the play is an incomplete pass or an out of bounds situation. Is it possible that there might be a bit of confusion regarding the play clock of the NCAA and the NFL, specifically in regard to when the play has ended and when the ball is set? I do know that there are some differences between the two.

[Magnum357]

Actually, I think Marauders may be right on this. I think I remember a few years ago the NFL adding some special Game Clock Rules as he indicated. I think the idea was too keep the game going and not have it slow down as much, not sure.

[Tullius]

My understanding of the NFL rules is that the game clock stops on any play at any time of the game when the result of the play is an incomplete pass or an out of bounds situation.

Marauders is right. When a player runs out of bounds the clock stops not - only in some situations at the end of a half. Look at the last Super Bowl. There was a situations when Pittsburgh ballcarrier went out of bonds with 10 minutes play in the 4th quarter. The clock did not stop.

[firebirds]

I double checked and I'm the one compounding the confusion here. I hereby humbly sit down in a corrected manner. Marauders, Magnum and Tullius, my apologies.

[Breeze]

I just had a thought, and I could be entirely wrong:

We know that the snap distance on kicks right now is incorrect (it's too short). Maybe this is somehow affecting the accuracy of the kick? Some people have said that passes seemed to be more accurate when the QB dropped back farther, so maybe this is a similar situation.