This fork keeps Azgaar's Fantasy Map Generator as the underlying project and adds two Windows convenience tools:
- 🛠️
Azgaar's Fantasy Map Generator.Bat— GUI installer, repair and uninstall tool ▶️ Start Azgaar's Fantasy Map Generator.Bat— optional standalone one-click launcher for starting the installed generator
The aim is simple: install and run the local version of Fantasy Map Generator with a few clicks instead of setting everything up manually through a terminal.
Double-click:
Azgaar's Fantasy Map Generator.Bat
This opens a Windows GUI setup wizard that guides you through installation.
- 🖱️ GUI installation wizard
- 📁 Lets you choose the installation directory
- 🟢 Automatically installs a local Node.js 24+ runtime
- 🔐 Verifies the Node.js download using SHA-256
- 📦 Automatically runs
npm install ▶️ Creates a reusable local launcher- 🔧 Repair installation
- 🗑️ Uninstall
- 🗺️ Preserves maps and common user assets during Repair
- 🚫 Does not install Node.js system-wide
The repository, Node.js runtime and npm dependencies are kept together inside the selected installation folder.
When the installer is run from a downloaded copy of this fork, it can install from those existing repository files. If the required project files are unavailable, the installer can download the original upstream Azgaar Fantasy Map Generator repository.
The installer uses the local Node.js runtime to install the required npm dependencies and runs the generator through npm run dev.
After installation, the installer automatically creates:
Run Azgaar's Fantasy Map Generator.bat
Simply double-click it to launch the map generator.
This fork also contains:
Start Azgaar's Fantasy Map Generator.Bat
This is a separate optional launcher and is not required for normal use. It can be separately downloaded from this fork and copied into the installed Fantasy Map Generator root folder, next to package.json.
It may be useful as an alternative or replacement launcher if the installer-created Run Azgaar's Fantasy Map Generator.bat is unavailable, deleted, damaged, or if the installation folder has been moved.
The Start launcher:
- 🔎 Checks that the Fantasy Map Generator installation is present
- 🟢 Uses the locally installed Node.js runtime
▶️ Runsnpm run dev- 🌐 Opens the generator in your default browser (You can also copy and paste the local host address to open the map generator in any browser after launch)
- 🚫 Does not require a system-wide Node.js installation
Keep the launcher window open while using the generator. Closing it stops the local development server.
If the installation has been moved, damaged or is missing its local Node.js runtime, run Azgaar's Fantasy Map Generator.Bat again and choose Repair.
Install once. Start with a double-click afterwards.
Made to make things easy for me, now sharing to make things easy for you.
The AonzOG Windows installer and launcher were created with assistance from GPT-5.6 Sol.
They have not undergone an independent security audit or comprehensive static and dynamic cybersecurity assessment.
Both helper tools are plain-text Batch/PowerShell code, so you can inspect what they do before running them.
The AonzOG Windows helper scripts are provided as-is and should be used at your own risk.
Azgaar's Fantasy Map Generator remains Azgaar's project and remains under its upstream MIT licence.
The AonzOG Windows helper files are separate additions to the fork.
Azgaar's Fantasy Map Generator.Bat and Start Azgaar's Fantasy Map Generator.Bat are released under The Unlicense. Feel free to use it, modify it, improve it or share it.
Azgaar's Fantasy Map Generator is a free web application that helps fantasy writers, game masters, and cartographers create and edit fantasy maps.
Link: azgaar.github.io/Fantasy-Map-Generator.
Refer to the project wiki for guidance. Development is tracked on the FMG dev board. Some details are covered in my old blog Fantasy Maps for fun and glory.
Join our Discord server and Reddit community to share your creations, discuss the Generator, suggest ideas and get the most recent updates.
Report bugs with the bug report form, suggest features in Ideas discussions, and ask usage questions in Q&A. Search existing reports first. For bugs, include your FMG version, browser/OS, reproduction steps and an affected .map file in a ZIP archive when relevant. For ideas, explain the problem and your use case.
In Discord, use #fmg-bugs or #fmg-suggestions; the assistant's /bug and /idea commands, when available, open forms for moderator review before GitHub submission. Asking the assistant a question does not file a report. See reporting instructions and examples.
Contact me via email for non-public suggestions. For performance problems, first check the performance tips.
You can support the project on Patreon.
Inspiration:
-
Martin O'Leary's Generating fantasy maps
-
Amit Patel's Polygonal Map Generation for Games
-
Scott Turner's Here Dragons Abound
Installers for Linux, Windows and macOS are attached to each release. Nix users can build the same app from the flake instead — see Install with Nix:
nix run github:Azgaar/Fantasy-Map-GeneratorPull requests are highly welcomed. The codebase is messy and I will appreciate if you start with minor changes. Check out the data model before contributing.
The codebase is gradually transitioning from vanilla JavaScript to TypeScript while maintaining compatibility with the existing generation pipeline and old .map user files.
The expected future architecture is based on a separation between world data, procedural generation, interactive editing, and rendering. The application is conceptually divided into four main layers: world data and styles (state), generators (model), editors (controllers), renderers (view).
Flow: settings → generators → world data → renderer UI → editors → world data → renderer.
The data layer must contain no logic and no rendering code. Generators implement the procedural world simulation. Editors implement interactive editing tools used by the user. They perform controlled mutations of the world state. Editors can be viewed as interactive generators. The renderer converts the world state into SVG or WebGl graphics. Renderer must be pure visualization step and not modify world data.