SaveGameManager should likely provide a method to retrieve the savefile path. The existing method to retrieve the directory name is meant to be used for logging purposes only (hence why it returns an absolute filesystem path), but for the use of tooling I can definitely endorse providing methods to query the savefile directory within the FileSystem API.

SaveGameManager should likely provide a method to retrieve the savefile path. The existing method to retrieve the directory name is meant to be used for logging purposes only (hence why it returns an absolute filesystem path), but for the use of tooling I can definitely endorse providing methods to query the savefile directory within the FileSystem API.

Small problem, this requires me to pull in SaveGameManager.cpp which brings with it Jobs, Game, etc and an expanding cloud of dependencies and problems to get savegamedump.exe to build.

Whereas this PR is currently quite a self contained change for a utility tool.

It's far more hassle than it's worth just so I can type filename intead of typing savefiles/filename

Hmm, yeah, good point. As-is, this is fine. I had originally required the use of the savegames/ prefix to support loading savefiles from anywhere within the user directory, but that's probably not a needed feature at all (in fact I've never used it once myself).