SeanOMik Posted May 30, 2018 Posted May 30, 2018 (edited) So a few weeks ago I started working on my mod again: https://minecraft.curseforge.com/projects/a-realistic-food-mod?gameCategorySlug=mc-mods&projectID=246769#c10. And after converting it from 1.10.2 to 1.12.2, I uploaded 2 versions. After a few days a friend through discord tried it and reported to me that it didnt work AT ALL. I opened eclipse and it seemed to work. So I compiled the mod and I discovered that it doesn't work at all. I have no idea why this is happening, its probably gonna be something stupid... But your gonna need code, and the only thing I can think of giving you is my github: https://github.com/SeanOMik/A-Realistic-Food-Mod. Thanks! Edited May 31, 2018 by SeanOMik Quote Developer of "A Realistic Foods Mod"
Asyc Posted May 30, 2018 Posted May 30, 2018 (edited) Did you use gradlew build or did you export it through eclipse? Edited May 30, 2018 by Asyc Quote
SeanOMik Posted May 30, 2018 Author Posted May 30, 2018 Just now, Asyc said: Did you use gradlew build or did you export it through eclipse? I used gradlew build Quote Developer of "A Realistic Foods Mod"
Asyc Posted May 30, 2018 Posted May 30, 2018 So I put your mod in JD-GUI and it appears the jar file only contains assets and Meta-inf Quote
Asyc Posted May 30, 2018 Posted May 30, 2018 Have you checked out the build.gradle file in your mod directory, make sure everything there is okay? Quote
SeanOMik Posted May 30, 2018 Author Posted May 30, 2018 Just now, Asyc said: So I put your mod in JD-GUI and it appears the jar file only contains assets and Meta-inf After opening it in WinRAR that does appear to be the issue... But what would cause this, and how could I fix it? Quote Developer of "A Realistic Foods Mod"
Asyc Posted May 30, 2018 Posted May 30, 2018 (edited) In your build.gradle file there should be some stuff you should checkout, I think it might be version = "1.0" group = "com.yourname.modid" archivesBaseName = "modid" Rename that stuff in your build.gradle with a text editor and rerun gradlew build Edited May 30, 2018 by Asyc Quote
SeanOMik Posted May 30, 2018 Author Posted May 30, 2018 1 minute ago, Asyc said: In your build.gradle file there should be some stuff you should checkout, I think it might be version = "1.0" group = "com.yourname.modid" archivesBaseName = "modid" Rename that stuff in your build.gradle with a text editor and rerun gradlew build I already did that: version = "0.5.1" group = "com.SeanOMik.realfoods" archivesBaseName = "realfoods-0.5.1_BETA" Quote Developer of "A Realistic Foods Mod"
Asyc Posted May 30, 2018 Posted May 30, 2018 Try running gradlew build with --stacktrace and post results! Quote
SeanOMik Posted May 30, 2018 Author Posted May 30, 2018 After running it, where it is: To honour the JVM settings for this build a new JVM will be forked. Please consider using the daemon: https://docs.gradle.org/2.14/userguide/gradle_daemon.html. This mapping 'snapshot_20171003' was designed for MC 1.12! Use at your own peril. ################################################# ForgeGradle 2.3-SNAPSHOT-4a7d623 https://github.com/MinecraftForge/ForgeGradle ################################################# Powered by MCP http://modcoderpack.com by: Searge, ProfMobius, R4wk, ZeuX Fesh0r, IngisKahn, bspkrs, LexManos ################################################# :deobfCompileDummyTask :extractMcpMappings SKIPPED :deobfProvidedDeobfDepTask0 SKIPPED :deobfProvidedRemapDepSourcesTask1 SKIPPED :deobfProvidedDummyTask :sourceApiJava UP-TO-DATE :compileApiJava UP-TO-DATE :processApiResources UP-TO-DATE :apiClasses UP-TO-DATE :sourceMainJava UP-TO-DATE :compileJava UP-TO-DATE :processResources UP-TO-DATE :classes UP-TO-DATE :jar :sourceTestJava UP-TO-DATE :compileTestJava UP-TO-DATE :processTestResources UP-TO-DATE :testClasses UP-TO-DATE :test UP-TO-DATE :extractMcpData SKIPPED :getVersionJson :extractUserdev UP-TO-DATE :genSrgs SKIPPED :reobfJar :extractAnnotationsJar :extractRangemapReplacedMain UP-TO-DATE :retromapReplacedMain UP-TO-DATE :sourceJar UP-TO-DATE :assemble :check UP-TO-DATE :build BUILD SUCCESSFUL Total time: 10.693 secs Quote Developer of "A Realistic Foods Mod"
Asyc Posted May 30, 2018 Posted May 30, 2018 Alright here is what I found out, I downloaded the source on my computer(and built it) and everything seems fine when I do it so it has to be something wrong with build.gradle Quote
Asyc Posted May 30, 2018 Posted May 30, 2018 (edited) version = "1.0" group = "com.yourname.modid" archivesBaseName = "modid" Edited May 30, 2018 by Asyc Quote
Asyc Posted May 30, 2018 Posted May 30, 2018 Oops wrong code set the build.gradle settings to default version = "1.0"group = "com.yourname.modid"archivesBaseName = "modid" Quote
SeanOMik Posted May 31, 2018 Author Posted May 31, 2018 (edited) 2 hours ago, Asyc said: Oops wrong code set the build.gradle settings to default version = "1.0"group = "com.yourname.modid"archivesBaseName = "modid" And I should compile the mod with the defaults? Because doing that still doesnt have the code in the jar Edited May 31, 2018 by SeanOMik Quote Developer of "A Realistic Foods Mod"
SeanOMik Posted May 31, 2018 Author Posted May 31, 2018 11 hours ago, diesieben07 said: Your Git repository is missing essential stuff. The repository root should be in your project root, where your build.gradle is. No, that does not mean you have to include everyone and their dog in your repository. Okay, well I fixed it. I moved all the files into a /src/main/... then I added gradlew.build and gradlew.properties. If you need any other folders, tell me. Quote Developer of "A Realistic Foods Mod"
DaemonUmbra Posted May 31, 2018 Posted May 31, 2018 (edited) sourceSets { main { java {srcDirs = ["$projectDir/common"]} resources {srcDirs = ["$projectDir/resources"]} } } should be sourceSets { main { java {srcDirs = ["$projectDir/src/main/java"]} resources {srcDirs = ["$projectDir/src/main/resources"]} } } Gradle seemed to cache this when I corrected it, built, then removed the sourceSets group entirely, and I believe this is the default if not overridden as you did. Edited May 31, 2018 by DaemonUmbra Quote This is my Forum Signature, I am currently attempting to transform it into a small guide for fixing easier issues using spoiler blocks to keep things tidy. As the most common issue I feel I should put this outside the main bulk: The only official source for Forge is https://files.minecraftforge.net, and the only site I trust for getting mods is CurseForge. If you use any site other than these, please take a look at the StopModReposts project and install their browser extension, I would also advise running a virus scan. For players asking for assistance with Forge please expand the spoiler below and read the appropriate section(s) in its/their entirety. Spoiler Logs (Most issues require logs to diagnose): Spoiler Please post logs using one of the following sites (Thank you Lumber Wizard for the list): https://gist.github.com/: 100MB Requires member (Free) https://pastebin.com/: 512KB as guest, 10MB as Pro ($$$) https://hastebin.com/: 400KB Do NOT use sites like Mediafire, Dropbox, OneDrive, Google Drive, or a site that has a countdown before offering downloads. What to provide: ...for Crashes and Runtime issues: Minecraft 1.14.4 and newer: Post debug.log Older versions: Please update... ...for Installer Issues: Post your installer log, found in the same place you ran the installer This log will be called either installer.log or named the same as the installer but with .log on the end Note for Windows users: Windows hides file extensions by default so the installer may appear without the .jar extension then when the .log is added the log will appear with the .jar extension Where to get it: Mojang Launcher: When using the Mojang launcher debug.log is found in .minecraft\logs. Curse/Overwolf: If you are using the Curse Launcher, their configurations break Forge's log settings, fortunately there is an easier workaround than I originally thought, this works even with Curse's installation of the Minecraft launcher as long as it is not launched THROUGH Twitch: Spoiler Make sure you have the correct version of Forge installed (some packs are heavily dependent on one specific build of Forge) Make a launcher profile targeting this version of Forge. Set the launcher profile's GameDir property to the pack's instance folder (not the instances folder, the folder that has the pack's name on it). Now launch the pack through that profile and follow the "Mojang Launcher" instructions above. Video: Spoiler or alternately, Fallback ("No logs are generated"): If you don't see logs generated in the usual place, provide the launcher_log.txt from .minecraft Server Not Starting: Spoiler If your server does not start or a command window appears and immediately goes away, run the jar manually and provide the output. Reporting Illegal/Inappropriate Adfocus Ads: Spoiler Get a screenshot of the URL bar or copy/paste the whole URL into a thread on the General Discussion board with a description of the Ad. Lex will need the Ad ID contained in that URL to report it to Adfocus' support team. Posting your mod as a GitHub Repo: Spoiler When you have an issue with your mod the most helpful thing you can do when asking for help is to provide your code to those helping you. The most convenient way to do this is via GitHub or another source control hub. When setting up a GitHub Repo it might seem easy to just upload everything, however this method has the potential for mistakes that could lead to trouble later on, it is recommended to use a Git client or to get comfortable with the Git command line. The following instructions will use the Git Command Line and as such they assume you already have it installed and that you have created a repository. Open a command prompt (CMD, Powershell, Terminal, etc). Navigate to the folder you extracted Forge’s MDK to (the one that had all the licenses in). Run the following commands: git init git remote add origin [Your Repository's URL] In the case of GitHub it should look like: https://GitHub.com/[Your Username]/[Repo Name].git git fetch git checkout --track origin/master git stage * git commit -m "[Your commit message]" git push Navigate to GitHub and you should now see most of the files. note that it is intentional that some are not synced with GitHub and this is done with the (hidden) .gitignore file that Forge’s MDK has provided (hence the strictness on which folder git init is run from) Now you can share your GitHub link with those who you are asking for help. [Workaround line, please ignore]
SeanOMik Posted May 31, 2018 Author Posted May 31, 2018 53 minutes ago, DaemonUmbra said: sourceSets { main { java {srcDirs = ["$projectDir/common"]} resources {srcDirs = ["$projectDir/resources"]} } } should be sourceSets { main { java {srcDirs = ["$projectDir/src/main/java"]} resources {srcDirs = ["$projectDir/src/main/resources"]} } } Gradle seemed to cache this when I corrected it, built, then removed the sourceSets group entirely, and I believe this is the default if not overridden as you did. Ah! It works now! I don't know how it got through the approving process from curse though. But thanks again thanks for all your help! Quote Developer of "A Realistic Foods Mod"
Recommended Posts
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.