Awsome

bump

Forgot to post code: Item Class: https://github.com/Awsomekeldeo/RealisTech/blob/forge-support/src/main/java/awsome/realistech/items/CeramicMoldItem.java Capability Wrapper: https://github.com/Awsomekeldeo/RealisTech/blob/forge-support/src/main/java/awsome/realistech/capability/MoldCapabilityWrapper.java Capability: Interface: https://github.com/Awsomekeldeo/RealisTech/blob/forge-support/src/main/java/awsome/realistech/api/capability/energy/IHeat.java IStorage implementation: https://github.com/Awsomekeldeo/RealisTech/blob/forge-support/src/main/java/awsome/realistech/api/capability/energy/HeatCapability.java Implementation: https://github.com/Awsomekeldeo/RealisTech/blob/forge-support/src/main/java/awsome/realistech/api/capability/impl/HeatHandlerItemStack.java

One of the items in my mod is supposed to be syncing it's NBT data to the client using ItemStack::getShareTag and ItemStack::readShareTag. I've tried putting breakpoints in these methods, but they don't seem to be getting called at all. Is something wrong with my installation? My forge version is 1.15.2-31.2.31, in case that helps. Any help would be appreciated.

I want to add a custom fluid type to my mod. I'm currently trying to extend ForgeFlowingFluid, and am lost as to what to do with the method overrides in the class.

I managed to get it working, I just looked at the campfire tile entity's renderer as an example.

I would like to have a tile entity that renders it's items in-world on top of itself. Can I get some pointers as to where to look for examples of that sort of thing? Also, just a few more questions: 1. Is it possible to just use a TER for the items and have the block itself just be a baked model? 2. Do I need to use a container for the tile entity if I'm not going to add a GUI for it?

If you already know basic java, I would suggest reading the forge documentation first: https://mcforge.readthedocs.io/en/1.15.x/ McJty's modding tutorial is also pretty good and covers most of the basics, found here: https://wiki.mcjty.eu/modding/index.php?title=YouTube-Tutorials

