Minetest is the former name of Luanti, an engine for playing and creating games built from voxel blocks. It does not install one official campaign or one fixed set of crafting rules. A game package defines the objects, map generation and progression, while the engine handles rendering, input, networking and content installation. This distinction explains why two Minetest worlds can feel like unrelated games.
A game comes first
The first launch directs the player to install a game before creating a single-player world. ContentDB sits inside the client and lists games, mods and texture packs. After choosing a game, the player creates a world with that game and a selected map generator.
Deleting or replacing a game package can make its worlds impossible to open correctly because the world depends on that content. A game update can also change item names or behavior. Copying the world directory before a large content change preserves a return point.
Worlds choose mods
Installing a mod does not activate it everywhere. Minetest keeps a separate mod selection for each world. The player selects the world, opens its configuration and enables the intended packages. A modpack groups related mods but still permits control over its members.
This per-world design prevents a new package from silently changing every save, yet it adds a common setup trap: the content can appear in the installed list while nothing changes during play. The active world must use a compatible game, and that world must enable the mod.
Servers carry rules
A multiplayer server chooses its game, mod set and player privileges. Server-side mods arrive through the connection, so joining does not require the player to install the same packages manually. The server list shows the game identity, and an in-game command can list active mods when the server permits it.
An account name on a public server belongs to that server, not to one universal Minetest account. A blank password may work where the host permits it, but another person can then claim or damage that player identity. Setting a password protects the name on that server.
Movement needs permission
Normal movement uses the familiar keyboard and mouse pattern, while block use and placement share the right mouse button. Holding Shift while placing avoids opening an interactive block such as a chest. The inventory, chat and console have separate shortcuts.
Fast movement, flight and noclip require server privileges. Pressing the configured shortcut without the matching privilege does not grant the ability. Some movement modes have no shortcut by default because they can confuse new players, and a server can restrict the minimap or zoom even when the client shows a control for it.
Mobile loses controls
The touchscreen interface maps mining, placement and movement to taps and on-screen areas. Official documentation describes mobile control as more restricted than PC control. A physical gamepad also needs an external binding program rather than direct complete support.
That difference matters on servers or games that depend on many shortcuts. A desktop player can bind extra actions, open the console and reach debugging displays that a mobile player cannot use in the same way. The underlying world remains compatible, but the interaction range changes with the client.
Mods can alter saves
Minetest normally sandboxes mods, but mods still have permission to change world data through the game API. Removing a mod can leave unknown nodes or missing items in an existing save. The documentation therefore recommends regular world-folder backups when adding mods.
Manual packages require the correct user-data directory and start disabled. ContentDB reduces that file-placement work and lets the client install compatible content, but it does not guarantee that every combination of mods will agree. Testing additions on a copy of a world reveals conflicts without risking the main save.
