Use case for supporting multiple plugin "variations"?

[studioph]

I'm currently working on a patcher for Quests Are In Skyrim, which comes in both USSEP and non-USSEP versions, which are named QuestsAreInSkyrimUSSEP.esp and QuestsAreInSkyrim.esp respectively.

Since the patcher doesn't care which variant of the plugin being used, I wrote 2 utility methods - one to assert that one of them is in the load order, and another to resolve the IModListing at runtime.

At face value, these seem like potentially useful capabilities to have, and I am interested in submitting a PR to add them, but thinking about it some more, I feel like most mods use the same consistent plugin name specifically to avoid this problem so that other people can make patches and build off of it without worrying about naming.

Have other people encountered this scenario with other mods where there are different plugin names based on a variant/version?

EDIT: SPO (Skyrim Project Optimization) is another one I just thought of that has different names - full vs no-homes versions

[Noggog]

Hmm, haven't come across that before, no. If you wanted to contribute an alternative convenience function of AssertHas[Any]Mod(...) or something similar, it would likely be over in the Mutagen library, probably in this file
https://github.com/Mutagen-Modding/Mutagen/blob/dev/Mutagen.Bethesda.Core/Extensions/HasModsMixIn.cs

Feel free to make a feature request issue, and then fulfill it with a PR if you're up for it.
See you over there!

[studioph]

Oh awesome! I was trying to gauge whether people felt it was worthwhile to add to Mutagen, but if you're open to it I'm happy to submit a feature request + PR.