Biome support in the API

[PilzAdam]

Hello everyone!
I think it would be great if there where some functions in the API that mods can define biomes.
Here are some ideas how these functions could look like:

Code: Select all

minetest.register_biome("desert", {
    rarity = 0.1,
    stone_like_node = "default:desert_stone",
    dirt_like_node = "default:default:desert_sand",
    dirt_with_grass_like_node = "default:desert_sand",
    generate_trees = true,
    tree_rarity = 0.01,
    leaves_like_node = "air",
    tree_like_node = "default:cactus",
}

This is an example for the desert biome.
There should be also a global table that cotains all definitions ordered by name:

Code: Select all

minetest.registered_biomes

If this would be implemented into upstream, the API would be much more powerful and mod creators could create variet maps.
Please post what you think about it and what you would add/remove to the functions.

[jin_xi]

i agree, this would be great. but i think some more degrees of control would be good, esp for placement of biomes.

[PilzAdam]

Another idea: In minetest.register_on_generated() there should be the biome as one param:

Code: Select all

minetest.register_on_generated(minp, maxp, seed, biome)

"biome" should contain the name of the biome or a table with all biomes in that block.
So the mod developers can check if they are in a desert and create some oasis there.

[Topywo]

Good idea.

Would it also be possible to let the mod makers use more 'like' nodes and use other than the minetest_game mods?

For example:
stone_like_node = "default:desert_stone",
stone_like_node_a = "modmakersmod:granite"

[BrandonReese]

Good idea.

Would it also be possible to let the mod makers use more 'like' nodes and use other than the minetest_game mods?

For example:
stone_like_node = "default:desert_stone",
stone_like_node_a = "modmakersmod:granite"

for something like that it would be better to make stone_like_node an array

stone_like_node = { 'default:desert_stone','modmakersmod:granite' }

In the biome definition should it include a size range. So you could make the desert biome rare, but you could make it very large. If it's just rare it could end up being small too.

[PilzAdam]

Another idea: Different types of trees.
New fields in the definition table:

Code: Select all

tree_small = true,
tree_medium = true,
tree_big = false,

[kotolegokot]

This is very great idea! I have some amendments. I think trees must be generated separately. I mean it must be generated by minetest.register_on_generated function. Also, we need function, that get biome name from position. Example: minetest.env:get_biome_name(pos).

[PilzAdam]

Also, we need function, that get biome name from position. Example: minetest.env:get_biome_name(pos).

I already had the idea to pass the biome to minetest.register_on_generated(). But this would be cool too, to use it in abms.

[PilzAdam]

2 new ideas:
1) A new layer above_dirt (for snow biomes)
2) Some params to control the mapgen (e.g. high mountains or flat).

[OdnetninI]

I think the same that you, we need more control of mapgen (like mines). +3

[sky]

I like this biome idea i can make a jungle biome a snow biome and plains biome if it will work

[PilzAdam]

Maybe textures that depend on the biome would be nice. When you place a grass block in a swamp biome it looks different than in a grass biome.

[jmf]

A height parameter would be nice, so for example snow biomes are only generated at great heights.

[0gb.us]

Maybe textures that depend on the biome would be nice. When you place a grass block in a swamp biome it looks different than in a grass biome.

That sounds like it would requite work on the client side.

Or on the server side, it could be implemented as a separate node that gets switched in.