diff options
| author | paramat <paramat@users.noreply.github.com> | 2017-06-22 06:50:22 +0100 |
|---|---|---|
| committer | paramat <mat.gregory@virginmedia.com> | 2017-06-26 04:38:36 +0100 |
| commit | 936d67dad4c4939c9f7c30f489d8bfc74f47fcaf (patch) | |
| tree | f9b5c51903572e2eafa7b4781a06768b1ed554db /doc/lua_api.txt | |
| parent | 1237206d4bdf840ae89018d14a0510035d54d0d3 (diff) | |
| download | minetest-936d67dad4c4939c9f7c30f489d8bfc74f47fcaf.tar.gz minetest-936d67dad4c4939c9f7c30f489d8bfc74f47fcaf.tar.bz2 minetest-936d67dad4c4939c9f7c30f489d8bfc74f47fcaf.zip | |
Ores: Make 'absheight' flag non-functional
The 'absheight' flag was added years ago for the floatlands of 'indev'
mapgen (now deleted). The feature mirrored all ore placement around y = 0
to place ores in floatlands.
In MTG we now use dedicated ore registrations for floatlands.
The feature is crude, inflexible, problematic and very rarely used, it
also makes ore vertical range code more complex.
Minetest 0.5 is a good chance to remove the feature.
The flag itself remains to not break flag values.
Diffstat (limited to 'doc/lua_api.txt')
| -rw-r--r-- | doc/lua_api.txt | 7 |
1 files changed, 1 insertions, 6 deletions
diff --git a/doc/lua_api.txt b/doc/lua_api.txt index 540bbe118..63d090ebe 100644 --- a/doc/lua_api.txt +++ b/doc/lua_api.txt @@ -1076,12 +1076,7 @@ Ore attributes See section "Flag Specifier Format". Currently supported flags: -`absheight`, `puff_cliffs`, `puff_additive_composition`. - -### `absheight` -Also produce this same ore between the height range of `-y_max` and `-y_min`. - -Useful for having ore in sky realms without having to duplicate ore entries. +`puff_cliffs`, `puff_additive_composition`. ### `puff_cliffs` If set, puff ore generation will not taper down large differences in displacement |