Difference between revisions of "Engine/Basic data structures"
Hybrid Dog (talk | contribs) (→Node) |
Hybrid Dog (talk | contribs) (→Node) |
||
| Line 14: | Line 14: | ||
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. | 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. | ||
| − | Special nodes are [http://wiki.minetest.net/Ignore ignore] and [http://wiki.minetest.net/Air air]. They can not be [[minetest. | + | Special nodes are [http://wiki.minetest.net/Ignore ignore] and [http://wiki.minetest.net/Air air]. They can not be [[minetest.override_item| overridden]].<br/> |
Where map is not generated, there's ignore. [[minetest.get_node]] gives ignore also if the map is not loaded, so to get the node in unloaded chunks you can use [[vmanip]].<br/> | Where map is not generated, there's ignore. [[minetest.get_node]] gives ignore also if the map is not loaded, so to get the node in unloaded chunks you can use [[vmanip]].<br/> | ||
air is set when a node is [[minetest.remove_node| removed]], for the player it's nothing. | air is set when a node is [[minetest.remove_node| removed]], for the player it's nothing. | ||
Revision as of 15:06, 28 February 2017
IRC logs on this subject
minetest-delta/2011-11-07 minetest-delta/2011-11-08
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.
Special nodes are ignore and air. They can not be overridden.
Where map is not generated, there's ignore. minetest.get_node gives ignore also if the map is not loaded, so to get the node in unloaded chunks you can use vmanip.
air is set when a node is removed, for the player it's nothing.
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.
mapchunk
A mapchunk in Minetest is a collection of 5x5x5 MapBlocks (described above), and each time map generates, another mapchunk appears.
See minetest.register_on_generated
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 arbitrary areas from the Map, for transferring into other threads and allowing faster node access than the Map does.