From c8ac4dfd3279a9d30c768ac4b12ad345c858784b Mon Sep 17 00:00:00 2001 From: rubenwardy Date: Tue, 8 Aug 2017 20:23:12 +0100 Subject: [PATCH] Update lua_api.html, add requirements.txt --- lua_api.html | 932 ++++++++++++++++++++++++++++++++--------------- requirements.txt | 2 + 2 files changed, 636 insertions(+), 298 deletions(-) create mode 100644 requirements.txt diff --git a/lua_api.html b/lua_api.html index 62ff994..c2c6302 100644 --- a/lua_api.html +++ b/lua_api.html @@ -4,10 +4,11 @@ layout: default ---

This is lua_api.txt nicely formated: I did not write this

-This page was last updated 23/April/2017.
See doc/lua_api.txt for the latest version (in plaintext).
Generated using a Python script.
+This page was last updated 08/August/2017.
See doc/lua_api.txt for the latest version (in plaintext).
Generated using a Python script.

Table of Contents

*_optional drawtypes need less rendering time if deactivated (always client side).

Node boxes

@@ -1096,19 +1257,20 @@ This results in smooth, rolling noise. Disable this (noeased) for s If no flags are specified (or defaults is), 2D noise is eased and 3D noise is not eased.

absvalue

Accumulates the absolute value of each noise gradient result.

-

Noise parameters format example for 2D or 3D perlin noise or perlin noise maps: - np_terrain = { - offset = 0, - scale = 1, - spread = {x=500, y=500, z=500}, - seed = 571347, - octaves = 5, - persist = 0.63, - lacunarity = 2.0, - flags = "defaults, absvalue" - } - ^ A single noise parameter table can be used to get 2D or 3D noise, - when getting 2D noise spread.z is ignored.

+

Noise parameters format example for 2D or 3D perlin noise or perlin noise maps:

+
np_terrain = {
+    offset = 0,
+    scale = 1,
+    spread = {x=500, y=500, z=500},
+    seed = 571347,
+    octaves = 5,
+    persist = 0.63,
+    lacunarity = 2.0,
+    flags = "defaults, absvalue"
+}
+^ A single noise parameter table can be used to get 2D or 3D noise,
+  when getting 2D noise spread.z is ignored.
+

Ore types

These tell in what manner the ore is generated.

All default ores are of the uniformly-distributed scatter type.

@@ -1163,14 +1325,12 @@ to small changes. The following is a decent set of parameters to work from:

}, noise_threshold = 1.6 -

WARNING: Use this ore type very sparingly since it is ~200x more +

WARNING: Use this ore type very sparingly since it is ~200x more computationally expensive than any other ore.

Ore attributes

See section "Flag Specifier Format".

-

Currently supported flags: absheight

-

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.

+

Currently supported flags: +puff_cliffs, puff_additive_composition.

puff_cliffs

If set, puff ore generation will not taper down large differences in displacement when approaching the edge of a puff. This flag has no effect for ore types other @@ -1211,12 +1371,14 @@ in the form of a table. This table specifies the following fields:

  • #force_place: boolean representing if the node should forcibly overwrite any previous contents (default: false)
    • -

    About probability values: - A probability value of 0 or 1 means that node will never appear (0% chance). - A probability value of 254 or 255 means the node will always appear (100% chance). -* If the probability value p is greater than 1, then there is a +

    About probability values:

    +

    Schematic attributes

    See section "Flag Specifier Format".

    Currently supported flags: place_center_x, place_center_y, place_center_z, @@ -1338,15 +1500,28 @@ is present, mapped to a boolean of any value, the specified flag is unset.

    things according to tool_capabilities.
  • #Craftitem (register_craftitem): A miscellaneous item.
    • +

    Amount and wear

    +

    All item stacks have an amount between 0 to 65535. It is 1 by +default. Tool item stacks can not have an amount greater than 1.

    +

    Tools use a wear (=damage) value ranging from 0 to 65535. The +value 0 is the default and used is for unworn tools. The values +1 to 65535 are used for worn tools, where a higher value stands for +a higher wear. Non-tools always have a wear value of 0.

    Item formats

    Items and item stacks can exist in three formats: Serializes, table format and ItemStack.

    Serialized

    -

    This is called "stackstring" or "itemstring":

    +

    This is called "stackstring" or "itemstring". It is a simple string with +1-3 components: the full item identifier, an optional amount and an optional +wear value. Syntax:

    +
    <identifier> [<amount>[ <wear>]]
+
    +

    Examples:

    Table format

    Examples:

    @@ -1422,17 +1597,20 @@ effective towards.

    Special groups