Finally, we can call this a true map editor. I'm sure there are still some features that would be nice to have, but I think I've taken this editor far enough to be genuinely useful to those with a basic or better modding skill level.

• Terrain painting, including water->land or land->water (see known issues below)
• Basic terrain morphing (raise/lower terrain, leveling)
• Movement/rotation of module_parties.py objects for settlement and bridge changes (requires module system know-how)
• Multiple rendering modes and a brand new native user interface
• Basic vertex editing (it'll be tedious for huge changes, but this will let you do things like smooth out a coastline or fix up land features to look nicer)
• Updated rendering engine libraries (so anyone who had issues running the previous version may have better luck this time--hopefully, including Win10 support)
• A config.ini file to customize a few things like window size/position, and the names of files used to load/save (1.0 release includes camera range limit configuration, for better support of huge maps)
• Window resizing & maximization added

Patches:
1.0.1 - Should fix a crash when moving settlements for users in countries which format numbers using "," (comma) where others use "." (period). Java version requirement has also increased to Java 11, and the size of the editor download has been cut in half. However, for this release the download size is actually larger, since I decided to bundle the old 1.0 version (which is better tested) along with 1.0.1, just in case there are new issues. Be sure to follow the Java update instructions below to update Java, if you're upgrading.
1.1 - Semi-functional Viking Conquest support. Not all icons are working (missing ones will use a placeholder), and the ones that do show have bad textures, but the crashes and other major issues seem to be resolved. Support is not "well" tested yet, and should be considered experimental. Also, improved logging has been added.
1.1.1 - Minor update in an attempt to improve VC support. I suspect there are still some major issues with parsing, reading/writing module_parties.py, however. Since I don't have time to re-write the editor's file parsing for compatibility, I think it's best if anyone using this for VC edits their module_parties file manually, using the changes saved in exportModuleParties.py that editor outputs as a guide. (Or, just get things like screen coordinates right out of the UI.)
1.1.2 - Added a (technically misnamed) option to change the UI buttons used for terrain painting into a scrolling list. Open config.ini and set the appropriate line to true (replace "false") to enable this at startup. Useful for low resolution screens where this panel gets cut off. Default is to show the buttons, since they seem to work a bit better (I had to click multiple times occasionally on this experimental scroll-list, otherwise it seems to work fine).
1.1.3 - Increased decimal precision for map vertex output to 6 digits, somehow this was only 2 before but the normal maps go to 6.

A few different rendering modes:
-M&B style (emulates the game's appearance as close as possible--or at least, as close as I can get it)
-Blended "simple" textures (designed to show terrain type, with blending, to approximate how terrain weights interact visually)
-Non-blended terrain faces (designed to show terrain type without blending, useful for painting mountain terrain and presumably determining what type of battlefield type a particular area will utilize)

At startup, the editor looks for the map and module_parties files (map.txt and module_parties.py by default in config.ini). There are default files provided, but if you're modifying an existing mod obviously you'll need to point the editor at those files instead. The config.ini file also lets you specify save/export filenames. Be sure to save often and back up your important work.

To run, extract the zip file and either run the .bat file or click on the .jar file to execute as runnable jar (for this to work you have to have .jar files set to open with javaw.exe).
You must have a recent Java 11 runtime installed. Minimum version is Java 11 or higher.
You can get this at https://adoptopenjdk.net, make sure to select OpenJDK 11 (or later).

The following direct link should work for most people (modern Windows users):
https://github.com/AdoptOpenJDK/openjdk11-binaries/releases/download/jdk-11.0.3%2B7/OpenJDK11U-jre_x64_windows_hotspot_11.0.3_7.msi

Camera navigation: use WASD keys to move, mouse wheel to change camera height (similar to how the game's camera works). Also Numpad +/- will change the camera's angle. Holding shift down while using WASD movement keys makes the camera move faster. Note that the Numpad +/- keys used for changing camera angle are NOT used for terrain altitude adjustments (those are the -/+ keys near Backspace).

Windows Support / Win10 Support
I run Linux these days, so I've no idea how this runs on any Windows version. Hopefully there won't be issues, but we'll work to resolve those if they turn up. Also I have a pretty powerful system here, so it's possible there could be performance issues on low-midrange hardware. Lightweight laptops don't do so well.

Viking Conquest Support
Unfortunately it doesn't look like this works with this map out of the box, but it might not be too hard to adapt it. Issues seem to be camera movement range limits and probably settlement graphics/module_parties support, which is obviously different from Warband. See release notes for an improved (but not quite perfect) support update.

Known Issues

• There are some visual gitches when reshaping coastlines that would be a little tricky to automatically eliminate. See tips for workaround.
• Clicking Load Exported Map when there isn't a map file to load (exportMap.txt by default) will crash the editor.
• There are some visual-only glitches sometimes, but they don't appear to corrupt the actual map file itself. If the glitch is resolved by clicking Export followed by a Load of the exported map, there shouldn't be a problem.
• While there are some usability issues, I don't know of any which are really bad.
• Camera rotation - this is a tricky one to implement and something I don't feel very motivated to work on. If you're good with 3D math, Quaternions, and Java and you want to fix it that badly, maybe we can fix this one up...

Tips

• As always, save-save-save often, and keep backups of your files at major milestones if you're doing large projects. Testing is difficult and I can't guarantee something won't go wrong.
• When reshaping coastlines, re-loading your map after terrain painting changes will apply proper blending. To do this conveniently you can click the Export Map to M&B Format button and then the Load Exported Map button (which reloads that same file immediately).
• Recommend clicking Export Map to M&B Format after first startup to ensure that the editor doesn't crash by accidentally clicking Load Exported Map (unless you don't mind the risk of losing changes you've made...)
• Non-Blended Terrain mode (radio button at top) is your friend. With M&B mode it's easy to miss a poly (triangle/face) when painting, and that can have a big impact on things, especially when painting mountains or coastlines. Non-Blended mode lets you see what you're doing much more clearly.
• Mountain terrain is weighted very weakly in order to simulate how the game renders mountains. In other words, you'll need to paint a larger area in order for mountain terrain to really show up visually because the other terrain types have a higher priority. So if it seems like mountain terrain doesn't show up, keep trying--it does work. It'll probably be much easier to "paint" mountain terrain in non-blended terrain mode.

Let me know on the forum thread if there's any issues. I don't really monitor comments on this page too much. See the 'home' link under the ratings for the thread link.