FOSS gamedev and creative worlds

Maybe the developers could add registered ores to a registered_ores table just like nodes.

Ores are already quite easy to setup and spawn in a world...

Thank you for the reply but that's not what I'm saying. They should add ores to a global table like they do for nodes. For example:

minetest.registered_ores

Still not merged: Save registered ores in a table, as is done with biomes.

Thank you for linking that. I had no clue it existed. Maybe this thread will bring it to their attention again. It's easier to use this table than to make a table and try to add support for many mods that add ores. I made this topic because I forked gloopblocks so when flowing water comes in contact with source lava random ores or stone is generated.

+1, +2, +3 and even more…

+1

I'm working on a LUA mapgen.
Of course, I want to add ores.
The problem is : I can't use the registered ores because, as you say, this table don't exist.
I have to redefine all of them myself. Not handy, and not "clean" because in this case my mapgen will not be compatible with ore mods like Calinou's Moreores.

Could you merge it, please ?
I really need it.

+1

Maybe you should commit out the duplicate biome registration. Maybe it will get merged sooner.

Gael de Sailly wrote:+1, +2, +3 and even more…

+1 +2 +3 +4 +5 +6 +7 ............. = -1/12

:P

Wikipedia Article

lol

rubenwardy wrote:

Gael de Sailly wrote:+1, +2, +3 and even more…

+1 +2 +3 +4 +5 +6 +7 ............. = -1/12

:P

Wikipedia Article

Half-life 3 confirmed !

Since I'm currently in the process of writing a mapgen, this is definitely something I support.

That said, I'd suggest a different way of describing where the ores should be placed. Mods which add ores generally should be mapgen-agnostic. This means that they should work just as well in a world made of floating islands or a giant maze as they do in the normal world. The current system of specifying maximum y coordinate, cluster size, etc, only really works with a normal world, and even then it restricts what mapgens can do when generating ores.

Instead, I propose a system more like that used by LaTeX and other markup languages. The ore definition should specify the gameplay purpose of the ore, while the precise implementation details should be left to the mapgen. For example, coal is essential in the early game and is required in large quantities. Iron is also required in the early game, but shouldn't be quite as abundant. Gold and mese are both late game ores, but mese is generally more useful than gold. With this knowledge a mapgen could easily determine where to place the ores and in what quantities, regardless of how unusual or insane the map topography is. Maybe in a floating islands map mese should only be found on high-altitude islands which are difficult to reach, or in a labyrinth the gold might be guarded by more dangerous traps.

I like the idea. +1

It was added. YES!!! https://github.com/minetest/minetest/co ... 6956275a5c

Came here to post it but you beat me :)

:) I'm glad people can use it now. It's been about two month since I first wanted this. I guess it's been longer than that for other people.

Really happy that it's now merged.

Another good new for mapgen modders : minetest.generate_ores, added last Sunday by kwolekr. I've not tested it yet, but looks handy and useful.