- Edited
I'm proposing a system similar to how Ore Dictionary for the forge Minecraft mod loader works
Suppose we have two mods, one made by juan, and one made by fireman.
Suppose each mod adds a resource named tungsten, with different sprites and ID's
Having your ship store tungsten for each mod, for each having the same way to obtain (asteroids),and each type having a tree of resource conversions that are completely segragrated from eachother, it would still be great, but it would be better if they could use the resources interchangeably
So, what if resources could have specific tags to allow using resources from other mods without having it beforehand
OreDict
[
oreTungsten
Tungsten
]
This would allow for building a part using tungsten from the other mod, without having clashing different types of resources
Suppose a third mod, mod X
In this image, this describes different resources and their crafting
The plate presser converts beetween a ore[...] Resource into a plate[...] Resource if (and only if) the plate[...] Resource exists
Mod A adds a type of oreTungsten
Mod B also adds a type of oreTungsten
Mod B adds a item with a OreDict of plateTungsten, allowing itself to be crafted from platePressers using either Mod B or Mod A's version of tungsten.
In this second image, this shows multiple fields of OreDict in the plastanium resource, and possible ways this could be implemented, using a oredict: ore
(similar word, same would be strange to use) prefix to be able to interchange, and using oredict:ore* as a wildcard for any resource of that type to change to another of the same wildcard name.
This could help mods in modern cosmoteer, as it's more focused on resources rather than money, and clashing different resources, all with the same name wouldn't go well...