+1

And add the agent name in the extension history csv export too please. Or put it in the file name as you wish.

Yeah, either/both in the file name / csv file. Thanks!

I'd say an API with a static export to query out of makes more sense. But no matter, the only useful static exports we have is extension history and events.

Let me outline this one more time, given the last few patches the point just doesn't come across.

Dear devs, we have the dictionaries from the GBF. We can pull them out at will, so whatever the language, we can make sense of tokens. Tokens are unique, yet their translations aren't. So whenever we export something, we either don't know what they are (there's no unique identifier) or there's 3/4 tokens to choose from based on their ambiguous translation in exports of numerous items (not an ounce/gram of overestimation here). So please, just throw us an actual bone. Tokens, not their translations.

Here's my database so far, for those interested. It's slightly out-of-date, and there's a lot of guesses that is going to bite me in the *** when an official static dump is released. All easily solved by the suggested tweak.

http://dl.dropbox.com/u/7523665/perpetuum-doek.sql

Or beg for a real database dump..