Jump to content
View in the app

A better way to browse. Learn more.

Forge Forums

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.

Truffacious

Members
  • Joined

  • Last visited

Everything posted by Truffacious

  1. I typically try to get things working on the command-line before setting up the project in an IDE, and it seemed reasonable based on https://mcforge.readthedocs.io/en/latest/gettingstarted/#building-and-testing-your-mod. I just now did the following: 1) delete ~/.gradle 2) delete the forge-mdk directory & download it again 3) run ./gradlew genIntellijRuns 4) import the project into Intellij 5) click 'Yes' on the 'Import as Gradle project' question 6) run 'runServer' in intellij. I get the logs below (this is just the last few lines) - if it'd be helpful I can figure out where the whole thing is stored and upload it [00:41:19] [pool-2-thread-1/DEBUG] [ne.mi.fm.ja.FMLJavaModLanguageProvider/SCAN]: Found @Mod class net.minecraftforge.common.ForgeMod with id forge [00:41:19] [pool-2-thread-1/DEBUG] [ne.mi.fm.lo.mo.ExplodedDirectoryLocator/SCAN]: Scanning exploded directory /Users/sam/mc1/forge-1.15.2-31.2.0-mdk-2/build/resources/main [00:41:19] [pool-2-thread-1/DEBUG] [ne.mi.fm.lo.mo.ExplodedDirectoryLocator/SCAN]: Scanning exploded target /Users/sam/mc1/forge-1.15.2-31.2.0-mdk-2/build/classes/java/main [00:41:19] [pool-2-thread-1/DEBUG] [ne.mi.fm.lo.mo.Scanner/SCAN]: Scanning Mod File: /Users/sam/mc1/forge-1.15.2-31.2.0-mdk-2/build/resources/main path /Users/sam/mc1/forge-1.15.2-31.2.0-mdk-2/build/classes/java/main/com/example/examplemod/ExampleMod$RegistryEvents.class [00:41:19] [pool-2-thread-1/DEBUG] [ne.mi.fm.lo.mo.Scanner/SCAN]: Scanning Mod File: /Users/sam/mc1/forge-1.15.2-31.2.0-mdk-2/build/resources/main path /Users/sam/mc1/forge-1.15.2-31.2.0-mdk-2/build/classes/java/main/com/example/examplemod/ExampleMod.class [00:41:19] [pool-2-thread-1/DEBUG] [ne.mi.fm.lo.mo.ExplodedDirectoryLocator/SCAN]: Exploded directory scan complete /Users/sam/mc1/forge-1.15.2-31.2.0-mdk-2/build/resources/main [00:41:19] [pool-2-thread-1/DEBUG] [ne.mi.fm.lo.mo.Scanner/SCAN]: Scanning /Users/sam/mc1/forge-1.15.2-31.2.0-mdk-2/build/resources/main with language loader javafml [00:41:19] [pool-2-thread-1/DEBUG] [ne.mi.fm.ja.FMLJavaModLanguageProvider/SCAN]: Found @Mod class com.example.examplemod.ExampleMod with id examplemod Process finished with exit code 0 I'm not sure what "After this has finished edit your Configurations to fix the “module not specified” error by changing selecting your “main” module" means - I don't see that error anywhere. The main module in runServer is still LaunchTesting Thanks for your help!
  2. Thanks for the reply. Like I mentioned, this doesn't have any effect. The same thing happens with ./gradlew --stacktrace --info --scan --debug --no-daemon runserver and org.gradle.daemon=false My limited understanding is that this flag just controls whether or not the daemon should persist after the build step
  3. environment: Mac OS X Sierra forge-1.15.2-31.2.0 jdk1.8.0_251 ---------------------------------- gradle.properties: Sets default memory used for gradle commands. Can be overridden by user or command line properties. # This is required to provide enough memory for the Minecraft decompilation process. org.gradle.jvmargs=-Xmx3G org.gradle.daemon=true org.gradle.java.home=/Library/Java/JavaVirtualMachines/jdk1.8.0_251.jdk/Contents/Home ------------------------------------ excerpts from standard out (./gradlew --stacktrace --info --scan --debug runserver): 2:13:45.081 [DEBUG] [org.gradle.launcher.daemon.client.DaemonClientInputForwarder] Dispatching close input message: org.gradle.launcher.daemon.protocol.CloseInput@58f485eb 22:13:45.081 [DEBUG] [org.gradle.launcher.daemon.client.DaemonClientConnection] thread 28: dispatching class org.gradle.launcher.daemon.protocol.CloseInput 22:13:45.081 [DEBUG] [org.gradle.launcher.daemon.client.DaemonClientConnection] thread 1: connection stop 22:13:45.089 [ERROR] [org.gradle.internal.buildevents.BuildExceptionReporter] 22:13:45.089 [ERROR] [org.gradle.internal.buildevents.BuildExceptionReporter] FAILURE: Build failed with an exception. 22:13:45.089 [ERROR] [org.gradle.internal.buildevents.BuildExceptionReporter] 22:13:45.089 [ERROR] [org.gradle.internal.buildevents.BuildExceptionReporter] * What went wrong: 22:13:45.089 [ERROR] [org.gradle.internal.buildevents.BuildExceptionReporter] Gradle build daemon disappeared unexpectedly (it may have been killed or may have crashed) 2:13:45.089 [ERROR] [org.gradle.internal.buildevents.BuildExceptionReporter] * Try: 22:13:45.089 [ERROR] [org.gradle.internal.buildevents.BuildExceptionReporter] Run with --scan to get full insights. 22:13:45.089 [ERROR] [org.gradle.internal.buildevents.BuildExceptionReporter] 22:13:45.089 [ERROR] [org.gradle.internal.buildevents.BuildExceptionReporter] * Exception is: 22:13:45.090 [ERROR] [org.gradle.internal.buildevents.BuildExceptionReporter] org.gradle.launcher.daemon.client.DaemonDisappearedException: Gradle build daemon disappeared unexpectedly (it may have been killed or may have crashed) -------------------------------- Any clue as to how to resolve this? I'm new to forge (and to minecraft, for that matter). I've tried switching org.gradle.daemon to false, and specifying --no-daemon, but neither seems to have any effect. Nor does removing ~/.gradle. Running runServer in IDEA also doesn't help. Interestingly, runclient seems to work fine (I do get the DaemonDisappearedException if I exit the game, however, which I suppose is expected?) Here is the full daemon log: https://www.dropbox.com/s/t30bsi37e7f8j12/daemon-27049.out.log?dl=0

Important Information

By using this site, you agree to our Terms of Use.

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.