What is this?
LiBPoV is the Luanti Biome Point Visualizer, a tool for people who develop games and mods for Luanti. It allows them to visualize the heat and humidity points of biomes. It runs in your web browser using JavaScript.
Features
- Add the heat and humidity points of biomes
- Visualize the biomes on a Voronoi diagram
- Show biomes for given world coordinates only
- Modify the noise parameters of the heat and humidity Perlin noises used by the mapgen
- Visualize the biomes of the v6 mapgen in a special diagram
- Export to Lua, LiBPoV JSON and Amidst for Minetest biome profiles
- Import from LiBPoV JSON and Amidst for Minetest biome profiles
Quick reminder how biomes work
When Luanti generates the world, each (X, Z) coordinate is assigned a heat and humidity value (“heat” is also sometimes called “temperature”). Also, each biome is assigned a heat and humidity value as well. Heat and humidity act as coordinates on a 2-dimensional plane. For any world position, the biome that has a heat and humidity value that are closest to the heat and humidity will be used for that position. This happens for every position.
Luanti also may apply “blending” at the biome borders for a smoother transition, but this is ignored in LiBPoV.
The challenge for the developer is to figure out good heat and humidity points of custom biomes to make sure they are well-balanced. This is where this program will help you.
The v6 map generator is an exception: Here, biomes don’t have heat and humidity points. Instead, Luanti instead just checks if the world position’s heat and humidity lies between some (mostly) hardcoded values and then decides which of the hardcoded biomes to use.
Please refer to the official Luanti Lua API documentation for a more in-depth explanation.
Interpreting the diagram
On top of the page, you see the biome diagram. The horizontal axis represents heat and the vertical axis represents humidity. The visible diagram area represents all mathematically possible values. Note that the further you go from the center, the less likely they will become, with the area close to the border being extremely unlikely.
If enabled in the diagram view settings, the diagram may show the axes for heat and humidity. Each axis might either be a solid line or a dashed line. If solid, then the axis lies exactly on the 0-line. If dashed, the axis is not on the 0-line. This happens when the value 0 is either out of range or too close to the diagram border.
In “biome points” mode, the default value range of heat and humidity is from −37.5 to 137.5, with 50 as the midpoint. As a rule of thumb, most values will be somewhere between 0 and 100 by default.
In “v6 biomes” mode, the default value range is smaller. The value range may be changed by the noise parameters (which will be explained later).
Red dots represent the biome points (only in “biome points” mode), and they are labelled by their name. Dark green border lines represent the boundaries of Voronoi cells and the large colored areas represent the biomes themselves.
By default, a grid is displayed. A grid line is shown for every 10 units in “biome points” mode and 0.1 units in “v6 biomes” mode. Note: The grid lines may disappear if there would be too many of them.
Below the diagram, a couple of status information is shown: The current world coordinates (this is for biomes that could appear at these coordinates, applying min./max. X/Y/Z biome limits), the heat and humidity range of the current diagram and your cursor position (if it is on the diagram).
An example
Let’s say in the “biome points” mode there are 2 biomes at the (heat, humidity) coordinates (10, 10) and (90, 90). This will divide the diagram in 2 sections. Each of these sections is a Voronoi cell, or the set of all (heat, humidity) value pairs of that biome.
Let’s look what happens at position heat=0, humidity=0. If you read the diagram, you will see it belongs to the first biome. This means that whenever a world position has a heat of 0 and humidity of 0, that biome will be used. Now at heat=70, humidity=50, we can read it belongs to the second biome. And this is how you can understand this diagram.
Usage
This section explains how you can interact with the various parts of the program.
The interactive sections have a header with an arrow symbol at the beginning. Click on this arrow to collapse or extend a section.
Biome modes
Above the diagram, there are two buttons: “Biome points” and “v6 biomes”. These are the biome modes. Click on one of these buttons to change the biome mode. This affects the entire program.
In “biome points” mode, you can add, see and visualize heat and humidity points as well as the biome area on a diagram. This is the default mode. Biome points are used in all Luanti map generators except v6.
The “v6 biomes” mode displays the biomes of the v6 mapgen. The v6 biomes work completely differently and are hardcoded because this mapgen is very old. There are no biome points and your options to configure them are limited to a few settings only. You can’t add custom biomes here.
Diagram
Hover with the mouse cursor over the diagram to see the heat and humidity coordinates at this position.
When you hover the diagram, a small grabbing widget will appear in the bottom right corner. You can use this to resize the whole diagram. Hold down Shift while resizing to preserve the aspect ratio.
In “Biome points” mode, you can click on a point to select it, click on it again and hold down the mouse button to drag it. You can add a new point by double-clicking on the diagram, provided a click wouldn’t select an already selected point.
Biome configuration
You can configure the biomes here. This section differs on the selected biome mode.
“Biome points” mode
Here you can see a list of all currently active biomes. Each biome has a name of your choice. The program always starts with a default biome at (50, 50). Select a biome in the list so you can edit it.
The “Add” button adds a new biome with a random heat and humidity. “Remove” removes the currently selected biome.
Once you’ve selected a biome in the list, the fields in “Selected biome” will activate. Here, you can edit the selected biome’s heat and humidity point (corresponds to heat_point
and humidity_point
in the Lua API). You can also edit the minimum and maximum X/Y/Z positions this biome will be generated in (corresponds to min_pos
/max_pos
in the Lua biome definition).
Each biome has a name and a color which can be changed, too. These are only used for display purposes and don’t affect the calculations.
Changing a value in any of these fields will immediately take effect.
“v6 biomes” mode
In this mode you can configure a few settings of the v6 biomes. The “Flags” sections changes the v6-specific mapgen flags (on/off settings) and corresponds to the Luanti setting mgv6_spflags
. The Desert noise threshold corresponds to mgv6_freq_desert
.
These settings can be changed:
- snowbiomes: Activates the 5-biome system which introduces tundra and taiga. This will also force-enable jungles.
- jungles: Activates the jungle biome. This is only available if snowbiomes are disabled. Otherwise, jungles are force-enabled.
- Desert noise threshold (
mgv6_freq_desert
): Deserts will generate if the heat is above this value. This is only available if snowbiomes is off. If snowbiomes is on, the desert heat is fixed.
You can’t add any custom biomes.
Diagram view settings
These settings only affect the visual representation and not the data. The checkboxes can be used to hide several things in the diagram, like the grid.
The world position setting changes at which world coordinates (XYZ) the diagram “looks” at. The diagram will only show biomes that would generate at these coordinates, applying the biome’s Min./Max. X/Y/Z settings. In “v6 biomes” mode, the world position has no effect.
Note: If you hide the points, you can no longer select them in the diagram. You can still select them in the biome list, however.
Noise parameters
This is fairly advanced and most games don’t modify this. You can experiment with this if you want to see what happens if you use non-default heat and/or humidity Perlin noise parameters. The parenthesis if the Heat and Humidity sections show the name of the setting the noise parameters correspond to. The noise setting names depend on the current biome mode. The explanation of Perlin noises is out of scope for this document. See the Luanti Lua API documentation.
Changing the noise parameters has an effect on the possible value range for heat and humidity which has an effect on the probability of all biomes.
If your game or mod does not modify these noise parameters, you can ignore this section and leave it at default. Click on “Reset noise parameters” to reset them to the default if you accidentally changed them.
This section works mostly the same in both biome modes. But in “v6 biomes” mode, the humidity can never exceed 0.0 and 1.0. This is why you might not immediately see a change when you change the humidity noise in this mode.
Import
This is only available in “Biome points” mode.
This allows you to import biomes from text. There are two formats that can be imported:
LiBPoV JSON is LiBPoV’s native format that LiBPoV creates when exporting.
The Amidst for Minetest option imports from a biome profile from Amidst for Minetest. Biome profile files usually have the ending “.mt
”.
To use the import functionality, just paste the text in the text box and press the corresponding import button. This will replace all biomes. A message below the text box will tell you if the import has succeeded or failed. If the import has failed, nothing will happen.
To import biomes from an existing Luanti game, use the Luanti mod libpov_biome_exporter
. This prints the biomes of an existing Luanti game in LiBPoV JSON format to the console, from which you can copy it to the import text box. Refer to the README file of that mod for details.
Export
This is only available in “Biome points” mode.
This allows you to export the current biomes into text. You can choose to export them in one of various formats. Only biome information is included, not the noise parameters.
The LiBPoV JSON option exports the biomes in LiBPoV’s native format. It contains all the biome information that LiBPoV uses, including the biome color in the diagram, but not the noise parameters. You may want to copy this into a text file for later use.
The Lua export gives you a very basic Lua code that can be pasted into a Luanti mod. The code is very basic and does not include the “landscape materials”, like what the surface is made of (dirt, stone, sand, etc.). Biome coordinate limits (y_min
/y_max
or min_pos
/max_pos
) are added to the export only if they differ from the default values -31000 and 31000.
The Amidst for Minetest export gives you a biome profile you can use for Amidst for Minetest. The export does not include biome coordinate limits on the X and Z axis because those aren’t supported by that software at the time of this writing.
The “Clear” button clears the previous export.
Caveats / Limitations
In “biome points” mode, it is perfectly legal to have the biome points to be out of the bounds of the diagram. These out-of-bounds points are represented as arrows in the diagram. However, you can’t select them with your mouse on the diagram unless it’s close to the edge. Use the biome list to edit points that are out of bounds.
Heat/humidity values above 1,000,000 or below −1,000,000 are not supported and will trigger an error message. This is a much smaller range than what Luanti supports. Also, no diagram can be drawn if the heat or humidity noise scale equals 0 or is very small, although this is legal in Luanti. This does not mean that your chosen settings won’t work in Luanti, just that LiBPoV can’t visualize them.
Credits / License
LiBPoV is free software. See the License page for details.
Appendix
LiBPoV JSON format
LiBPoV uses JSON to import and export the biome points. For general information about JSON, see www.json.org. This section explains how this format is used by LiBPoV.
“LiBPoV JSON” is just normal JSON. The name “LiBPoV JSON” is used to clarify that LiBPoV is the intended use case for this JSON format. The reason for this name is because internally, the Amidst for Minetest biome profiles are also JSON-based, so we say “LiBPoV JSON” to avoid any confusion.
Definition
A LiBPoV JSON text is a JSON text that is an array of objects. Each object in that array represents a biome. Each of these objects must contain the following fields:
name
: Biome name (string). Same name as in Luaheat_point
: Heat point (number). Same name as in Luahumidity_point
: Humidity point (number). Same name as in Lua
Additionally, the object may optionally specify any of the following fields:
x_min
: Minimum X position of biome (number). Corresponds tomin_pos.x
in Luax_max
: Maximum X position of biome (number). Corresponds tomax_pos.x
in Luay_min
: Minimum Y position of biome (number). Corresponds tomin_pos.y
ory_min
in Luay_max
: Maximum Y position of biome (number). Corresponds tomax_pos.y
ory_max
in Luaz_min
: Minimum Z position of biome (number). Corresponds tomin_pos.z
in Luaz_max
: Maximum Z position of biome (number). Corresponds tomax_pos.z
in Luacolor_index
: A number that represents a color of the biome color palette, starting with 0. Used by LiBPoV to store the biome color in the diagram, otherwise meaningless. The number does not represent any particular color, only a palette index, as the palette might change in future.
If unspecified, the minimum/maximum position arguments default to -31000 (minimum) and 31000 (maximum). If color_index
is unspecified or is out of range, LiBPoV will pick a color index based on the position in the JSON array.