Home › 2025 Preview Release

2025 Preview Release

We’ve now progressed to a “beta” version.  This version requires a license key for the pro features. You can order a license in our store. 

Note this is still a “beta” so there may be bugs. If you think you may want to reopen a file in the pre-2025 version of Worldographer, make a copy of it first.  Worldographer won’t be able to open Worldographer 2025 files.

Planned Features

  • Other export options.
  • More room types in the Battlemat Rooms tab.
  • Cosmic maps create multiple planets in a system.

List of Known Issues

(An “X” in front means the issue is fixed but not yet released. “v1.##” means the issue is fixed in that numbered update.)

  • Allow generation of Empires/Nations on continent/kingdom maps?
  • “Dynamic” Terrain – a base tile, then features randomly placed above it.
  • Toolboxes (terrain, features, etc.) should remember their last location when reopened.
  • Paint bucket terrain fill isn’t working for non-terrain layers.
  • Some fonts don’t load.
  • “Dense” setting in city generation should do more to pack buildings into the center even on a sparse map.
  • Need to add offset selectors to Configure Terrain window.

Recent Fixes

Beta 1.03:

  • New Room Generator Room Type: Study.
  • Fixed formatting on the Generate Map Key dialog.
  • Coasts generate on their own layer.
  • Edit shape Help instructions are on the shape drawer/
  • Help menu has a Reset Properties (saved values like what checkboxes default on, favorite terrain, etc) menu item.
  • Can enter license key from initial “no license” dialog.

Beta 1.02:

  • Fixed bug with zooming when “Use Toolboxes” is on from the first time a map is created/opened.  This scrolling also affected selecting lines, features, etc.
  • World/Kingdom coast/empire/river/road/hex-crawl settings are now saved & reloaded.
  • Added a “schema” id to the save file data.  It starts at 1.0, and won’t be tied to the overall Worldographer version–it only increments when the file format changes.

Java Version

If you’re trying to use the Jar file to run the program, you’ll need some experience with Java or running programs from the command line.  We’re using version 21 of Java currently. We have now made this a “fat” jar so you don’t need to find and import outside libraries, but you will need to have the javafx “jmods”. The easiest way to do get them is to get a “full JRE” or “full JDK”–not the standard JRE or JDK that doesn’t include javafx.  We’re using Liberica which you can get here. Install that, and make sure your path is using that JRE or JDK for Java.

To run the Java version, you might be able to just double-click it to run it.  But it may not claim much memory by default (a limitation of Java) so to work with large maps (maybe over 1000×1000 tiles) you’d open a command line and type:

java -Xmx4G -Dprism.maxvran=3G -jar target\Worldographer-[version number].jar

You can substitute the 4G with another number of Gigabytes.  If using large hex maps that have more than 2000×2000 hexes (the size of each hex doesn’t matter) you’ll want 4 gigabytes or more, but it should be less than 3/4 of the memory on your computer. And because of the child map/multilevel map functionality, it is easy for the bottom (aka Province) level to be over 2000×2000 if you use the bottom level.)

The -Dprism.maxvram=3G option might not be 100% required, but is a good idea if you’re adding a large number of additional graphics. (Extra features, terrain, etc.)

If you also need to spell out the location of javafx because you downloaded it separately:

java -Xmx4G -Dprism.maxvram=3G –-module-path 'path to openjfx libs' –-add-modules javafx.controls,javafx.web,javafx.swing,javafx.graphics,javafx.fxml -jar 'worldographer jar file'