One note though, remember to clean out the export folder manually after each export if you do this. The export script assumes that the TileExport folder is empty before each export.

Are you one of my students?

To answer the original request, no, this forum doesn't have any built-in chat features or online indicators. It would take quite a bit of development effort to add something like that.

Never seen anything like that shrinking before.

As for the Large Exports, you can just edit the script file found in the annual folder (@Annual\Issue 129 - Large Exports) with notepad or similar. Near the very bottom of the file, there is this line:

RUNAPP @Annual\Issue 129 - Large Exports\tile.cmd

This is the line that calls that windows batch file that does the stiching and deleting of the output files. Simply remove this line from the script, and that batch file will never be called.

(An alternative is to edit the batch file and remove the commands you don't want, but I find it better to edit the script file as you can then have one copy of the script file with this line and one without so you can easily use it both ways)

A new set of maps integrated. This time I did @Royal Scribe's contest entries, along with some required intermediate overland maps and supporting maps.

Autosave deliberately save to a separate file to make sure to not accidentally overwrite your actual map file with what is perhaps unwanted changes, for example when testing things.. This is how autosave works in most software. I guess a more correct name would be "recovery save" or something like that, but autosave has just stuck in most software as the common term. It is not a replacement for manual saves, just an extra layer of security, so yes, you should always manually save before exiting. (Personally, I have autosave on, but the dialog off, so it autosaves silently in the background, which is what most other software does by default)