Jump to content

1.10.2 ItemBlock with Variant [SOLVED]


NoPlotBlog

Recommended Posts

I know this has been asked a million times, and I've tried following the example that Choonster has very graciously provided.  Most everything is working exactly like I would expect, except that my items are not rendering.  They are registered, but I get the lovely little purple/black boxes.

 

I've created a Git repository to help show what I've done.

My Main class:

https://github.com/meganmorgangames/Sweets/blob/master/SweetsMod/src/java/com/meganmorgangames/sweets/Sweets.java

My Variant Block class:

https://github.com/meganmorgangames/Sweets/blob/master/SweetsMod/src/java/com/meganmorgangames/sweets/block/SweetsPlanks.java

My Block Registering class:

https://github.com/meganmorgangames/Sweets/blob/master/SweetsMod/src/java/com/meganmorgangames/sweets/init/ModBlocks.java

BlockState JSON

https://github.com/meganmorgangames/Sweets/blob/master/SweetsMod/src/resources/assets/sweets/blockstates/planks.json

Block JSONs

https://github.com/meganmorgangames/Sweets/blob/master/SweetsMod/src/resources/assets/sweets/models/block/candycane_planks.json

https://github.com/meganmorgangames/Sweets/blob/master/SweetsMod/src/resources/assets/sweets/models/block/gumdrop_planks.json

 

I had Item JSONs, but I deleted them because I thought maybe they were interfering with the process.  The blocks render just fine, and it seems like maybe the items are named wrong for some reason?  They appear as tile.sweets:planks.candycane.name and the same for gumdrop, but even when I created item models named planks.candycane, they didn't render.

 

Normally, I can figure these things out, but I think I've been staring at the forest too long.  First foray into 1.10.2 is more than a little bit frustrating...lol

 

Thanks for any help you can offer.

Edited by NoPlotBlog
Figured it out
Link to comment
Share on other sites

Nevermind.  You step away, have a bite, smoke a cigarette, then realize there is an entire class you forgot to include that's entire purpose is to render items and itemblocks....Sheesh.

 

Thank you for the response, though, Jay.  In the future, if I have issues, I will included a link to the log from my test run.

Edited by NoPlotBlog
spelling errors
Link to comment
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Unfortunately, your content contains terms that we do not allow. Please edit your content to remove the highlighted words below.
Reply to this topic...

×   Pasted as rich text.   Restore formatting

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Announcements



  • Recently Browsing

    • No registered users viewing this page.
  • Posts

    • Right now im trying to make an own mod for minecraft for the version 1.16.5 with forge but whatever i do it still doesnt fix the error this is my build.gradle : buildscript { repositories { maven { url = "https://maven.minecraftforge.net" } mavenCentral() } dependencies { classpath 'net.minecraftforge.gradle:ForgeGradle:5.1.+' } } apply plugin: 'net.minecraftforge.gradle' apply plugin: 'java' group = 'com.example' // Modify to your package name version = '1.0' archivesBaseName = 'flippermod' java { toolchain { languageVersion = JavaLanguageVersion.of(8) } } minecraft { version = "1.16.5-36.2.42" // Ensure this matches your Forge version mappings channel: 'official', version: '1.16.5' runs { client { workingDirectory project.file('run') property 'forge.logging.markers', 'SCAN,REGISTRIES,REGISTRYDUMP' property 'forge.logging.console.level', 'debug' mods { flipper_mod { sourceSets.main.output } } } } } repositories { maven { url = "https://maven.minecraftforge.net/" } mavenCentral() } dependencies { minecraft "net.minecraftforge:forge:1.16.5-36.2.42" } and this one is my settings.gradle:  pluginManagement { repositories { gradlePluginPortal() maven { name = 'MinecraftForge' url = 'https://maven.minecraftforge.net/' } } } plugins { id 'org.gradle.toolchains.foojay-resolver-convention' version '0.7.0' } rootProject.name = 'flippermod' this one is the mods.tml    modLoader="javafml" loaderVersion="[36,)" modId="flippermod" version="1.0.0" displayName="Flippermod" and the last one is the gradle-wrapper.properties distributionUrl=https\://services.gradle.org/distributions/gradle-7.6-bin.zip dc :"code_slivki"
    • Today I tried downloading 1.16.5 forge (the recommended version) and when installing I selected "download client". At the end just before appeared "These libraries failed to download. Try again." and at the bottom there were "org.apache.logging.log4j:log4j-api:2.15.0 ; org.apache.logging.log4j:log4j-core:2.15.0 and org.apache.logging.log4j:log4j-slf4j18-impl2.15.0" I tried the newest version and the same thing appeared
    • I think the problem is the server doesn't have enough ram, but I need to be sure before buying more. The modpack I use is Craft of exile 2 and the server has 4gb ram. When I try to turn it on I get a bunch of warns and at the end it just says "[Multicraft] Skipped 564 lines due to rate limit (160/s)" Is there a way to increase the rate limit? One time it did start, but without half of the mods. The modpack works perfectly fine on my computer even if I have the launch ram limit to 4gb.
    • Nevermind, RedstoneWireBlock.java had what I needed. Surprised I didn't try looking there until now.
    • I tried to open my Minecraft world normally and got the error "Errors in currently selected data pacts prevented the world from loading." Trying to start in safe mode gives the error "This world contains invalid or corrupted save data." My recent log is too large to make a Pastebin link. Any help would be much appreciated. 
  • Topics

×
×
  • Create New...

Important Information

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