Closed modmuss50 closed 5 years ago
The problem here is that the JAR does not have a manifest, which when I wrote this, I always expected JAR files to have manifests, because if you build your mod with FG, you should have one. Why does this JAR not have one?
I forget sorry
It's all good. I mean, since enough people complained, and I really don't care anymore (considering it isn't even my project anymore :P) I don't see a problem with it being fixed on this end.
Though all JARs should all have manifests, just to make everyone's life easier.
I ran into this issue with GraviSuite-1.7.10-2.0.3.jar (with 1.7.10-stable_2) mappings.
same problem
I can look into how this got un-fixed but really your jars should have manifests...
The mod is in a Zip file and the classes are usually in a folder that end up being zipped. I'm trying to take apart one of my old mods and there was no way to have a manifest
You might have more luck with the original BON...BON2 is made to work with mods built with (Forge)gradle
I think this mod was built with forgegradle
Then it should be a jar file, and jar files have manifests.
The jar specification declares the META-INF directory optional. "A JAR file is essentially a zip file that contains an optional META-INF directory" (emphasis mine)
well modloader jars to have a manifest. Does this support notch name decompilation modloader mods don't use srg names
Hello, When I tryied to debof a mod:
http://i.imgur.com/VoguR11.png
I tried running from an elevated cmd:
http://i.imgur.com/cjEz9oJ.png
This is using 1.7.10 forge. I might take a look at fixing it