Multiple source mod deduplication

[triphora]

The name of this issue is a bit confusing, so let me elaborate on what this means.

• Modpack maker installs Fabric API from Modrinth
• Modpack maker installs a mod from CurseForge that lists Fabric API as a dependency
• It asks the modpack maker to install Fabric API as a dependency. This is a relatively minor thing, but considering I have to select n every time I update Xaero's, it's a bit of an annoyance. The solution here that I see is to check the slug of the dependency (Fabric API on CF and MR use the same slug) rather than to check whether it shares the same project ID.

[comp500]

Hmm, that's an interesting problem... Ideally we'd be able to get the actual modid + provides from the jar, but that isn't currently provided by any mod website API. Checking the slug for now will work, but I'd like to experiment with implementing the full dependency resolution features that Fabric/Quilt will use - especially for "provides" dependencies like Quilt's Fabric API replacements. Might require a local cache of this sort of metadata or mod jars somewhere.

[Fnige]

As a simpler way to maybe solve this, is it possible to just have a file that just states what dependencies to ignore? i.e:

.pwdepignore

# Ignores Fabric API (Could be slug or what it shows in the command line or whatever)
Fabric API

[comp500]

I do like this idea as a stopgap. Since it needs to know what Modrinth/CurseForge project IDs to ignore, you'd have to include those in the ignores list - probably an [options] field in pack.toml.

[Steveplays28]

This would be super nice as well for Quilt, since Quilt has its own Fabric API wrapper (Quilted Fabric API). Being able to ignore Fabric API from the dependency prompt would be neat.

[comp500]

@Steveplays28 That's a slightly different issue to this one, see https://github.com/packwiz/packwiz/issues/173 (packwiz now has a manual override for that specific case)

[Steveplays28]

Ahh cool, thanks!