Okay, this took a little longer than planned. I had "things to do" (*) and a couple of technical glitches(**), but here's a link to a replacement JAR file
to try (visit the link and click on "Java_and_JAR_Files", then right-click the JAR file and save it).
(*) "Things to do" means the wife had some chores for me that I couldn't put off.
(**) "Technical glitches" involves code changes elsewhere in MT that caused exceptions when I enabled this code and did preliminary testing. Nothing major, but annoying because I hadn't been keeping these patches up to date.
The code related to importing and exporting individual maps is hidden inside a "development" section of the code. This means that without the proper command line option, this JAR file will work exactly like the maptool-1.3.b63.jar
that is in the downloadable ZIP. But with
the proper command line option you'll have two new menu options on the Map
menu: Import Map...
and Export Map...
To enable the import/export menu functions:
1. Download and unzip the 1.3.b63
version of MapTool into a new directory.
2. Replace the maptool-1.3.b63.jar
file with the one described above.
3. Edit one of the .BAT scripts and add -DMAPTOOL_DEV=true
4. Execute the modified .BAT script.
If you want to test this out, copy one of your campaigns to a new filename (I wouldn't want to risk something bad happening to an in-progress campaign!). Execute the new JAR as described above and load the campaign. (I suggest using the largest memory size that your OS will support for Java, since this gives you the most room for loading/saving maps and will minimize "out of memory" errors.)
Now try the Map -> Export Map...
menu option and save the map. It will receive the .rpmap
filename extension. You can immediately import the same map if you like, but it will come in with the same name that it had when it was saved, so you may want to rename the current map first. When you're all done goofing around, save the campaign. It will be saved with "1.3.b63" as the version of MapTool so you will need at least that version to read the campaign file.
Now try using your original version of MT 1.3.b63 to open the campaign. Play around with it a lot
(!) and make sure both the original maps and the imported maps don't have any strange problems related to campaign properties, token properties/macros, VBL, and so on.
Particular problems: nothing is done about tokens with an invalid Property Type (such as "D&D3.5" used by tokens on the map when that property type doesn't exist in the campaign), tokens with Lights that don't match those defined in the campaign, and so on. I do
reset some fields: last path, ownerList is emptied, and sight type is set to "Normal". I expect fields which are NOT reset WILL cause some kind of problem, but it may not show up right away.
BE CAREFUL BEFORE USING THE NEWLY SAVED CAMPAIGN FOR A LIVE GAME! And be sure to keep copies of previous campaigns as backups. THIS IS VERY ALPHA and you are hereby warned the campaign could be screwed up, hence the need for backups.
Good luck, and please report your results. Did it work for you? If not, what can I do to recreate the problem? Note that no attempt is made to convert property types. The macros on the existing tokens should be preserved, but I'm not that familiar with the macro handling code and there might be more needed...