Describe the bug
If I edit the heightmap in "risk" mode and then immediately click "Exit Customization", all rivers are re-generated, and all custom rivers are removed.
I understand that determining what should happen with the rivers after changing the heightmap is difficult. However, I had not expected all rivers to change regardless of what I do. If this is intended, then I think the message should be changed to indicate that rivers will be regenerated regardless.
My use case is that I have a map on which I have removed all default rivers and added a few important rivers myself. The exact locations of those rivers are important for my map. To be quite frank, I don't care if rivers suddenly go up a mountain because of my heightmap changes; the locations are more important for me, because sometimes rivers should follow borders.
Steps to reproduce
- Load FMG in a fresh browser session. A random map with default settings should now generate.
- Go to "Tools".
- In the "Tools" window, under "Edit", click "Rivers".
- In the "Rivers Overview" window, click "Remove all rivers". Confirm by clicking "Remove".
- In the "Tools" window, under "Add", click "Rivers".
- Click anywhere on land.
- In the "Rivers Overview" window, check the name of the single river that now exists. Remember this name.
- In the "Tools" window, under "Edit", click "Heightmap".
- In the "Edit Heightmap" window, click "Risk".
- In the bottom-right, click "Exit Customization".
- In the "Tools" window, under "Edit", click "Rivers".
- Compare the list of rivers with what you saw in step 7.
Expected behavior
Some old rivers are removed, some are altered, and some remain unchanged. No rivers are added.
Actual behaviour
All old rivers are removed, and all rivers are generated from scratch.
.map file
Lania 2026-03-19-22-59.map.zip
System
- Version: v1.113.6
- Browser: Firefox 140.8.0esr (64-bit)
- OS: Linux Debian 12 stable
Describe the bug
If I edit the heightmap in "risk" mode and then immediately click "Exit Customization", all rivers are re-generated, and all custom rivers are removed.
I understand that determining what should happen with the rivers after changing the heightmap is difficult. However, I had not expected all rivers to change regardless of what I do. If this is intended, then I think the message should be changed to indicate that rivers will be regenerated regardless.
My use case is that I have a map on which I have removed all default rivers and added a few important rivers myself. The exact locations of those rivers are important for my map. To be quite frank, I don't care if rivers suddenly go up a mountain because of my heightmap changes; the locations are more important for me, because sometimes rivers should follow borders.
Steps to reproduce
Expected behavior
Some old rivers are removed, some are altered, and some remain unchanged. No rivers are added.
Actual behaviour
All old rivers are removed, and all rivers are generated from scratch.
.map file
Lania 2026-03-19-22-59.map.zip
System