thinkverse Posted August 16, 2019 Posted August 16, 2019 (edited) I can't seem to get the runClient task to show up in IntelliJ's Gradle tab anymore when starting a clean copy on any 1.14 MDK, I can get it in the 1.13.2 version though, anyone has any idea on how to fix it? Gradle builds aren't my strong suit, I know it's their, because gradlew runclient works, it's just now showing up in IntelliJ anymore.FIX I clicked the Gradle elephant icon on the sidebar, the execute gradle tasks, and I could just write in runClient and it ran, still not sure why it doesn't show up under fg_runs when it's there... Edited August 16, 2019 by thinkverse Topic fixed Quote
Caucorico Posted August 16, 2019 Posted August 16, 2019 Hi, do you have run the setupDecompWorkspace task ? Best regards, Caucorico Quote
thinkverse Posted August 16, 2019 Author Posted August 16, 2019 setupDecompWorkspace doesn't seem to exists though.Task 'setupDecompWorkspace' not found in root project '1.14.4'. Quote
Caucorico Posted August 16, 2019 Posted August 16, 2019 In your IDEA, there is the gradle Tab on the right. And when you click on the icon, a file/repository list is displayed. In this repository there is a task named setupDecompWorkspace. Are you sure that it is not here ? Quote
thinkverse Posted August 16, 2019 Author Posted August 16, 2019 Yeah, not there, never had that task, not with 1.13.2 either, don't know about 1.12.2 or earlier though, have it in the terminal in the included gradlew file, .gradlew setupDecompWorkspace, but not in IDEA for some reason, everything works regardless for me so. Quote
DaemonUmbra Posted August 16, 2019 Posted August 16, 2019 setupDecompWorkspace does not exist in ForgeGradle 3, that work is now done when the IDE imports/refreshes the project. I believe I heard this is an issue with intellij not liking tasks that are added dynamically or something. 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. Reveal hidden contents Logs (Most issues require logs to diagnose): Reveal hidden contents 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: Reveal hidden contents 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: Reveal hidden contents 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: Reveal hidden contents 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: Reveal hidden contents 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: Reveal hidden contents 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]
thinkverse Posted August 16, 2019 Author Posted August 16, 2019 Could be the case, it works when I click Execute Gradle Task, so it's not lost, it just wasn't showing up under tasks > fg_runs, but after clicking on stuff I found Execute Gradle Task and can run the task from there. Quote
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.