Minetest is a free open-source voxel game engine with easy modding and game creation.

Copyright (C) 2010-2022 Perttu Ahola celeron55@gmail.com and contributors (see source file comments and the version control log)

1. Further Documentation
2. Default Controls
3. Paths
4. Configuration File
5. Command-line Options
6. Compiling
7. Docker
8. Version Scheme

• Website: https://minetest.net/
• Wiki: https://wiki.minetest.net/
• Developer wiki: https://dev.minetest.net/
• Forum: https://forum.minetest.net/
• GitHub: https://github.com/minetest/minetest/
• doc/ directory of source distribution

All controls are re-bindable using settings. Some can be changed in the key config dialog in the settings tab.

Locations:

• bin - Compiled binaries
• share - Distributed read-only data
• user - User-created modifiable data

Where each location is on each platform:

• Windows .zip / RUN_IN_PLACE source:
  • bin = bin
  • share = .
  • user = .
• Windows installed:
  • bin = C:\Program Files\Minetest\bin (Depends on the install location)
  • share = C:\Program Files\Minetest (Depends on the install location)
  • user = %APPDATA%\Minetest or %MINETEST_USER_PATH%
• Linux installed:
  • bin = /usr/bin
  • share = /usr/share/minetest
  • user = ~/.minetest or $MINETEST_USER_PATH
• macOS:
  • bin = Contents/MacOS
  • share = Contents/Resources
  • user = Contents/User or ~/Library/Application Support/minetest or $MINETEST_USER_PATH

Worlds can be found as separate folders in: user/worlds/

• Default location: user/minetest.conf
• This file is created by closing Minetest for the first time.
• A specific file can be specified on the command line: --config <path-to-file>
• A run-in-place build will look for the configuration file in location_of_exe/../minetest.conf and also location_of_exe/../../minetest.conf

• Use --help

• Compiling on GNU/Linux
• Compiling on Windows
• Compiling on MacOS

• Developing minetestserver with Docker

We provide Minetest server Docker images using the GitLab mirror registry.

Images are built on each commit and available using the following tag scheme:

• registry.gitlab.com/minetest/minetest/server:latest (latest build)
• registry.gitlab.com/minetest/minetest/server:<branch/tag> (current branch or current tag)
• registry.gitlab.com/minetest/minetest/server:<commit-id> (current commit id)

If you want to test it on a Docker server you can easily run:

sudo docker run registry.gitlab.com/minetest/minetest/server:<docker tag>

If you want to use it in a production environment you should use volumes bound to the Docker host to persist data and modify the configuration:

sudo docker create -v /home/minetest/data/:/var/lib/minetest/ -v /home/minetest/conf/:/etc/minetest/ registry.gitlab.com/minetest/minetest/server:master

Data will be written to /home/minetest/data on the host, and configuration will be read from /home/minetest/conf/minetest.conf.

Note: If you don't understand the previous commands please read the official Docker documentation before use.

You can also host your Minetest server inside a Kubernetes cluster. See our example implementation in misc/kubernetes.yml.

We use major.minor.patch since 5.0.0-dev. Prior to that we used 0.major.minor.

• Major is incremented when the release contains breaking changes, all other numbers are set to 0.
• Minor is incremented when the release contains new non-breaking features, patch is set to 0.
• Patch is incremented when the release only contains bugfixes and very minor/trivial features considered necessary.

Since 5.0.0-dev and 0.4.17-dev, the dev notation refers to the next release, i.e.: 5.0.0-dev is the development version leading to 5.0.0. Prior to that we used previous_version-dev.