FOSS gamedev and creative worlds

Something that could be useful for lots of mods would be a softdepends.txt file in the mod folder: mods that are listed in it are loaded before the mod if they exist, but else, they are ignored.

You can use lua to check wheter a certain mod is installed and change your script's behaviour:


I don't think that a softdepend.txt is needed.

Yes it is, because we sometimes want to execute the code after the other mod in that case (for example in the older versions of mesecons, or if we want to call code in the other mod). Of course, the mod will still call that to know if it should run the code.

webdesigner97 wrote:You can use lua to check wheter a certain mod is installed and change your script's behaviour:

Your phone or window isn't wide enough to display the code box. If it's a phone, try rotating it to landscape mode.

Code: Select all

 if minetest.get_modpath("streets") then
  print("Streets is installed")
 else
  print("Streets isn't installed")
 end


I don't think that a softdepend.txt is needed.

I don't think that is reliable at 'load time' since it appears that mods load in a particular order (probably ascii). Consequently mod 'A' may not be able to detect the presence of mod 'B' until both mods are loaded.

Edit, actually modpath should be still readable, I am thinking of using function calls or static data from other mods.

Please ignore..

Yes. This would be nice. OR, a way to register a callback that will be made once a named mod is loaded (or called immediately if it is already loaded, or called never if it isn't present). This would eliminate the possibility of introducing circular dependencies where A tries to load after B and B tries to load after A (or A -> B -> C -> A or even more complicated patterns) although it would also require slightly more event-driven thinking. For example, here is how a pair of mods might look with a soft dependency loading order:



and here is how it might look with a mod loaded callback:



There are two things worth noting about that example:

• aCallback may never be called, or may be called right away if mod A is already loaded, so mod B needs to be designed so that either order would work.
• Since aCallback is never called if mod A isn't loaded, it is free to lookup the global symbol A (which we know is defined by mod A) without testing whether it actually exists.

Mod B in the second example could also look like this, but I wanted to be able to name the function when talking about the behavior:

get_modpath seems to be reliable; it just doesn't solve the mentioned problem. Sometimes you have to execute your own code *after* the other mod finished. For example, I want to plug into the tree-growing functions of moretrees. That's difficult to do if those functions are not defined yet because my mod was loaded first. All I could do would be to delay execution of my mod for a few seconds and hope it won't get needed in the meantime.
The callback method prestidigitator suggested would be very helpful.

http://minetest.net/forum/viewtopic.php?id=2911

Please search forum first.

When I turned my mod into a modpack, it seems it got executed first :-(. Anyway, doing a callback with 0 seconds as suggested in the thread rubenwardy mentioned may work but isn't exactly a clean soulution.