If I understand this request right, then I think that the opposite solution would make more sense. So, you could write in one mod's info.json (for example):


{
"name":"dependentmod",
//...
"dependencies" : [ "foo|bar"], // foo or bar could satisfy this dependency
//...
}


and then, if at ...

Yes, I figured it would be something like that, given Lua's insistence on internalized strings with no buffer. Restructuring the saved data to contain only enough information to reconstruct a local structure which has the proper references gave a marked improvement in performance during the save ...

Demonstration here: https://drive.google.com/open?id=13IZTWzq-fFmdqcMEDQS2AibypEkKoH_V
To reproduce, simply install and enable the mod linked above, and note that it takes a good deal longer to complete the save process than necessary, and in the process consumes an enormous amount of ram, and the ...

Fair enough, I suppose, and I can work around its absence.

In case you're curious, the reason I came across this is that I'm experimenting with building a layer on top of the gui element API, and I had wanted to be able to release the names of destroyed elements to be used again. Since element ...

Stack trace: https://pastebin.com/vMh8X7mt To reproduce (this works with any object which errors during finalization, this is just the shortest command I could think of):

/c setmetatable({}, {__gc = error})

I realize that a crash due to writing a bad finalizer routine is technically my fault ...