#Minetest net mod

I spent the majority of my limited server maintenance time fixing other people’s mods (usually broken by ’s API changes on GitHub) and creating software to maintain the server, such as mass inventory editing and mass mod updating. I chose to use the git version since I am a developer and the server was not public, similar to why a mechanic may own a “fixer-upper.” However, I got in over my head and eventually had to be careful about updates and backups. As a contributor and server owner during this entire period (also going back to 0.4.13-git on the same server), I concur with that (at least since 0.5 on /minetest/minetest) is in technically-defined “fork” status (regardless of lack of “administrative,” or stated, fork status).įor over two years or so I ran a Minetest server owned by a high school, using the git (GitHub) version ’s Minetest 5.0.0 (previously called 0.5). The current release, 5.0.1, is administratively marked stable but doesn’t even have a recipe for stairs.

They even backported some of the breaking changes into 0.4.17 (and possibly earlier “stable” versions, see below). I can vouch for the fact that the 5.0.0 (originally 0.5) branch introduced many breaking changes, regardless of how administratively labels it. Expectedly, each site explains the issue differently. and both claim to be the stable branch of Minetest, similar to the FFmpeg vs.

Minetest net