Here's my build.gradle file, I forgot to post it. buildscript { repositories { maven { url = 'https://files.minecraftforge.net/maven' } jcenter() mavenCentral() } dependencies { classpath group: 'net.minecraftforge.gradle', name: 'ForgeGradle', version: '3.+', changing: true } } apply plugin: 'net.minecraftforge.gradle' // Only edit below this line, the above code adds and enables the necessary things for Forge to be setup. apply plugin: 'eclipse' apply plugin: 'maven-publish' version = '1.0' group = 'awsome.techmod' // http://maven.apache.org/guides/mini/guide-naming-conventions.html archivesBaseName = 'techmod' sourceCompatibility = targetCompatibility = compileJava.sourceCompatibility = compileJava.targetCompatibility = '1.8' // Need this here so eclipse task generates correctly. minecraft { // The mappings can be changed at any time, and must be in the following format. // snapshot_YYYYMMDD Snapshot are built nightly. // stable_# Stables are built at the discretion of the MCP team. // Use non-default mappings at your own risk. they may not always work. // Simply re-run your setup task after changing the mappings to update your workspace. mappings channel: 'snapshot', version: '20200913-1.15.1' // makeObfSourceJar = false // an Srg named sources jar is made by default. uncomment this to disable. // accessTransformer = file('src/main/resources/META-INF/accesstransformer.cfg') // Default run configurations. // These can be tweaked, removed, or duplicated as needed. runs { client { workingDirectory project.file('run') // Recommended logging data for a userdev environment property 'forge.logging.markers', 'SCAN,REGISTRIES,REGISTRYDUMP' // Recommended logging level for the console property 'forge.logging.console.level', 'debug' mods { techmod { source sourceSets.main } } } server { workingDirectory project.file('run') // Recommended logging data for a userdev environment property 'forge.logging.markers', 'SCAN,REGISTRIES,REGISTRYDUMP' // Recommended logging level for the console property 'forge.logging.console.level', 'debug' mods { techmod { source sourceSets.main } } } data { workingDirectory project.file('run') // Recommended logging data for a userdev environment property 'forge.logging.markers', 'SCAN,REGISTRIES,REGISTRYDUMP' // Recommended logging level for the console property 'forge.logging.console.level', 'debug' args '--mod', 'techmod', '--all', '--output', file('src/generated/resources/'), '--existing', file('src/main/resources/') mods { techmod { source sourceSets.main } } } } } dependencies { // Specify the version of Minecraft to use, If this is any group other then 'net.minecraft' it is assumed // that the dep is a ForgeGradle 'patcher' dependency. And it's patches will be applied. // The userdev artifact is a special name and will get all sorts of transformations applied to it. minecraft 'net.minecraftforge:forge:1.15.2-31.2.31' // You may put jars on which you depend on in ./libs or you may define them like so.. // compile "some.group:artifact:version:classifier" // compile "some.group:artifact:version" // Real examples // compile 'com.mod-buildcraft:buildcraft:6.0.8:dev' // adds buildcraft to the dev env // compile 'com.googlecode.efficient-java-matrix-library:ejml:0.24' // adds ejml to the dev env // The 'provided' configuration is for optional dependencies that exist at compile-time but might not at runtime. // provided 'com.mod-buildcraft:buildcraft:6.0.8:dev' // These dependencies get remapped to your current MCP mappings // deobf 'com.mod-buildcraft:buildcraft:6.0.8:dev' // For more info... // http://www.gradle.org/docs/current/userguide/artifact_dependencies_tutorial.html // http://www.gradle.org/docs/current/userguide/dependency_management.html } // Example for how to get properties into the manifest for reading by the runtime.. jar { manifest { attributes([ "Specification-Title": "realistech", "Specification-Vendor": "examplemodsareus", "Specification-Version": "1", // We are version 1 of ourselves "Implementation-Title": project.name, "Implementation-Version": "${version}", "Implementation-Vendor" :"examplemodsareus", "Implementation-Timestamp": new Date().format("yyyy-MM-dd'T'HH:mm:ssZ") ]) } } // Example configuration to allow publishing using the maven-publish task // This is the preferred method to reobfuscate your jar file jar.finalizedBy('reobfJar') // However if you are in a multi-project build, dev time needs unobfed jar files, so you can delay the obfuscation until publishing by doing //publish.dependsOn('reobfJar') publishing { publications { mavenJava(MavenPublication) { artifact jar } } repositories { maven { url "file:///${project.projectDir}/mcmodsrepo" } } }

Whenever I change the mappings version in the build.gradle file to something other than the default MCP mappings, it causes genEclipseRuns to be unable to resolve forge dependencies. Gradle Log:

That fixed it, thanks.

Whoops, forgot to put links to my source. Recipe Type Class: https://github.com/Awsomekeldeo/RealisTech/blob/6ec72fec9334633460b9ac9305626bc18272c680/src/main/java/awsome/realistech/api/recipe/NonConsumingShapelessRecipe.java Recipe Type Serializer: https://github.com/Awsomekeldeo/RealisTech/blob/6ec72fec9334633460b9ac9305626bc18272c680/src/main/java/awsome/realistech/api/recipe/NonConsumingShaplessRecipeSerializer.java

So I have a recipe type that is supposed to not consume certain inputs. For some reason, whenever I craft a custom recipe of that type, it sets the output of the recipe to air after the output item is placed in the player's inventory. I've tried poking around with eclipse's debugger, but to no avail. If anyone knows why this is happening, help would be greatly appreciated.

I would need the recipe to not consume an input, probably should have specified that.

Just a quick question. I already know how to add a custom recipe type, but I don't know how to allow it to be used with the vanilla crafting table ore inventory crafting.

ok, that's what I figured