The kil stats table in the mission log for the border skirmish mission log is not displayed correctly.

The name column contains ~s for all rows, and the other columns are not lined up, i.e. the player name occurs in the wrong column.

Screenshots are available at http://imageshack.us/g/809/dump0001.png/

(also, the /dump command placed the screenshots in ~/.vendetta, not the first place I looked and I think it's not the regular place on linux to put files that the user is supposed to access?)

Thanks for the report! I just hotloaded a fix on the production server.

Personally, I think the game's own directory is the proper place to put them; would you suggest their home directory, or...?

It could be made customizable, with the default inside the game directory. Maybe the path option could even take a %character% variable, so that people could optionally have them automatically sorted by using something like "~/screenshots/vendetta/%character%".

Personally, I think the game's own directory is fine as well. Though i would probably go one step further and have them be in a screenshots directory under the vendetta directory, just like I'd rather see all of the various character specific files under the settings/<character> folder.

+1 to that as well. Too much clutter in there.

Thanks. A new skirmish yesterday (I think) was correct, the old ones are still funky but the log is probably stored statically (maybe even locally?). I'm sure I'll see some more tables tonight :-)

I always feel that the ~/.application directories are for 'internal state' or settings that the user is not supposed to access normally, hence the hidden directory... I have to say I don't mind too much, anyway, I don't think there's an official standard.

It would be helpful for noobs like me if it said "Screenshot stored as ~/.vendetta/dump001.png" instead of just "Screenshot stored as dump001.png"

The game saves screenshots into its current working directory and is the same code across all platforms. Having it say the full path of the file name is problematic due to the possibility of UTF8 (or other formats) characters somewhere in the path. VO doesn't handle UTF8 properly.

Heh. As part of my day job I program a document management and text analysis system for social scientists, so I know all about the evils of unicode...

Thanks for the extensive replies, and keep up the good work!