Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Give a better way to figure out where Jar in Jar mods originate #93

Closed
Asbestosstar opened this issue Jun 23, 2022 · 2 comments
Closed

Comments

@Asbestosstar
Copy link

Some mods, such as Exotic Blocks, include extra jars kind of shadowed or some other way included in there, sometimes it goes many levels deep(jar-in-jar-in-jar etc.).Sometimes these libraries bundled mods included conflict with other mods and cause problems. And yes while shadowing, fat jars and other methods to include libraries in mods is often a bad idea, it is commonly used by many mods, and it makes modpack making a pain for mods which do it. It is possible that the game could crash because of some mod you have never heard of and do not know where it is coming from. I would like a way to know which jar file the crash is coming from and a way to know which mod a bundled mod is actually coming from.

Mod.jar -> IncludedMod.jar

An example would be if IncludedMod.jar were to crash you would be able to know that it was included in Mod.jar so you know to disable Mod.jar rather than just having the modid of the mod which failed.

@IMB11
Copy link

IMB11 commented Jul 14, 2022

I'll take a look at this.

@TheGlitch76
Copy link
Member

The mod table shows where mods were loaded from, I think that's sufficient?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants