Jump to content
Search In
  • More options...
Find results that contain...
Find results in...

Country_Gamer

Members
  • Posts

    27
  • Joined

  • Last visited

Converted

  • Gender
    Undisclosed
  • Personal Text
    I am new!

Country_Gamer's Achievements

Tree Puncher

Tree Puncher (2/8)

1

Reputation

  1. You mean for smelting? I know how to create the custom recipe class, but not how I would make it usable for smelting recipes. GameRegistry has an addRecipe(IRecipe) but I cannot find something similar for smelting.
  2. Hey, I am having trouble finding a way to transfer a string in the nbt of the input inside a vanilla furnace to be transferred into the nbt of the output. Both items have a mac stack size of 1, so it isn't an issue of storing the string. It does not look like I can use an IRecipe, but I may be mistaken. Any one with any ideas out there? It should be noted that this needs to use a vanilla furnace.
  3. What specifically do you mean by editing the run configurations?
  4. Not entirely sure. I would suggest; A) Using "gradlew setupDevWorkspace --refresh-dependencies"; this will use less memory because Decomp decompiles the source of MC, which you really shouldn't need to do B) Increase the ram utilized by gradle be way of jam args in a gradle.properties file (I think thats what you call it). I found that I had to do this, otherwise it wouldn't setup the workspace completely.
  5. The folder layout is like so: /Workspace/ /Workspace/Core/src/main/java/ /Workspace/Angel/src/main/java/ /Workspace/CAPO/src/main/java/ /Workspace/PvZ/src/main/java/ I added a file named "settings.gradle" to /Workspace/Core/ with text: includeFlat ‘Angel’,’CAPO’, ‘PvZ’ I then ran the "bash gradlew setupDevWorkspace --refresh-dependencies" and "bash eclipse --refresh-dependencies" on each mod directory (Core, Angel, CAPO, PvZ). Opened the workspace in eclipse (path /Workspace/) and it still does not work. EDIT: I have also tried putting a "settings.gradle" into the Angel CAPO and PvZ directories, including the Core project. This injects the data, but does not allow for a successful workspace run nor build
  6. Hi! After following LexManos's (LexManos' ?) tutorial on setting up the workspace with multiple mods, (which I have successfully done, thank you Lex!) I am wondering how to add it so that all my mods except 1 of them is dependent on that one. This is meant to be so that I can modify my core mod and then its code is directly usable from each of my other mods. Here is what the setup looks like, and two sample build.gradle files. Hope someone can help me out on this! (Note, all the errors are because the sub mods cannot find the core mod) Setup image: Core build.gradle: SubMod build.gradle:
  7. Ok, so I have gradle decompiling with a JVM args of: org.gradle.jvmargs=-Xmx3G -XX:MaxPermSize=256m inside the gradle.properties file (within the forge directory) The log is very expansive, so it will be saved on my google drive. If you have any tips, anything would be appreciated. The commands I used were: cd <path to forge directory> bash gradlew setupDecompWorkspace --refresh-dependencies --debug Log: https://drive.google.com/file/d/0BydSDfW_5O_IMWZ3ZlBrZDVrSmc/edit?usp=sharing
  8. I have one for the WeepingAngelsMod if you want to look at the source: https://github.com/TheCountryGamer/WeepingAngels
  9. use: gradlew.bat setupDecompWorkspace --refresh-dependencies gradlew.bat eclipse --refresh-dependencies see if that helps your missing library. If you get any errors, try increasing the max ram used
  10. Ok. So I have it setting up the workspace fine now. The only thing is that there are a few default errors in the workspace: gradle.properties file: org.gradle.jvmargs=-Xmx3G Log: Last login: Sun Feb 9 07:13:44 on console MyMacBook:~ username$ cd /Users/username/Programming/Java/Minecraft\ Modding/1.7.2/forge-1.7.2-10.12.0.1025-src MyMacBook:forge-1.7.2-10.12.0.1025-src username$ bash gradlew setupDecompWorkspace --refresh-dependencies To honour the JVM settings for this build a new JVM will be forked. Please consider using the daemon: http://gradle.org/docs/1.10/userguide/gradle_daemon.html. **************************** Powered By MCP: http://mcp.ocean-labs.de/ Searge, ProfMobius, Fesh0r, R4wk, ZeuX, IngisKahn MCP Data version : unknown **************************** :extractUserDev :getAssetsIndex :getAssets :copyAssets :extractNatives :genSrgs :downloadMcpTools :downloadClient SKIPPED :downloadServer SKIPPED :mergeJars SKIPPED :deobfuscateJar Applying SpecialSource... Applying Exceptor... Injecting source info... :decompile Corrupted Cache! :doFmlPatches Corrupted Cache! :addFmlSources :remapJar Corrupted Cache! :doForgePatches Corrupted Cache! :addForgeJavadoc Corrupted Cache! :extractForgeSrc :recompForge warning: [options] bootstrap class path not set in conjunction with -source 1.6 Note: Some input files use or override a deprecated API. Note: Recompile with -Xlint:deprecation for details. Note: Some input files use unchecked or unsafe operations. Note: Recompile with -Xlint:unchecked for details. 1 warning :repackForge :setupDecompWorkspace BUILD SUCCESSFUL Total time: 3 mins 37.261 secs MyMacBook:forge-1.7.2-10.12.0.1025-src username$ bash gradlew eclipse --refresh-dependencies To honour the JVM settings for this build a new JVM will be forked. Please consider using the daemon: http://gradle.org/docs/1.10/userguide/gradle_daemon.html. **************************** Powered By MCP: http://mcp.ocean-labs.de/ Searge, ProfMobius, Fesh0r, R4wk, ZeuX, IngisKahn MCP Data version : unknown **************************** :eclipseClasspath :eclipseJdt :eclipseProject :eclipse BUILD SUCCESSFUL Total time: 44.355 secs MyMacBook:forge-1.7.2-10.12.0.1025-src username$ Workspace Screenshot: https://dl.dropboxusercontent.com/u/90187699/Workspace.png
  11. Here ya go Lex: (this is the best i could do with how big it is) https://drive.google.com/file/d/0BydSDfW_5O_INkV1anVIajFsTWM/edit?usp=sharing
  12. running "bash gradlew setDevWorkspace eclipse --refresh-dependencies --debug" and i get the same error i started with.
×
×
  • Create New...

Important Information

By using this site, you agree to our Privacy Policy.