PDA

View Full Version : Nfl (10/26-27/2008)


Taleren Bloodsong
10-24-2008, 04:08 PM
Week 8

This is for the 26th-27th. Entered wrong dates

Kelraz Bladesinger
10-26-2008, 02:56 PM
Wow, I'm looking to lose all of my vCash today.

Bylimet Spiritwalker
10-26-2008, 04:07 PM
Thought I was about to drop 200 on the Redskins, but they squeaked by with a 1/2 point lead after a late field goal. :D


I swear, there is no sure bet this season.

Kelraz Bladesinger
10-26-2008, 06:18 PM
Yeah, my 500 was the other half of that bet. Honestly, Redskins should have manhandled the Lions, and I really thought the Raiders were gonna do a lot better than they did against the Ravens.

Bylimet Spiritwalker
10-26-2008, 07:52 PM
Yeah, my 500 was the other half of that bet. Honestly, Redskins should have manhandled the Lions, and I really thought the Raiders were gonna do a lot better than they did against the Ravens.

Ravens and Redskins were my two wins this week; Jaguars my loss.

Bylimet Spiritwalker
10-28-2008, 10:09 AM
Um, Ravens 29 Oakland 10.

29 - 10 = 19. Isn't that enough to cover a 7.5 spread? :cool:

Selwen Soulgazer
10-28-2008, 11:30 AM
shhhh.

Kelraz Bladesinger
10-28-2008, 11:57 AM
Oh, hrm. Cool!
http://www.cbc.ca/arts/images/pics/chappelle1.jpg
I'm rich, beeyach!

Taleren Bloodsong
10-28-2008, 12:07 PM
I'd swear I hit the ravens covered check box. I guess I didn't.

Taleren Bloodsong
10-28-2008, 12:08 PM
Again Sanchek will have to fix this. Sorry guys.

Bylimet Spiritwalker
10-31-2008, 06:06 PM
Again Sanchek will have to fix this. Sorry guys.


I sent him a note, but not fixed still. /shrug

Taleren Bloodsong
11-02-2008, 10:37 AM
I am sorry, check boxes can be misread even straight across when I'm trying to hurry to get this done.

Shortyrez Starfury
11-08-2008, 02:32 PM
Has this been corrected?

Bylimet Spiritwalker
11-09-2008, 07:54 AM
Has this been corrected?

Nope.

But I just noticed a message from San regarding this in my inbox, so I expect it will be addressed soon.

edit:
Just saw that my vCash has been adjusted, so I am figuring the error was corrected today.