Forums

Help › Forums

Re: Scorecards shown for Tie scores.

rated by 0 users
Sun, Jun 1 2014 4:05 PM (11 replies)
  • PAGES
  • 1
  • 2
  • Shedlite
    917 Posts
    Sat, May 31 2014 6:12 PM

    Tamsach:

    I've been unlucky with Bracket Tournaments. Three time I tied and three time I lost. I would like to see the scorecards, just for curiosity and consolation. ;) Could it be possible? Tks Bye

    i guess i 'm the guy that's opposite you....I've advanced 3 times on tie score. Usually when i birdie last hole or last couple of holes.

    I do agree with another reply.....don't tempt them to add something else that will cause problems elswhere

  • ShadyShank
    629 Posts
    Sun, Jun 1 2014 4:05 PM

    chrisironsbones:
    It wont change the result and analyzing It wont make much difference.

    While I agree with this sentiment, I too have felt the same on wanting to be able to see the actual scorecards after a tie. Not because I think I've been screwed out of a win, but because I know for a fact that, especially gaming software, makes mistakes and glitches all the time. Also, I'd like to be able to see them just to see what shot it was that i missed that lost the game for me.

    It's more of just being interested for me. And I don't believe it is asking too much either. I mean, the software decides the tiebreak from the scorecards so they must exist. I get to see my scorecard after every single hole I shoot, so how hard could it be to post the cards when there is a tie, if even for only an hour or so? Or, not post them but have a place they can be viewed that would take up no space at all in comparison to Pinehurst #2 or any other course here. Or, a simple program that emails each player the scorecards who are involved in a tie?

    My mailbox is full of WGT receipts, replies to posts when I have never even checked that box, etc. Shooting out a few more each day seems like a non-issue to me.

    We're talking a few MB's compared to GB's, and there is no comparison there as far as eating up bandwidth enough to cause glitches or issues elsewhere on the site.

  • PAGES
  • 1
  • 2
RSS