minenux
/
minenux
mirror of https://codeberg.org/minenux/minenux
1
0
Fork 0
Code Issues Releases Wiki Activity

tutorials - server - game.conf features and description usage

master
mckaygerhard 2023-07-10 22:05:10 +00:00
parent 6c0576f5cd
commit 683d14ad57
1 changed files with 22 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

23
tutorials/servers-howto-en.md
View File

@ -67,7 +67,7 @@ A minetest server need as minimun of 3 parameters to indicate: game id, config f
* **gameid** : a game itself is a directory with collection of mods that defines behaviour of the game, those * **gameid** : a game itself is a directory with collection of mods that defines behaviour of the game, those
will load the files inside mods directories, **Due we are assuming** `RUN_IN_PLACE` **they are located at** will load the files inside mods directories, **Due we are assuming** `RUN_IN_PLACE` **they are located at**
`/usr/local/minetest/games`, **and you must download under that path (generally as a unique directory)**, `/usr/local/minetest/games`, but if you are running as system wide, are located at `$HOME/.minetest/games`; **you must download under the games path (generally as a unique directory)**,
there are some famous: there are some famous:
* `minetest_game` is the default one.. download from https://github.com/minetest/minetest_game/tags * `minetest_game` is the default one.. download from https://github.com/minetest/minetest_game/tags
and must match the minetest version runing, is the most stable and basic to run. and must match the minetest version runing, is the most stable and basic to run.
@ -79,6 +79,23 @@ there are some famous:
for 0.4.X at https://github.com/davedevils/MineClone, since v0.51 are only for 5.X releases. for 0.4.X at https://github.com/davedevils/MineClone, since v0.51 are only for 5.X releases.
* `clonecrat` like the previous one but lighter, download at https://github.com/notanewbie/clonecraft_ZIP * `clonecrat` like the previous one but lighter, download at https://github.com/notanewbie/clonecraft_ZIP
but is a older development so use only for 0.4 releases but is a older development so use only for 0.4 releases
* **game.conf** : the config file that the server try to load over minetest.conf when the `game_id` loads.
* Loading path: it loads from the directory of the game that are currently loading.
* Contains paramteters to run the host:
* `title`: (Required), the name of the directory where game parts will be loaded
* `name`: (Deprecated) same as title, used for minetst from 0.X to 5.4 releases.
* `description`: Short description to be shown in the content tab, no more than 128 chars
* `allowed_mapgens = <comma-separated mapgens>` e.g `v5,v6,flat`, Mapgens not in this
list are removed from the list of mapgens for the game. If not specified, all mapgens are allowed.
* `disallowed_mapgens = <comma-separated mapgens>` e.g. `v6,flat` These mapgens are removed from the
list of mapgens for the game, allowed_mapgens is applied before disallowed_mapgens.
* `disabled_settings = <comma-separated settings>` e.g. `disabled_settings = enable_damage, creative_mode`
these settings are hidden for this game in the "Start game" tab and will be initialized as false when
the game is started. Prepend a setting name with an exclamation mark to initialize it to true (this does
not work for enable_server). Only these settings are supported: `enable_damage, creative_mode, enable_server`.
* `map_persistent`: Specifies whether newly created worlds should use a persistent map backend.
Defaults to true (= "sqlite3")
* `author`: The author of the game. It only appears when downloaded from ContentDB.
* **world** : a world itself, is a directory with collection of files for environment and/or building(s) and * **world** : a world itself, is a directory with collection of files for environment and/or building(s) and
all saved data associated with a world, **Due we are assuming** `RUN_IN_PLACE` **they are located at** all saved data associated with a world, **Due we are assuming** `RUN_IN_PLACE` **they are located at**
`/usr/local/minetest/worlds`, **and if not pointed in config will be loaded one named `world`** `/usr/local/minetest/worlds`, **and if not pointed in config will be loaded one named `world`**
@ -98,6 +115,10 @@ and the usage of the gameid of the world, you will now rarely need to edit minet
screen provide you a interface to confgure it all. This file is read every time the game starts and is always screen provide you a interface to confgure it all. This file is read every time the game starts and is always
created/modified when the menu quits. created/modified when the menu quits.
* Loading path: it loads from: * Loading path: it loads from:
* `/usr/local/minetest/games/<gameid>/minetest.conf` if you have system wide with `/usr/local` as prefix
and build the game with `RUN_IN_PLACE=0` (means it loads from the gameid directory of the game first)
* `$HOME/.minetest/games/<gameid>/minetest.conf` as second try if the game is running from user wide
and build the game with `RUN_IN_PLACE=0` (means it loads from the gameid user directory then)
* `../minetest.conf` if you are configuring build for `RUN_IN_PLACE=1` that means all the minetest * `../minetest.conf` if you are configuring build for `RUN_IN_PLACE=1` that means all the minetest
files are running from one place. files are running from one place.
* `../../minetest.conf` also, but will not write to it, if you are configuring build for `RUN_IN_PLACE=1` * `../../minetest.conf` also, but will not write to it, if you are configuring build for `RUN_IN_PLACE=1`