|
1 month ago ::
Oct 27, 2009 - 2:53PM
#1
|
|
|
I had a problem with DST PA from Week 1. It came down to 2 points in my league. I contacted fox and they told me if they ran the scoring to correct it, then the changes I made to my scoring would take place for all weeks. I didn't want that, I told them no thanks. I took the 2 point loss. It sucks, but sometimes stats are wrong when the scoring is "finalized". Had the problem with a different site last year...
|
|
1 month ago ::
Oct 27, 2009 - 2:14PM
#2
|
|
|
I have given up on this stat being fixed. If that stat alone is fixed, and negative yardage for negative points is not implemented, the wrong team wins a game in my league.
But seriously, this is a cut and dry case of an incorrect stat, yet FOX Sports seems incapable of fixing it.
|
|
1 month ago ::
Oct 27, 2009 - 1:20AM
#3
|
|
|
Seriously, we are all trying to have a fun time and expect Fox Sports to please take these issues seriously. This thread is completely correct, and this commish is doing exactly what you (Dawn) has advised people to do. This is not the way to treat your customers.
|
|
2 months ago ::
Oct 19, 2009 - 2:37PM
#4
|
|
|
Time for my weekly check-in on this issue. Dawn, you said Baltimore did block a punt in Week 1, as this site shows. But I assert that the actual game stats from NFL.com (and other sites) show that it was Baltimore that had a punt of their own blocked.
Can we please resolve this?
|
|
2 months ago ::
Oct 12, 2009 - 3:13PM
#5
|
|
|
Week 1 baltimore did have a blocked punt...
No, they did not.
If you go to NFL.com and the box score for this game, http://www.nfl.com/gamecenter/200909130 … t-boxscore, you will see punts for Baltimore, and how many of those that were blocked. Punt blocks listed under Baltimore is for Baltimore punts that were blocked.
For proof, noting from the game stats that there was only one punt blocked in the game by either team, here is the play log for the drive ending in that blocked punt. Note that it was Kansas City that did the blocking.
Play-by-Play Log
Baltimore Ravens at 11:29
1-10-BAL 9 (11:29) 27-R.Rice left guard to BLT 14 for 5 yards (53-D.Williams).
2-5-BAL 14 (10:55) 5-J.Flacco pass incomplete short left to 85-D.Mason.
3-5-BAL 14 (10:49) (No Huddle, Shotgun) 5-J.Flacco pass short left to 27-R.Rice to BLT 16 for 2 yards (56-D.Johnson).
4-3-BAL 16 (10:09) (Punt formation) 4-S.Koch punt is BLOCKED by 47-J.McGraw, Center-70-M.Katula, RECOVERED by KC-47-J.McGraw at BLT 0. TOUCHDOWN.
Is this error happening for other Defense/Special Teams? If you are assigning a punt block to the wrong team, it may be. I don't have time to look for an example. Just please fix this.
Also, when will that negative scoring for negative yardage kick in?
|
|
2 months ago ::
Oct 12, 2009 - 1:53PM
#6
|
|
|
Week 1 baltimore did have a blocked punt...
|
|
2 months ago ::
Oct 07, 2009 - 10:33AM
#7
|
|
|
Another week goes by and this stat error, and it seems many others, have not been fixed. Dawn? FOX Sports? Do you intend to fix these errors, and/or give us scoring editting, or are we just screwed?
|
|
2 months ago ::
Oct 01, 2009 - 9:18AM
#8
|
|
|
This stat has not been fixed. A Week 1 stat! Baltimore did not block a punt in Week 1. You said you'd fix it. Just how many stats do you have wrong that haven't been found yet.
|
|
2 months ago ::
Sep 22, 2009 - 7:13PM
#9
|
|
|
I agree Elwood, one of our teams lost the game by
NESTANi (1-1-0) CP: 0 YTP: 0 PMR: 0 102.4 0% 0 pts
Brooklyn Bombers (1-1-0) CP: 0 YTP: 0 PMR: 0 102.1 0% 0 pts
He lost the game because fox has Phil Rivers with 2 INT, and in reality he only got 1,
Come on FOX FIX THIS,
Chicago def on sunday got a fumble recovery, Ben Rothburger got 1 int not on the fox
|
|
3 months ago ::
Sep 20, 2009 - 6:33PM
#10
|
|
|
Thanks, Drew!
----
Are you referring though to this or other Week 1 scoring issues? That those would be fixed when the Week 2 scores become final? I guess I'll find out soon enough.
|