Sorry for poor title. In short I'm wondering if there is a better way to deal with the issue of self extracting jars. I had a pack denied due to the file "ImmersiveEngineering<version>-core" which is a self extracting core jar mod. I was going to request it for approval but there is no "other" or similar box on the form where I could of put the issue. For now I made sure the pack launched properly then I deleted the core-jar from the mods list and exported the instance.
Will I have to do this every time I update the pack (remove all self extracting jars) or will Curse have someway to approve these too? With the above example the name is always the same with the version of the core matching the version of the non core mod I believe.
There is no reason to be including these in your modpacks, since they'll simply be extracted on the users' side anyway. When you export your profile, make sure anything that you didn't explicitly add to the pack has no checkmark next to it.
That will work, with more and more mods doing this is there anyway to automate this as it can get tedious and hard to member with bigger packs, specially as Forge is pushing for self extracting jars and mods to separate out ASM into said separate jar?
One thing I do is I export the instance, check overrides folder, then check mods folder. Make sure everything in that folder is on the 3rd party mod list. If its not, it will be rejected. It just lets you preemptively check if you have anything that needs approved outside of direct mod downloads. Ive caught a few mod updates that way as well. Sometimes old versions of mods get removed from the site and end up in the overrides folder.
-
View User Profile
-
View Posts
-
Send Message
Curse PremiumSorry for poor title. In short I'm wondering if there is a better way to deal with the issue of self extracting jars. I had a pack denied due to the file "ImmersiveEngineering<version>-core" which is a self extracting core jar mod. I was going to request it for approval but there is no "other" or similar box on the form where I could of put the issue. For now I made sure the pack launched properly then I deleted the core-jar from the mods list and exported the instance.
Will I have to do this every time I update the pack (remove all self extracting jars) or will Curse have someway to approve these too? With the above example the name is always the same with the version of the core matching the version of the non core mod I believe.
-
View User Profile
-
View Posts
-
Send Message
Project AuthorThere is no reason to be including these in your modpacks, since they'll simply be extracted on the users' side anyway. When you export your profile, make sure anything that you didn't explicitly add to the pack has no checkmark next to it.
-
View User Profile
-
View Posts
-
Send Message
Curse PremiumThat will work, with more and more mods doing this is there anyway to automate this as it can get tedious and hard to member with bigger packs, specially as Forge is pushing for self extracting jars and mods to separate out ASM into said separate jar?
-
View User Profile
-
View Posts
-
Send Message
Project AuthorThere is not - the App has no way of knowing when this happens; it just sees new files in the folder.
-
View User Profile
-
View Posts
-
Send Message
Curse PremiumIn reply to carstorm:
-_-