Jump to content

DaemonUmbra

Members
  • Posts

    11222
  • Joined

  • Last visited

  • Days Won

    67

Everything posted by DaemonUmbra

  1. Delete this file: C:\Users\Baker\AppData\Roaming\.minecraft\config\forge-client.toml
  2. 1.7 is no longer supported on this forum. Please update to a modern version of Minecraft to receive support.
  3. 1.12 is no longer supported on this forum. Please update to a modern version of Minecraft to receive support.
  4. User was banned for piracy. Buy the game.
  5. 1.12 is no longer supported on this forum. Please update to a modern version of Minecraft to receive support.
  6. 1.12 is no longer supported on this forum. Please update to a modern version of Minecraft to receive support.
  7. 1.12 is no longer supported on this forum. Please update to a modern version of Minecraft to receive support.
  8. 1.12 is no longer supported on this forum. Please update to a modern version of Minecraft to receive support.
  9. https://docs.gradle.org/current/userguide/core_dependency_management.html
  10. It deobfuscates things to your current mappings
  11. 1.12 is no longer supported on this forum. Please update to a modern version of Minecraft to receive support.
  12. No that's not how you do it. (I mean it is for regular Eclipse projects, but this is a Gradle project) If you make a multi-build project you just have the mod project depend on the library project's output and have everything reobf on publish. If you have every project separate you reobf with build, have the library publish to mavenLocal (or use a flatDir repo) and have your mod project get the library and fg.deobf() it
  13. Well you'll still have the issue of do you want to reobf with build or do you want to reobf with publish?
  14. I'm not sure that works anymore, I need to look at that. And even if it works the same way it used to, it working would depend on how your library is built, whether it's reobfed or not
  15. Delete these folders: %USERPROFILE%\.gradle\caches\forge_gradle\mcp_repo\de\oceanlabs\mcp\mcp_config\1.15.2-20200515.085601 %USERPROFILE%\.gradle\caches\forge_gradle\maven_downloader\de\oceanlabs\mcp\mcp_config\1.15.2-20200515.085601 %USERPROFILE%\.gradle\caches\forge_gradle\minecraft_user_repo\de\oceanlabs\mcp\mcp_config\1.14.4-20190829.143755 and run the refresh command again
  16. I believe you'll probably want to set up publishing your library to mavenLocal (it's a maven repository structure on your disk), then pull it from there. (Please attempt to look up what I've mentioned before continuing)
  17. 1.10 is no longer supported on this forum. Please update to a modern version of Minecraft to receive support.
  18. 1.12 is no longer supported on this forum. Please update to a modern version of Minecraft to receive support.
  19. 1.12 is no longer supported on this forum. Please update to a modern version of Minecraft to receive support.
  20. 1.12 is no longer supported on this forum. Please update to a modern version of Minecraft to receive support.
  21. Corrupt MCP_Config zip by the looks... try gradlew build --refresh-dependencies --rerun-tasks
×
×
  • Create New...

Important Information

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