Page 1 of 1
Incorrect Score after Editing Play-by-Play
Posted: Thu Oct 15, 2009 4:48 am
by don.english
I went back into a game and changed two plays from hits to errors (one for the home team and one for the visitor). Now the score shows an extra run for each team everywhere except on the scorecard (pdf). The scorecard still shows 8-7, but the game is listed as 9-8 and all of the non-PDF outputs show 9-8. Any idea what is going on or what I did wrong?
This is in the TE Opponent vs Tulsa Eagles game scored on 10/11. I have exported my data to you and I believe you have my customer ID.
Thanks!
Re: Incorrect Score after Editing Play-by-Play
Posted: Thu Oct 15, 2009 9:49 am
by FTMSupport
It is hard for us to troubleshoot specific issues in the forum. If you can email us directly at
support@fasterthanmonkeys.com with this issue, we can take a look and respond to you directly.
Thank you.
Re: Incorrect Score after Editing Play-by-Play
Posted: Thu Oct 15, 2009 9:53 am
by don.english
Will do. Thanks!
Re: Incorrect Score after Editing Play-by-Play
Posted: Thu Oct 15, 2009 2:11 pm
by OhioTex
I will be curious to hear the outcome, as play by play editing is designed to prevent any changes that would impact teh score...
(PS was in tulsa on business this week)
Re: Incorrect Score after Editing Play-by-Play
Posted: Thu Oct 15, 2009 2:28 pm
by don.english
I will let you know what is discovered.
So did you feel like you were in Seatle instead of Tulsa? I haven't seen the sun in over a WEEK! lol
Re: Incorrect Score after Editing Play-by-Play
Posted: Thu Oct 15, 2009 2:38 pm
by FTMSupport
It looks like this issue is related to tie breakers, and the runners added to the bases not showing correctly on the scorecard. We are still researching.
Re: Incorrect Score after Editing Play-by-Play
Posted: Fri Oct 16, 2009 4:30 am
by don.english
What was discovered:
Report from support is that it is a tie breaker issue with the scorecard. I was incorrect in the direction of the error. The scorecard is in error, not the other outputs. The score was 9-8. According to support this issue will be fixed in a post 2.10 release.
Keep up the great work FTM!