no content
AdBlocker active?
It seems you are using software to block advertisements. You could help us if you could switch it off when visiting redzoneaction.org.
The reason is very simple: Advertisements help us running the site, to offer you the game in a good quality for free. So if you like the game, please support us by purchasing a Supporter Account or disabling the AdBlocker on this site.
Thank you very much!
| Main / Bug reporting / Play after clock is all zeros... Search Forum | |
| Navigation: |< 2 > >| | |
| Poster | Message |
| posted: 2018-01-29 21:35:05 (ID: 100122794) Report Abuse | |
|
Not sure, but I appeared to tie this game after the clock had already expired. Not sure if it's a rounding issue or something else.
match 100566275 0:00 3 and goal to go on opp 1, Quincy Colvin (OC) snaps the ball to Charly Grégoire (QB), Charly Grégoire (QB) selected Ashley Paul (WR/L) as target, Peter Schuster (OLB/L) seems to go for the blitz, Rocky Locke (FB/R) blocks, the pass goes outer left to the receiver, who catches the ball, tackled by Goran Werner (FS/C), forward progress: 1 yards (Shotgun 2 WR vs. 4-4-3) more 0:00 touchdown more 0:00 Ball spotted on the 15, Roberto Romero (K) kicks the ball for the PAT, PAT is good Sill lost in OT though... :-( Steve SD Blitz |
|
| Quote Reply Edit | |
| posted: 2018-01-29 21:44:52 (ID: 100122795) Report Abuse | |
|
When a touchdown occurs in regular gametime (NOT overtime!!) with no time on clock left, PAT is required by rule!
Therefore, no bug |
|
| Quote Reply Edit | |
| posted: 2018-01-29 21:50:30 (ID: 100122796) Report Abuse | |
|
And the official reason for this is: either team has a chance to score by the PAT, there it has to happen.
However, I am sure you will find evidence in the NFL rulebook... |
|
| Quote Reply Edit | |
|
Bovakian
|
posted: 2018-01-29 21:51:56 (ID: 100122797) Report Abuse |
|
I watched this match and that final play did not show live and game went into overtime. Only after reloading page did it show. |
|
| Quote Reply Edit | |
| posted: 2018-01-29 21:56:48 (ID: 100122798) Report Abuse | |
|
Wait, the bug report is for the display, not for the fact the try happened with no time on clock?
|
|
| Quote Reply Edit | |
| posted: 2018-01-29 21:58:33 (ID: 100122799) Report Abuse | |
|
pete wrote:
Wait, the bug report is for the display, not for the fact the try happened with no time on clock? I think it's that the actual play itself happened with no time on the clock. |
|
| Quote Reply Edit | |
| posted: 2018-01-29 22:02:52 (ID: 100122800) Report Abuse | |
|
lions1934 wrote:
pete wrote:
Wait, the bug report is for the display, not for the fact the try happened with no time on clock? I think it's that the actual play itself happened with no time on the clock. This part is according to the rules, so this cannot be a bug. |
|
| Quote Reply Edit | |
|
Bovakian
|
posted: 2018-01-29 22:03:53 (ID: 100122801) Report Abuse |
|
lions1934 wrote:
pete wrote:
Wait, the bug report is for the display, not for the fact the try happened with no time on clock? I think it's that the actual play itself happened with no time on the clock. Previous play was incomplete pass so it could be that the game clock had not completely gone to zero when the play finished so there was possibilty of another play being mad, but what I said that the Q4 display still showed SDB on 3 for the period and the game went into OT without the play being displayed live and the scoreboard showing OC still leading. |
|
| Quote Reply Edit | |
| posted: 2018-01-29 22:09:04 (ID: 100122802) Report Abuse | |
|
I starts to confuse me what this report is about. Steve, please clarify.
A.) If this bug report is about the fact the PAT at the regular game finish was played: this is no bug! B.) If it is a report for not showing the 1 point, this is "by design". I cannot reload the thing to have a proper display, because I would reveal the final standing at that moment. Sorry for that |
|
| Quote Reply Edit | |
| posted: 2018-01-29 22:12:22 (ID: 100122803) Report Abuse | |
|
C.) If it is because the touchdown happened at 0:00...the internal gameclock works in millisecs, so I would have to write 0:00.786...which is plain ugly, and therefore it is 0:00 Trust the computer he knows very well if the gameclock has ticks left or not.
|
|
| Quote Reply Edit | |
| reply Mark this thread unread | |
| Navigation: |< 2 > >| | |
| Main / Bug reporting / Play after clock is all zeros... | |
