Difference between revisions of "Games/Minetest Game"

From Minetest Wiki
Jump to navigation Jump to search
m (Wuzzy moved page Games/Minetest to Games/Minetest Game: Was officially renamed)
m (Wuzzy moved page Games/Minetest Game to Subgames/Minetest Game: Parent page is called “Subgames”)
(No difference)

Revision as of 14:49, 11 October 2015

Minetest Game
Minetest logo.png
A game
Game Type Default
Author Minetest developers
Latest version 0.4.13
Forum topic 9724
Source code GitHub


Minetest Game (previously called “minetest_game”) is a subgame which is installed by default. It is mostly a big sandbox and therefore there are no goals.

Function

As default game

Minetest Game is included by default to give some initial single player content when Minetest is downloaded in the single archive file from the download section of the homepage. It includes some basic mods that add enough game content to offer a simple playable game. Control keys and basic gameplay activities are set to function similar to other games of the genre to make immediate playing possible.

Minetest Game is not needed to play on other servers as all game content is controlled and "served" by the hosting server. Only when running an own Minetest server is some playable content needed that is normally a collection of mod scripts in a “game” folder. “Single-player” may be viewed as a special case when the local Minetest program acts as local game-server, hosting a local game and then connects to its own self as client.

As basis for new games

The gameplay can be modified considerably by Lua scripts organized in mods. As a lot of mods, offered by the community, name “default” as dependency, Minetest Game is thought as the basic content on which game designers may build their own games. Thus if compatibility with most mods is the aim of a new game, it is advisable to start building the new game by adding content to a copy of Minetest Game.

As collection of modding examples

Although this may seem trivial this function of the Minetest game should not be forgotten as it often offers the first example of how to code things for modders.


0.4.9-Branch

Since early 2014, Minetest Game (then called “minetest_game”) was semi-officially under feature freeze. It was not dropped and was kept available in maintenance-mode as basis for all mods that depended on "default". The consensus of the Minetest developers seemed to be that Minetest Game should be changed as little as possible[1] (feature-freeze) and rather no new content added. Thus offering the most compatibility to old mods and leaving the bulk of game content for game designers to develop.

Notable things not included

As Minetest Game was included in the download archive it was supposed to be lightweight and as gameplay-neutral as possible. It therefore often irritated new players that many things known from similar games were not included by default.

Although it offered rails, it did not include mine carts, boats or any other vehicles as such.

No mobs[2] or NPCs were included and no API for these was offered.


0.4.10-Branch

With the release of 0.4.10, Minetet Game Minetest-NeXt was merged[3] with Minetest Game.

Content

It containes the following mods:

Future development

To give more examples of the possibilities of the Minetest engine it had been discussed to include more example games in the download archive. The only other game that was included in the 0.4.9 versions of Minetest was Minimal, which is only recommended for testing purposes. Games suggested as example games[4] have been Dwarves, PilzTest, Nostalgia, Realtest, Eden or a game based on the Ethereal mod. More recently BFD, Minetest NeXt and Carbone have been considered among others. The idea is to showcase a variety of different gameplay, environment and atmosphere concepts.


Notes and References

  1. "Minetest Game will no longer be developed" thread on the Minetest forum.
  2. Though rats might just be able to sneak in if you are not carefull ;-).
  3. "(0.4.10) NeXt merged / Updated minetest_game" thread on the Minetest forum.
  4. as discussed on IRC at 2013-10-17