Jump to content

mbh333

Members
  • Posts

    9
  • Joined

  • Last visited

mbh333's Achievements

Tree Puncher

Tree Puncher (2/8)

0

Reputation

  1. Just want to say thank you for this thread - it has solved several hours of headaches. I thought I had issues with my textures and/or code for registering new blocks, and had been going over everything, again and again.
  2. Bump. Surely this is a common problem, with a standard solution. How does anyone develop and test dependent mods?
  3. I'm trying to get set up in Eclipse with 1.15.2, I have a workspace with two projects, where each project is a mod. I want to be working on multiple mods as different projects in the same workspace, however the mods are dependent on each other. How do I setup the Eclipse runs so that I can run the game with all of the mods loaded at once? I have searched for old threads, such as this one, and found video tutorials, such as the Lex Manos tutorial. However, the information is out of date, and does not cover multiple mods in a single run config. All of the threads that I have found have been unanswered, and I can't find any official source of information for how to set this up correctly. But surely this is a very common issue for mod developers with multiple dependent mods?
  4. As far as I am aware it will only work on the most up-to-date version of Java, which would be 1.8.0.221. You do need an Oracle account, but that shouldn't stop you from downloading it. Making an account is free, and you can use a dummy email if you don't want to give them your real one. Try updating the JDK to that version and see if it helps. I solved my other problem, hopefully this solves yours.
  5. I'm trying to compile information about this issue here. Try following the steps I describe in that thread. If that works for you, could you let me know whether you're able to test the mod using gradlew runClient ? I've run into a different problem, documented here, and I am trying to discern if that is related to this issue with the mapped snapshot, or perhaps just a general issue with 1.14.x updates. It may be neither, in which case the issues are unrelated and only exist on my end, but currently I can't find any information either way.
  6. This issue has finally been resolved, after I tried the following: re-install the JRE and JDK for version 1.8.0_221 remove any newer versions of the JDK that were previously installed restart the computer I still have no idea what was causing it, and I have seen a few other instances of people running into the same error, so I'm editing the original post to keep track of these threads. If it is indeed related to the JDK, then it would be good if the error message made that clear, or if there was a clearly documented solution somewhere for these sorts of basic setup issues.
  7. I finally managed to get the basic empty mod from the mdk to build, but I cannot load it into the game to verify that it works. If I drag and drop my compiled test mod into the mod folder in .minecraft, and then start up Forge, it gives me an error saying that it failed to load the mod. If I do gradlew genEclipseRuns in the console, that succeeds. Then I try gradlew runClient, and that open the client just fine, but the mod isn't visible. When I close the client, the console then spits the following error: FAILURE: Build failed with an exception. * What went wrong: Could not dispatch a message to the daemon. I have no idea how daemon works, so I'm not sure what any of this means. This is becoming increasingly frustrating, as it seems immensely difficult to actually get started modding with Forge. I've been trying for several days now just to get the basic installation and dev envrionment setup, and it has been a pain at every step along the way. The docs appear to only help with 1.12.x and 1.13.x, and I can't seem to find any support for getting started with 1.14.x. If anyone is able to help, that would be hugely appreciated.
  8. I'm using Eclipse 2019-03 (4.11.0) All I've done is: run the gradlew eclipse command in my project folder import the project folder into eclipse change the group and archivesBaseName fields in the build.gradle file run gradlew build from the command line Worth noting, I just tried running gradlew eclipse on a new extraction of the mdk files, and I noticed this in the console, towards the end: MinecraftUserRepo: Failed to get Minecraft Joined SRG. Should not be possible. Could not resolve: net.minecraftforge:forge:1.14.4-28.0.24_mapped_snapshot_20190719-1.14.3 This is followed by a warning about deprecated gradle features making it incompatible with Gradle 5.0, and then the "build successful" message.
  9. --- UPDATE: As of August 01 I've managed to resolve this issue (as described in the thread below), but after building the mod I am still unable to test it in the client. I'm compiling a list of related threads here, as this seems to be an unresolved issue for several people. The following threads are related to the original issue of finding the mapped snapshot: [July 20] Could not find mapped snapshot [July 31] gradle genIntellijRuns does not supply 1.14.4 forge as external library [July 31] Can't Download Forge, failing on :compileJava The following threads are related to the ongoing issue of being unable to test the mod: [August 01] Cannot Load or Test Mod (1.14.4) --- ORIGINAL POST: Hi all, newcomer here. I've done a bit of research on this and can't find any answers. After downloading and extracting the mdk, I've followed the steps found here but whenever I try to run gradlew build I run into this error: * What went wrong: Could not resolve all files for configuration ':compileClasspath'. > Could not find net.minecraftforge:forge:1.14.4-28.0.24_mapped_snapshot_20190719-1.14.3. Searched in the following locations: - file:/C:/Users/[username]/.gradle/caches/forge_gradle/bundeled_repo/net/minecraftforge/forge/1.14.4-28.0.24_mapped_snapshot_20190719-1.14.3/forge-1.14.4-28.0.24_mapped_snapshot_20190719-1.14.3.pom - file:/C:/Users/[username]/.gradle/caches/forge_gradle/bundeled_repo/net/minecraftforge/forge/1.14.4-28.0.24_mapped_snapshot_20190719-1.14.3/forge-1.14.4-28.0.24_mapped_snapshot_20190719-1.14.3.jar - https://files.minecraftforge.net/maven/net/minecraftforge/forge/1.14.4-28.0.24_mapped_snapshot_20190719-1.14.3/forge-1.14.4-28.0.24_mapped_snapshot_20190719-1.14.3.pom - https://files.minecraftforge.net/maven/net/minecraftforge/forge/1.14.4-28.0.24_mapped_snapshot_20190719-1.14.3/forge-1.14.4-28.0.24_mapped_snapshot_20190719-1.14.3.jar - https://libraries.minecraft.net/net/minecraftforge/forge/1.14.4-28.0.24_mapped_snapshot_20190719-1.14.3/forge-1.14.4-28.0.24_mapped_snapshot_20190719-1.14.3.jar - https://repo.maven.apache.org/maven2/net/minecraftforge/forge/1.14.4-28.0.24_mapped_snapshot_20190719-1.14.3/forge-1.14.4-28.0.24_mapped_snapshot_20190719-1.14.3.pom - https://repo.maven.apache.org/maven2/net/minecraftforge/forge/1.14.4-28.0.24_mapped_snapshot_20190719-1.14.3/forge-1.14.4-28.0.24_mapped_snapshot_20190719-1.14.3.jar Required by: project : The first problem I identified was that the forge_gradle directory did not contain a folder named "bundeled_repo". It did however contain something called "minecraft_user_repo", which contained the rest of the file path and the .pom file that gradle was searching for. I assume this is an error in the installation, so I made a copy of the "minecraft_user_repo" folder and renamed it "bundeled_repo". I tried building the project again, but received the same error as above. I have deleted the entire project folder and re-extracted the mdk, multiple times, with no luck. For what it's worth, I have installed and run Forge version 1.14.4-28.0.24 and I'm using eclipse with the 8u221 version of both the JDK and JRE. As far as I can tell this seems like an issue with the 1.14.4 version of either forge or the mdk, but I can't find any information, and I am totally new to modding so I'm not sure how to proceed from here. Any help would be appreciated, cheers!
×
×
  • Create New...

Important Information

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