Tell us how he reached on error in the play by play?

[iscore@tragus.org]

I'm re-reading the play by play and I see 'Reached on Error' in all the right places but it doesn't tell me who made the error. To know that I have to go back to the scorecard & sort out who was in which fielding position for the defense when the error was made. It would be handy to have that in the p-b-p detail.

Related to that, and I know there's a thread about alternate scorecard formats, it would also be cool to see the current state of the diamond at the end of the play for each p-b-p line. I'm sure that's not an easy thing but that's my two cents worth for integrating the scorebook and play-by-play.

As always, thanks for a fantastic app. With iScore I'm able to give our coach defensive detail he's never been able to capture on his past teams.

[OhioTex]

Both of these details, 1) Error source and 2) current state of the diamond already exist in the more detailed " pitch-by-pitch"l on the iPhone, so would expect FTM to put on list and become a question of priorities. as you pointed out not in the "play by play" detail on the web. The error one specifically seems like a big miss. (guess i was lucky having errorless ball lately and had not noticed...

[FTMSupport]

The Play by Play is intentionally left as a "lightweight reading" of the events of the game. We do not want it to become the same as Pitch by Pitch which has every detail of the game, and takes a lot longer to read. With Play by Play, you get a simple overview of the games, and can read through an entire game very quicly.

[iscore@tragus.org]

That makes sense. I was just thinking of ways to answer questions that the coach might have a day or two after the game when the details aren't fresh. I can certainly dig that out between the scorecard & play-by-play but having it all in one place would be a big help.

[OhioTex]

I generally like the play-by-play balance of depth vs length.

that said, would consider adding who created the error into the play by play as a resonable question.. ... but understand the challange of where to cut off the detail.