Engine/Basic data structures

IRC logs on this subject

http://2pktfkt.de/irc/minetest-delta/2011-11-07.html http://2pktfkt.de/irc/minetest-delta/2011-11-08.html

Links are down. See Copy of #minetest-delta 2011-11 log

For the log dating 2011-11-07, the subject discussion starts at the end.

Node

A node in Minetest is the equivalent of a block in Minecraft. They are the cubes that make up the world.

In code, a node (represented by the class MapNode) contains only a small amount of data that can be transferred easily between the client and the server. This data includes what type of node it is, eg. Dirt node or Sand node, and some other data for lighting and miscellaneous parameters.

Nodes don't have any interactive functionality, this is done by the client and the client knows what to do depending on what type of node it is.

Block

A block (MapBlock) in Minetest, is a collection of 16x16x16 nodes (described above), and they are the pieces that together make the world/map.

In code, the block (represented by the class MapBlock) contains one mesh (only client-side) for all 16x16x16 nodes. A mesh is the geometry of an object, in this case the block. A mesh contains a collection of materials aka. textures, which is how each node is represented visually.

Map

The Map (class Map) stores MapBlocks and works as an abstraction layer for the MapBlocks, allowing the users of Map to see the world as a consistent bunch of MapNodes.

Map also knows how to load and save MapBlocks.

It also contains functionality for lighting and liquid updates.

VoxelManipulator

The VoxelManipulator is an object that stores arbitary areas from the Map, for transferring into other threads and allowing faster node access than the Map does.