I'd thought about length and end stats, but I'd have to parse the entire demo file to get them, which is not impossible but would involve writing a version of the full server update parser in the menus, checking for all server messages, and advancing the message pointer appropriately for the data type(s) and size(s).
Player names are not really practical, as a demo could potentially have any number of players entering and leaving at any point in it.
There's also space considerations, with a limited amount of space to display the info.
One thing I did add though was a filter (also works on Maps and Load/Save) - type the first few letters of the demo name and the selection will be restricted to demos that match. Very handy if you've got a really really long list to select from.
Player names are not really practical, as a demo could potentially have any number of players entering and leaving at any point in it.
There's also space considerations, with a limited amount of space to display the info.
One thing I did add though was a filter (also works on Maps and Load/Save) - type the first few letters of the demo name and the selection will be restricted to demos that match. Very handy if you've got a really really long list to select from.
Comment