diff --git a/.github/CONTRIBUTING.md b/.github/CONTRIBUTING.md index 715e51c4ab..0abde91d32 100644 --- a/.github/CONTRIBUTING.md +++ b/.github/CONTRIBUTING.md @@ -109,6 +109,8 @@ translated by editing a `.tr` text file. See If you'd like to monetarily support Minetest development, you can find donation methods on [our website](https://www.minetest.net/get-involved/#donate). + + # Maintaining * This is a concise version of the diff --git a/doc/client_lua_api.md b/doc/client_lua_api.md index 5bfa961c94..1f62c3ed95 100644 --- a/doc/client_lua_api.md +++ b/doc/client_lua_api.md @@ -881,6 +881,8 @@ It can be created via `Raycast(pos1, pos2, objects, liquids)` or * `next()`: returns a `pointed_thing` with exact pointing location * Returns the next thing pointed by the ray or nil. + + # Definitions * `minetest.get_node_def(nodename)` diff --git a/doc/world_format.md b/doc/world_format.md index 5843cd0997..d2e3130f88 100644 --- a/doc/world_format.md +++ b/doc/world_format.md @@ -12,6 +12,8 @@ The block serialization version does not fully specify every aspect of this format; if compliance with this format is to be checked, it needs to be done by detecting if the files and data indeed follows it. + + # Files Everything is contained in a directory, the name of which is freeform, but @@ -180,6 +182,8 @@ For `load_mod_`, the possible values are: redis_port = 6379 - (optional) Connection port redis_password = hunter2 - (optional) Server password + + # Player File Format Should be pretty self-explanatory. @@ -248,6 +252,8 @@ Example content: EndInventoryList EndInventory + + # Map File Format Minetest maps consist of `MapBlock`s, chunks of 16x16x16 nodes. @@ -330,6 +336,8 @@ The blob is the data that would have otherwise gone into the file. See below for description. + + # MapBlock Serialization Format > **Notes**: @@ -508,6 +516,8 @@ Before map format version 29: End of File (EOF). + + # Format of Nodes A node is composed of the `u8` fields `param0`, `param1` and `param2`. @@ -522,10 +532,14 @@ Since map format version 24: The purpose of `param1` and `param2` depend on the definition of the node. + + # Name-ID-Mapping The mapping maps node content IDs to node names. + + # Node Metadata Format (Before Map Format Version 23) The node metadata is serialized depending on the `type_id` field. @@ -565,6 +579,8 @@ The node metadata is serialized depending on the `type_id` field. * `u8[len]` `owner` * serialized inventory + + # Static Objects Static objects are persistent freely moving objects in the world. @@ -588,6 +604,8 @@ Since protocol version 37: * `s32` pitch * 1000 * `s32` roll * 1000 + + # Itemstring Format Examples: @@ -603,6 +621,8 @@ Older formats: The wear value in tools is 0...65535. + + # Inventory Serialization Format * The inventory serialization format is line-based.