41 coaches online • Server time: 12:36
* * * Did you know? The highest gate in a single match is 243000.
Log in
Recent Forum Topics goto Post Gnome Roster - how a...goto Post Problem to organize ...goto Post Updated star player ...
pubstar
Last seen 7 years ago
pubstar (20986)
Overall
Rookie
Overall
Record
0/0/0
Win Percentage
n/a
Archive

2015

2015-05-24 16:19:59
rating 2.2

2012

2012-07-11 18:28:59
rating 5.3
2012-05-22 05:51:34
rating 5.1
2012-04-22 13:16:15
rating 5.2
2012-04-15 12:51:59
rating 5
2012-03-08 07:17:18
rating 5

2010

2010-03-03 17:46:16
rating 5.2
2010-03-02 13:45:25
rating 4.8
2010-02-08 13:06:10
rating 4
2010-02-01 13:45:19
rating 5.3
2010-01-26 20:40:50
rating 4.8

2009

2009-11-17 20:04:01
rating 3.4
2009-11-12 04:17:22
rating 3.6
2009-08-30 17:15:56
rating 2.2
2009-07-25 04:40:24
rating 3.7
2009-06-19 21:52:15
rating 3.6
2010-01-26 20:40:50
28 votes, rating 4.8
Just a thought on match reports
I value the match report page highly. Obviously, you can't really tell the nuts and bolts of what happened in a match without watching the replay, but the report page gives you a very good idea.

Who blocked, fouled, passed, etc. People seem split on the luck meter, whether or not it means anything, but that's there too. Great stuff.

I would never call into question the effort put forth by the site's administrators, it's a great site run free of charge by people who love the game. So, hat's off to them before I humbly ask for more free labor.

It seems to me that KO's (and possibly x/y KO rolls successfully made) really should be a part of the match report page. Often, a KO is as good as a casualty, which are very well documented, even which type inflicted, though the nature of the casualty doesn't matter in the context of the match. At the very least, it's exactly as good as a casualty for one drive. In a game that is rarely decided by multiple scores, one drive is huge.

So if the intent of the match report page is to give a coach a clear idea of the events of a match, I think KO's are definitely worthy of inclusion.

thanks for reading,
~pubstar
Rate this entry
Comments
Posted by TempestBlade on 2010-01-26 20:49:41
Very good point! For teams with mass Regen, a KO is pretty much equivalent to a CAS (50/50 chance of returning from the result next drive, only major difference is that if you fail that roll the first time with Regen, you don't get another chance...)
Posted by justagigolo on 2010-01-26 21:21:16
I would like to throw my support behind this as well. All to often the match report does not tell the whole story by omitting the ko's. I have had a few matches where although I suffered no casualties, I had 8 people ko'ed on the sidelines.
Posted by Calthor on 2010-01-26 21:37:36
I agree.
Posted by Cavetroll on 2010-01-26 23:24:56
I would like to see KOs added to the match report if it is within the realm of possibility.
Posted by Raasted on 2010-01-27 00:52:12
Agree agree! ;)
Posted by Arktoris on 2010-01-27 06:29:10
KOs just don't bring that same warm fuzzy feeling as the CAS though.
Posted by pythrr on 2010-01-27 08:34:39
CAN I HAS STUN AND FALL OVER AND GFI FAEL AND DROPPED PASSES AND FUMBLES AND BONEHEADS AND AFABS ETC TOO...? WHERE WOULD IT END/...

oh, my eyes
Posted by ultwe on 2010-01-27 14:46:43
For this to happen, the client would need to report it. Something tells me that in the current climate, it is unlikely that Ski will make any update to JavaBB in a hurry....

The Fantasy client Kalimar is rumored to be working on may do it, but I doubt that this will be high in the priority list
Posted by Jeffro on 2010-01-27 18:56:55
Having just played a game where at one point I had failed 9 of 10 KO rolls... I suppose I see the point behind it. But in the rare situations that it happens to affect the game drastically (as it did mine) it can be added to game report.

pythrr's right... do you record KO's? How many returned? WHO was KO'd?!?... that's stuff that can go in a game report without bothering the folks writing the code.