Posted March 9, 201411 yr Hey guys! I finished reorganizing my mod workspace similarly to how bspkrs arranges his, and updating my bugfix mini-coremod to 1.7.2 It works completely in my workspace. However, when I do gradle build , the resultant jarfile has its META-INF/MANIFEST-MF replaced with a single line: "Manifest-Version: 1.0" The line where I specify my FMLCorePlugin is missing. If I manually readd this line to the manifest in the jar, the mod works as intended, but that's not really in the spirit of gradle's automation, eh? What is happening and how do I correct it? Source: https://github.com/williewillus/XPFix/
March 9, 201411 yr Why did you put a non-java file in your java code? Think about it. Where do non-java files go? I do Forge for free, however the servers to run it arn't free, so anything is appreciated. Consider supporting the team on Patreon
March 9, 201411 yr Author I moved manifest.mf to src/main/resources/MANIFEST.MF. On build the proper manifest is included in the root directory of the jarfile, however a new META-INF is generated with a "blank" manifest inside. Same thing occurs if I move it to src/main/resources/META-INF/MANIFEST.MF, except that the proper manifest does not show up at all in the jarfile (Gradle overwrites it with the blank??) Neither of these allow for FML to load the mod.
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.