by Poikilos
ENLIVEN is a subgame for minetest with the goals of providing immersion and lessons for humanity.
ENLIVEN is a work in progress, but the goals are:
The EnlivenMinetest project (a.k.a. ENLIVEN project) includes tools for installing, building, and maintaining (such as developer scripts) the ENLIVEN and Minetest (engine) itself.
The official game server (world) is called center (or "Center of the Sun"). The address and port for that and other worlds are listed at minetest.io.
To better understand what the Issues section covers, see Project Status below.
For notes on current development discussions, see the "Work in Progress" section.
If you build ENLIVEN yourself, you may be able to get it working with several versions of Minetest but probably not ones from the .net site. Bucket_Game from minetest.org is now the basis, so Final Minetest and Finetest (and probably MultiCraft 2 on which Finetest is based) are the targets for game compatibility.
Q: What is included?
A: The installer includes the Minetest engine, the ENLIVEN "game" (Lua mods) and configuration file(s). ENLIVEN tries to emphasize Minetest as an engine, whereas ENLIVEN is the game. One way this approach improves the user experience is that ENLIVEN includes minetest.conf settings that should probably be default. For example, tone mapping and other graphical improvements that are basically universal to gaming and intuitively expected (such as is clear from vision biology in the case of tone mapping).
The EnlivenMinetest repo has tools for:
Q: "Why not make it compatible with versions from the .net site to get [feature x]?"
A: The Minetest 5 (.net site) core devs have decided to reduce compatibility and be the tail wagging the dog, not the many people who enjoy or used to enjoy making mods and games. If you want to be associated with that team, you are free to use their software. This project is for single player and people who want to play games with our community at minetest.io and the Final Minetest engine community minetest.org. MultiCraft (and hence Finetest) aimed for dual compatibility with MT4 and MT5 but successive versions of 5.x even hindered that (as predicted here) by breaking mod (and network protocol) compatibility multiple times. It doesn't just harm dozens or perhaps hundreds of mods, but also harms and increases development and maintenance cost for the many copies of those mods in games, and for the many copies of those games on servers and those for single-player use. When the API is changed, the problem isn't in x number of mods, it is in that times the number of games, times the number of servers (often customized further), and all of those innumerable people have to make up for the tail trying to wag the dog, or all that work simply gets discarded if they are unavailable or unwilling to make up for it and perform all of that work that is redundant (or doubly redundant in the case of servers). See also:
The following subprojects were moved to other repos for clarity and better git practices:
The Issues page
of the repo's web interface is used to track issues in ENLIVEN, the
Center of the Sun server that uses it, Bucket_Game on which it is
based, and Final Minetest which runs it. In many cases the issues are
upstream and fixes can lead to pull requests, or resolve issues that
are ignored or tagged as wontfix upstream. In several cases the
upstream mod related to the issue is no longer maintained or only works
with backward compatibility present in Final Minetest or MultiCraft2
code.
However, this project has led to upstream improvements.
Several patches here have been accepted to upstream mods, such as:
or proposed such as:
or rejected for unspecified reasons :), such as:
or I'm uncredited for unspecified reasons :), such as:
In some cases I may use maintained versions of unmaintained mods or ones where I have differences of direction such as:
Or new mods, such as:
You can apply whatever patches here you want (if applicable), but they are already in ENLIVEN (at least if you build it, otherwise the old installer may not have the latest changes). Most of the patches are also in Bucket_Game. The newest build script uses Bucket_Game as a content database. It has specific goals that make it small (such as in node definition count) in comparison to Bucket_Game.
There are several improvements I may implement in new or existing mods. See the Issues section of the GitHub project.
Disable or remove these Bucket_Game mods/features potentially (not matching theme):
This project is mostly for building ENLIVEN, but there are some scripts here to help build the engine as well: See doc/building-minetest.md.
run-any is a shim to run binaries (instead of compile) in VSCode. The
purpose is:
run-any will use it to
convert paths in Lua tracebacks to clickable paths. For example:
...../games/ENLIVEN/mods/coderfood/unified_foods/hunger.lua:342: in function .../home/user/minetest/games/ENLIVEN/mods/coderfood/unified_foods/hunger.lua:342: in function ...
(If paths including working directory are set correctly such as in
code-workspace if using VSCode)run-any works outside of VSCode), try sudo ld-config & see:
run-any may require outputinspector such as if the main
function is moved to a submodule there.(configuring the build of ELIVEN [the mod set only, not binaries])
You can place zero or more of the following variables in
$HOME/.config/EnlivenMinetest/scripting.rc:
CUSTOM_SCRIPTS_PATH
MT_POST_INSTALL_SCRIPT_2 # relative to CUSTOM_SCRIPTS_PATH
REPO_PATH # Set this if your copy of the repo is not ~/git/EnlivenMinetest
ENABLE_CLIENT # =true if you want install-mts.sh to install the client.ENABLE_CLIENT=trueYou can place a script called mts.sh in your home (or
CUSTOM_SCRIPTS_PATH) directory to run it after install (you can put
archive-minetestserver-debug.sh there too to run first). A suggested use
is to put a line in mts.sh that starts the server, so that the server
starts after the installation or upgrade is complete.
Click "Releases" for the installer, which has the singleplayer and multiplayer client for ENLIVEN.
For Linux servers, place the "ENLIVEN" directory from "Releases" into your "games" directory in minetest if you have a run-in-place version. If not, place it in ~/.minetest/games/. For what Minetest versions are compatible, see the first part of this document.
change_world_name_manually_first and
its subfolders, change the values of the variables in the folder name
as noted before using.enable_local_map_saving = true, which will cache the world locally
on their machines. You can feel free to change that according to your
preference.See changelog.md.
Authors: poikilos (Jake Gustafson) ENLIVEN project (aka EnlivenMinetest), including launcher (ENLIVEN application) and ENLIVEN subgame, is released under the LGPL v2.1 license (see LICENSE), except media which is released under the CC BY-SA 3.0 license (see LICENSE). There are other exceptions to this license and authorship where specified below and in subfolders. Source code is available at https://github.com/Poikilos/EnlivenMinetest.
Minetest is included with releases--for Minetest license, please read README.txt in Minetest's doc folder which is provided in releases.
(changed by EnlivenMinetest project)
For future plans and how you can contribute or build the game (Lua) or package (Lua+engine+conf) see doc/development.md and issues.
This section is a temporary dev discussion record for the purpose of tracking meta (issues about issues). In other words, this section has version-specific points that clarify reasoning such as prioritization, difficulty, or impact of issues or solutions. It may clarify why some issues are undecided, need feedback, are lowered in priority (such as via "Bucket_Game-future", "non-trivial"), etc.
On 1/14/22 3:13 AM, Robert Kiraly wrote: (except changed 0 to # so GitHub creates links to issue pages)
497 RJK could fix this but he has questions. TBD.
498 RJK could fix this but he has questions. TBD.
510 Poikilos needs to review next snapshot first
511 Poikilos needs to review next snapshot first
512 Doable but TBD
516 Poikilos needs to review next snapshot first
523 Q. Oily Patch: Can you put the patch in the ENI?
[see next e-mail below]
530 Q. Is the fix to modify the images or the models?
Modifying the models would be complicated. They were never designed to align with the pixels on different resolutions. This may require lots of model editing or image editing to use mobile-sized textures. The problem is that even if you make some edges right, the pixel, at a low res, may be shared with another face. We could try reverting to the old higher resolution then upscaling instead of downscaling and see if the pixels line up, and if not then hand editing would work since there would be enough pixels that they aren't used twice on more than one polygon. I can try it.
On 1/22/22 3:21 AM, Robert Kiraly wrote:
(except added # so GitHub creates links to issue pages)
- ENI #486 Dye shapes:
So, this is a simple incorrect-images issue. I'd thought that it might be the dingy-colors issue.
Poikilos said: The actual images are in bucket_game/mods/codercore/dye/textures and either aren't all used by the dye mod code or unifieddyes reverts them to its image. The latter is probably the case. It is probably best to revert the images there to the ones in the dye mod in..."
I follow that we can just change the images. However, I'm not certain of what "there" refers to. I assume that you mean "unifieddyes". Are you able to provide a patch?
<Poikilos> there: bucket_game/mods/codercore/dye/textures
<Poikilos> I'll provide a patch. A good compromise would be to to some resizing and editing to make a better dye pile rather than reverting the nice bowls to the 16x16 MTG dye piles. The patch would also have to cover unifieddyes since that seems to override some of them since they aren't uniform. In any case, dye and unifieddyes images should be uniform anyway.
- ENI #487 Revert a change:
Are you able to provide a patch relative to the latest snapshot that does the revert?
<Poikilos> Ok can do.
Issues where discussion was requested by RJK:
Issues where discussion was requested by Poikilos:
On 1/10/22 6:31 PM, Jake Gustafson wrote:
<OldCoder>0517 Animal Materials: Should we just factor the mod out?Factoring it out would be like factoring out default or basic_materials. Factoring it out would make several mods much more complex to maintain. Such mods exist for good reasons: See my comments at the two links ...
Issues deferred pending a previous issue but ready to address:
On 1/10/22 6:31 PM, Jake Gustafson wrote:
<OldCoder>0510 Animal materials<OldCoder>0511 Meat<OldCoder>0516 Meat<Poikilos>510-511 & 516: I'm waiting on incremental change so I don't desync from you (same reasons as under 0508 above, including my suggestion to add animalmaterials).
Issues deferred pending a current issue:
See also:
(This section provides out-of-context copypasta lines that have no meaning relevant to this document except to prevent retyping them over and over)
This is resolved in bucket_game snapshot 220114.