ASK KEVS JAHAHAAHAHAHAHAHAHAHAHAHAHAHAHAHAHAHAHAH

lmao wupZ

i mean programmatic demo analysis. sorry this wasn't clear.

I don't know the answer, but why do you want to do this?

i'm working on a project that would benefit from taking some information from demos. i created a demo parser for warsow a few years ago, but there was a lot of plaintext information that made it simple. afaik ql demos are encrypted, and unfortunately the source isn't available.

maybe i can look at wolfcam source? but i'm not sure where to start.

i think this would be a time effective way to regulate my duel games; in comparison to the pro's. since, i think i roam the map helplessly, it would be great to see distance travelled, if i can be bothered.

Contact myT, as he's been working on reading demo data for years, or you can check for the uber demo tool directly. Code is available.

http://www.tilion.org.uk/2011/11/quake-3-demo-format/

Something like this? I think the phrase you're looking for is "quake demo parsing/parser".

Also there is source code available that would probably be hugely beneficial -

http://sourceforge.net/projects/wolfcamql/
(mostly complete dm_90 support)

https://code.google.com/p/uberdemotools/source/checkout
(supports dm_90)

http://sourceforge.net/p/qldt/code/ci/master/tree/
(sadly no one's ever updated it for dm_90 support)

yeah, i've been taking a general look at wolfcamql for the past 20 minutes or so, but not in a position to do anything really thorough atm. hopefully somebody familiar with wolfcamql can maybe point out some critical files that would give a head start on where to look for what's necessary to start parsing demo data.

qldt and udt both have some kind of auto 'cut by event' options, you'd probably be better off there at a guess.

The stuff in wolfcam is mostly (entirely?) simply actually reading the demo headers and running the packets through the quake engine rather than parsing it for collective info, I don't know really though I've never really done anything with wolfcam other than watch demos.

http://www.qldemos.com used to have all of that until the site went down and the owner disappeared. Maybe you can contact him somehow through the youtube channel https://www.youtube.com/user/quakelivedemos

does anybody know how qlranks handles weapon statistics? do they somehow have access to shots fired & shots hit?

Your shots fired/hit are visible in your quake live profile on the statistics page (hover over accuracy).

ah, thanks. unfortunately unavailable per match.

If you are using chrome install Tampermonkey extension and then https://raw.githubusercontent.com/Lamieur/QL/...ts.user.js and then you will see shots fired/hit (hover over accuracy) at any match.

Bit ironic this came up today as I posted this just a few hours earlier, slightly modified version of that script if for some crazy reason you want to see cg/ng stuff in match stats too :

http://www.quakelive.com/forum/showthread.php...post311046

thanks. this may be a huge help in getting things moving initially. it might even be the better option.

too bad there is no info about taken YA/RA/MH and weapons (for TDM).
lazy fuckers from id.