suggestion to add an ability to hide apis and libraries like in modmenu

Question

suggestion to add an ability to hide apis and libraries like in modmenu

delveticas opened this issue 2 years ago · 9 comments

delveticas commented 2 years ago

Tapacywka · Answer 1 · 2024-02-11T08:05:40.000Z

Yes, please, we need this feature for our modpack, especially with Sinytra Connector where 100 additional libraries are presented.

Boshigiri · Answer 2 · 2024-10-17T03:07:55.000Z

Yes, Sinytra Connector add lots of libraries.
We need this feature.

MrCrayfish · Answer 3 · 2024-11-10T13:14:36.000Z

@Boshigiri @Tapacywka Unfortunately a lot of authors don't mark their mod as a library in NeoForge (using FMLModType in the JAR manifest), so it's impossible for Catalogue to determine if a mod is actually a library. Nested jars should be marked as a library in NeoForge, however Sinytra might not be following the same behaviour.

Boshigiri · Answer 4 · 2024-11-10T13:31:11.000Z

Because i tried the neoforge ported Modmenu(Better Modlist [(Neo)Forge]), it can hide the fabric api correctly, I thought it could be detected
So i should submit this issue to Sinytra Team?

MrCrayfish · Answer 5 · 2024-11-10T13:55:33.000Z

I've made a patch that will be available in 1.21.1
9902144

MrCrayfish · Answer 6 · 2024-11-10T13:52:26.000Z

I've just reported an issue outlining the problem (Sinytra/Connector#1524). I can mark Fabric API libraries correctly, but Jar in Jar libraries from regular Fabric mods won't be marked as libraries based on the code I've read in Sinytra Connector.

Boshigiri · Answer 7 · 2024-11-10T13:57:34.000Z

Thank you for your work, just being able to hide the fabric api would be useful enough

MrCrayfish · Answer 8 · 2024-11-10T13:57:48.000Z

I've also made it possible to hide libraries in the list, assuming they are also marked as libraries. Added in 1526557

Furglitch · Answer 9 · 2025-06-10T05:16:11.000Z

I was going to make a separate feature request, but seeing as this wasn't closed with the commit, I figured it would be good to put here and not add to the number of issues. I can make a separate issue for the request if deemed necessary.

As you mentioned, the main problem with the libraries feature is that many devs don't properly

Perhaps some kind of config file could be made? Like, a line-by-line list of libraries that could be maintained by end-users both on their local instances and through pull requests to keep track of libraries? Catalogue already provides mod IDs, so the list could utilize those. Something like...

almanac
balm
bookshelf
cloth_config
creative core

Share to