the names of the players who scored?
Yes
And the half time score?
No, however, once development on the dice logs is complete I will be able to provide this, along with what turn the players scored - or at least, my best guess of when that was, things like the clock going forwards/backwards a turn, or people doing the sum total of nothing on their turn will screw it up.
There is a pending change to do that will bring the "end of normal time" score into the database though - for use in cup matches. That's going to come along first, it's not too tricky to do.
I propose a structure like this for a matchreport API.
{ home_score : 2
, home_passes : 5
... and so on, like the current file
, touchdowns {
1 : { scorer : Ernie
, team : home
, turn : 6
, method : pass catch (possible options = pass catch, hand-off, pickup, interception, run in, depending on what they did on the turn they scored)
}
2 : { scorer : Alan
, team : home
, turn : 14
}
}
}
As mentioned, the touchdowns will just have the scorer for now, but may as well build the structure of the API to make future expansion easy.
Other possibilities I could do now that may be of interest for the match report...
- player with most yards run (overall? per team?)
- player with most yards passed (overall? per team?)
- most violent player (overall? per team? can be most casualties caused, but I'd prefer something like most knockdowns inflicted (ie armour breaks))
But I am wary of having too much data on one image.
If you want the API structure different then let me know. I can do one record per team and do away with the home_ and away_ prefixes easily enough - in fact that's how it's stored in the DB, but I found the home_ and away_ prefixes to be easier for building the matchreport web page. After all there will never be more than 2 teams in a game of blood bowl.
Then the coach writing the report gets to choose which images or combination thereof to use in his report. For example, starting with the main score image, writing a bit of report, then following up with some stats/dice analysis below. It would at least let us break up the walls of text we write sometimes.
Long-term it's been suggested that match reports are written to the website. It'll be another tab on the match report page. Obviously I need to set user logons and such first. Then you can see *all* the data pertaining to the match and the report, all in one place.
My personal opinion is that that's good, you can go back & relive matches, but having a summary image & the match report on the forums is good too, for a few reasons, eg this is a better place to discuss things, and it means they are all in the same place for readers to look at after a weekend's matches.
