FOSS gamedev and creative worlds

I had a quick idea today.

Basically, it'd work similarly to npm, but for Minetest. You could install mods, subgames, texture packs, utilities and maybe maps with it. It could work directly using Git or from archives. It could be made to handle dependencies automatically, too.

You could invoke it from a terminal using a command like mpm (with subcommands help, search, install, update, remove, …).

For this to work well, modders, subgame developers and texture pack developers might have to add a package.json file which would contain version information and other metadata.

This is a great idea! That is, if it would me integrated with mmdb.

For some users, we'll still need a graphical installer as they might be afraid of a blinking cursor.

It'd be great if mmdb could get usable again. A mod installer which is integrated into the game is far more helpful for most players. It just doesn't really work right now, and it does need categories. Perhaps it could interface with the installer you've got in mind?

I'm a fan of this idea, but simply because I love npm. :P

Minetest mods can already use mod.conf to specify their name, this could be expanded for descriptions and author name.

Within the last week, iqualfragile, the main mmdb developer, has identified the problem and emailed a list of instructions to thexyz. Hopefully it will be resolved in a matter of days, rather than a few more months to wait.

rubenwardy wrote:Minetest mods can already use mod.conf to specify their name, this could be expanded for descriptions and author name....

Might be usefull if you also explain that in your manual at "Mod folder". As suggestion for good style for example.
Maybe also with an addition to what characters to avoid in the mod name and the danger of name-space clashes as is recently happening with the severall "mobs" mods around.

i like the idea with the package.json file.
this could contain the dependencies and so the dependence.txt file gets obsolet.
it could contian, if its a normal mod or a modpack, so the modpack.txt gets obsolet.
it could also contain a mod description, so the description.txt file gets obsolet.
it could contain the modname, so mod.conf gets obsolet.

a json file can also read by the mod database, minetest itself or a npm (or just mod manager :-) ) wich can download, update, and delete the mods.
for that there have to be some additional information, eg. version number, and where to check for new versions, type of archive etc.

I hope something like that will in minetest!