... minus the cursor of course. (oops)
Personally I'm thinking something like a console command like:
":mapshot <size> (<f/p>) ... "
- mapshot: would take care of the needed cam-settings. (top-down view, rotation zero (ie: same orientation as minimap), no perspective (or as little as possible), ....)
- <size>: some value relating to the output image size.
-- <f/p>: ... perhaps optional "Full-map" vs "Player-map" setting. (perhaps with an additional trailing objects-bool setting)
--- (No output filespec input. Not needed in my view ... it usually only gets in the way. Outputting some datetime stamped files works better.) (... Upload to HnH server only, )
I know, just a day-dream of mine that not going to happen. (for whatever reason/excuse)
---
Follow up electric dream.
Output Filename:
in case of custom clients, which already output mini-map tiles, a related coordinate file naming might be a potential option.
Should make merging hi-res-maps almost as easy as merging mini-map tiles. (depending on the used software of course)