TODO

Things to do right away

Mapgen

• Put ores back in the core
• Separate generic functions, such as lighting updates and liquid updates, put them in the parent Mapgen class
• Remove duplicate and/or dead mapgen code
• Simplify terrain height calculation, perhaps cache results in an array
• Add jungles back in
• Add configuration for DungeonGen
• Add Lua callbacks for DungeonGen room placement

MapVoxelManipulator

• Figure out a permanent, elegant solution to the walled-in cave problem

EmergeThread

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

Liquid code

• Clean up the new finite liquid code a bit.

Big, long term goals

Lua MapVoxelManipulator Interface

Description
Practically any mod that is more complex than the little clicky thing on the end of ink pens would want to modify portions of the map. To do this, a minetest.env:set_node() call is required for each node to be modified. It does not take much imagination to arrive at the conclusion that the performance of these mods suffer accordingly, due to not only the inherent slowness of Lua, but the overhead of Lua-to-C calls, and the overhead of each Map::setNode() call. To make matters even worse, all this must be done within an envlock, leaving the rest of the server unresponsive while the Lua mods do their thing. Absolutely disgusting.
The answer is to give the Lua API the power of the ManualMapVoxelManipulator, so nodes may be retrieved or modified through a 3d array, and then blit (if necessary) back to the map.
What needs to be done

• The API for this needs to be well thought-out - no afterthoughts or hacky looking pieces.
• The central structure of the VoxelManipulator will be the data itself - a 3D array (in Lua, a table containing tables containing tables of MapNodes), or even better, just one huge array, leaving the modders responsible for finding the index within the array (the latter would surely improve performance).
• An API to simply read chunks of map to an array without any intentions of modifying it. An envlock would only be required when initially reading from the map to the VoxelManipulator.
• An API to read chunks of map, then blit back to the map when done. An envlock is required throughout the lifetime of the object (unless you're not concerned with the contents of the map being modified in between the mod doing so).
• An API to create a blank VoxelManipulator, perhaps filled with CONTENT_IGNORE, to which the mod sets only some blocks, and is blitted back to the map (CONTENT_IGNORE nodes aren't set, obviously). Here, an envlock would only be required when blitting back changes.

LuaJIT

Description
Lua is an interpreted scripting language. As such, it is slow. No, really. Much of the time, it feels like the problem of Lua's slowness is the elephant in the room being avoided by adding more and more API so the actual work is delegated to the core in C++. While some may argue that Lua mods are simply the dashboard to the car, and the core is well... the engine, it cannot be argued that the amount of work being deferred onto the core isn't much more than necessary.
What needs to be done

• Research LuaJIT. Find out how it fits in with the current Lua interpreter, what changes would need to be made, etc. Probably not too much.
• Real, substantial benchmarks. Some within the Minetest community have commented that LuaJIT has been tried before, but the performance increases "weren't worth it", and was therefore dumped - this may not be so. Regardless, even if the performance increase is minimal 'in most cases', it must be added to not neglect the subset of cases where the benefits would be much greater. Also, 'less than optimal' is unacceptable, especially if the work to make it optimal had already been done.
  

Annendum: Research has been done; LuaJIT is completely compatible with the Lua library itself, and can be used as a link-in replacement. At the same time, the LuaJIT website warns its users to treat it as a shared library only and not attempt to include it into the source tree.

Voxel Area Entities

Description
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.

Envlock Scope Reduction

Description
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.

Bar API

Description
A set of Lua API to maintain graphical bars representing various values on the client's interface. This would be the *right* way to more generally implement health, armor, breath, hunger, and XP.
What needs to be done

• Lua API to define the bars, remove, and set them.
• A general way to draw them (a la 'draw hearts' code in game.cpp, draw_hotbar())
• Some sane boundaries so bars cannot be arbitrarily drawn all over the screen and overwrite other UI elements.

New network packets, to be sent from the server to the client:

• Add bar (bar identifier, name of texture for bar elements, title, initial value, et cetera.)
• Remove bar (bar identifier)
• Set bar value (bar identifier, new value). Happens on a Lua defined-event (someone gets hit and takes damage, or w/e).

SSE/AVX Perlin Noise

Description
Calculation of perlin noise maps are embarassingly parallel. Using SSE or AVX for the gradient map methods will speed up computations by a factor of 4 or 8. This is not needed anytime soon, as perlin noise is very cheap currently.
What needs to be done

• Finish implementing it
• Test
• Do the same for NEON on arm

Mapgen V7

Description
The highly anticipated, next-generation biome-based map generator, what more is there to say?
This "big feature" has a higher priority than the others, since it is mostly done already and is in high demand from the Minetest community.
What needs to be done

• Make water occur in all biomes when terrain height is below water_level, instead of only in an ocean or lake biome
• Increase the number of octaves for biome perlin noises, create the fast flood fill algorithm, fill in any interior biome bubbles
• Simplify biome selection (perhaps remove the biome group selector nonsense?)
• Find a way to smooth height transitions between biomes (look to Minecraft for inspiration)
• Add DecorationDef. (Doesn't this fit in with the current work on ores?).
• Perhaps, vary terrain height's perlin noise parameters by perlin noise (is this possible with the current perlin noise map functions?!).
• Figure out how to use 2d perlin noise to generate ridges on cliffs, or perhaps 2d noise to form the walls of cliffs... hrmmm...
• Nether and aether biomes.

Mapgen V5

Description
Revival of the 3d perlin noise-based generator that produced excellent looking terrain. Used to be very slow, which is the reason why it was ultimately dumped for V6 - this is no longer a problem with the new perlin noise map functions, which are insanely fast. celeron55 specifically requested to be the one to do this.
What needs to be done

• Class-ify the V5 mapgen code. Create noise objects and handle parameters in the constructor, destroy noise objects in the destructor.
• Replace all NoiseBuffer calls with array accesses to the 3d noise result array
• Replace lighting and liquid updates with calls to the parent Mapgen class' updateLiquid() and updateLighting(). Replace cave, dungeon, and tree generation with the appropriate generalized calls too.
• Overall code cleanup would be nice in addition.

Pre-generate world

Description
What needs to be done

Store block differences only

Description
Instead of storing everything in the database, only store the changed mapblocks (or even only modified nodes?). This would save a lot of space. What needs to be done

• Change the mapblock saving code to only save modified blocks.
• Change the mapblock loading code to mapgen, and then load changed blocks.

TODO in minetest_game

Gameplay mechanics

• Beds? Need to think about this one more.
• Enderballs (or at least the teleportation aspect of it in something else).

Add new ores

• Diamond, silver, gold - their utility should be much like what they have in Minecraft.
• Ruby, sapphire, emerald, lapis lazuli? - perhaps find more utility for these than in Minecraft.
• Copper? - need to find uses for this first, perhaps craft bronze?

Add new craftables

• Smoothstone half-block tiles.
• All Mese gear instead of only pickaxe, along with diamond versions.

Add in a couple mobs?!?

• No: too laggy at current.

Add things to surface

(so we do have something else than mining)

• Farming.
• More trees.
• Cacti/papyrus growing.

Sounds

Collect some (not annoying) sounds from somewere and add them in.

• a sound pack would be good

ne