From Minetest Developer Wiki
Jump to: navigation, search


TODO in Minetest

Notice + Other Sources

Be aware that this may be biased towards whoever has had the time to update their thoughts here.

For another biased view about what to do next, see celeron55's roadmap on the forum. (At least you know who to blame if that is out of date.)

Things to do soon


  • Add configuration for DungeonGen
  • Add configuration for CaveGen

Mapgen V7

  • Get all biome definitions in!


  • Add L-system decoration support
  • Add cutoff handling



  • Figure out a permanent, elegant solution to the walled-in cave problem - can use is_ground_content now - does this belong in VoxelManipulator?


  • Figure out the thread priority mess
  • Assign thread affinities for a bit of a performance boost (reduce L2 cache misses)


  • Add double-click-to-move-inventory-to-chest support


  • Make a library for reading a Minetest map without worrying about the database used. (libmtmap?)
  • Add block tinting (grass, water, sky, etc.) (for biomes)
  • Add Fullbright option
  • Package more subgames in next release

Big, long term goals (Client)

Client-Side Scripting

Main article: Client_scripting_plans

* on_movement, on_punch, etc.
* key binding API

Client-Side Biomes

The server should transfer biome definitions to the client which calculates biomes locally. Crossing over into a new biome should trigger a client-side script callback Biomes have effects:

* Full scene post-effects (tint everything a different color)
* Temporarily override settings (cloud_height, enable_clouds, water_wave_height, water_wave_length, water_wave_speed)

Hardware Lighting for Light Sources


  • would allow variable light range and cutoff
  • would free up param1 of MapNodes to be used for storing more immediate node metadata (always a good thing!).
  • would allow colored light sources

Of course, can use dynamic lights, except they're very intensive and generally a scarce resource Dynamically generated lightmaps seem like a good way forward.
RealBadAngel is currently working on shader-based lighting. What strategy is he using?

Occlusion Culling/Occlusion Query

Irrlicht does support occlusion culling. If enabled, it culls scene nodes which are entirely out of the camera's view fulcrum.
Problem: The entire map is an Irrlicht scene node. Why? What was the rationale for this decision?
Solution: Make scene nodes per MapBlock.
While we're at it, playing around with scene nodes, it'd probably be a good idea to maintain two (or three) separate nodes for each MapBlock, one for each type of material. Opaque, transparent, and liquid drawtypes. This fixes the still unsolved material transparency problem.

Big, long term goals (Server)

Voxel Area Entities

How cool would it be to build a full-sized boat in Minetest, and then drive it around the ocean? That's one example of something that would be possible with this feature.
Voxel Area Entities are moveable ActiveObjects whose mesh and texture is user-modifiable via setting MapNodes in it. This is an extremely powerful feature, and while perhaps not of extreme difficulty to implement, there is very much to be done.
What needs to be done

  • A new derived SAO and CAO (they would need to be treated fundamentally differently), along with setNode() and removeNode() calls.
  • A derived VoxelManipulator class, perhaps called ObjectVoxelManipulator, which will be used to manipulate them.
  • These types of objects have meshes, and will need to be updated in MeshUpdateThread along with MapBlocks.
  • Some way to store these in the map. Perhaps these objects will get special non-block-ID keys in the map DB.
  • A decent way to serialize these objects. This detail in particular will require special attention.
  • For the previous two points, see for a discussion of a possible way to handle the objects.
  • Also see for user interface ideas,

Envlock Scope Reduction

Envlock needs to be put on a diet. Seriously. This is believed to be the primary reason for perceived unresponsiveness in Minetest - solving this would help matters immensely.
What needs to be done

  • Add a thin abstraction layer for atomic operation intrinsics.
  • Replace Environment operations that require concurrency but are simple enough with the said atomic operations and clever ordering.
  • Add a thread-safe hashtable structure to be used instead of std::map (or core::map) where locks would be needed, make use of this.
  • RCU for Map things - big structures such as MapBlocks could benefit from Read-Copy-Update for synchronization. This is the biggest change, but the reward would be immense.

Pre-generate world

What needs to be done

Add colorlike to node param types

Add a field like facedir, wallmounted, and liquidlike called colorlike that will allow the user to register a set of colors so that the color of some base node is modified on draw. This would save many node definitions.
This field would be (part of, at least) param2 in a MapNode. If colorlike is specified on its own, then it can define and use up to 256 colors. If used with facedir or wallmounted, then, it can only define and use 8 colors.
What needs to be done

  • Store a color LUT with the ContentFeatures for the defined node that is to be passed along from Lua when registering the node.
  • Figure out how to draw these colors in inventory screens and what not without having to prerender more textures
  • Bump ContentFeatures version

Rewrite falling code to C++

nodeupdate() now very slow and can't handle large amount of falling nodes. 100-1000 falling nodes now makes server very slow, 10000+ cause segfault. To test - make sand floating island via mapgen, touch it
What needs to be done
Rewrite in core with queue (like Map::transformLiquids)

Big protocol changes

There are several features that would probably bring benefits in the long term, but can't currently be merged because of network protocol incompatibility. That is, they either can't be implemented in a way that lets old clients connect to new servers and new clients to old servers, or it would be a major pain to do so. The point of this section is to list such features so that they can be merged at once: a one-time incompatibility, perhaps coinciding with the release of 0.5.0, is better than breaking compatibility all the time. Note: Not all of the things listed below need to be done, these are just ideas.

  • A binary key-value storage which easily supports missing fields with default values (e.g. header, source, usage)
  • Using TCP for reliable data transfer (e.g. tcp_connection)
  • Make the client request mapblocks (e.g. tcp_blocks_2)
  • Improved authentication and encryption
  • Remove old compatibility kludges.
  • Many command IDs have become obsolete in the protocol: they could be consolidated
  • Change builtin CONTENT_* to 0, 1, 2

TODO in Minetest Game

Things to do soon

Gameplay mechanics

  • Enderballs (or at least the teleportation aspect of it in something else). Throwing mod by PilzAdam has teleport arrows; use mese crystal fragments for teleportation?

Add things to surface

(so we do have something else than mining)

  • More trees. Not as a mod, nodes will be added on request if they are added to mapgen More Trees Mod
  • Convert Terasology's trees to minetest, they also use the L-system


  • Add more variants of each sound (4 sounds good).
  • Add hurt sounds and falling damage sounds (already supported by the engine).

See also

Personal tools