Search the Forums BEFORE making a new post.

Oredictionary issues

Posted March 20, 201510 yr

Hey, I am getting this crash after registering ores: http://pastebin.com/SnFrfL3N

I understand that it's an issue with damage values, but I don't get why it is doing it...

Here's the code registering the oreDict stuff:

	OreDictionary.registerOre("ingotCopper", new ItemStack(itemRegist.ingots));
	OreDictionary.registerOre("ingotLead", new ItemStack(itemRegist.ingots, 1, 3));
	OreDictionary.registerOre("ingotTin", new ItemStack(itemRegist.ingots, 2, 3));
	OreDictionary.registerOre("ingotNickel", new ItemStack(itemRegist.ingots,3, 3));
	OreDictionary.registerOre("ingotAluminum", new ItemStack(itemRegist.ingots, 4, 3));
	OreDictionary.registerOre("ingotSilver", new ItemStack(itemRegist.ingots, 5, 3));

And if I comment that out, everything runs just fine. And I have tried that code like that and like

	OreDictionary.registerOre("ingotCopper", new ItemStack(itemRegist.ingots));
	OreDictionary.registerOre("ingotLead", new ItemStack(itemRegist.ingots, 1));
	OreDictionary.registerOre("ingotTin", new ItemStack(itemRegist.ingots, 2));
	OreDictionary.registerOre("ingotNickel", new ItemStack(itemRegist.ingots,3));
	OreDictionary.registerOre("ingotAluminum", new ItemStack(itemRegist.ingots, 4));
	OreDictionary.registerOre("ingotSilver", new ItemStack(itemRegist.ingots, 5));

both of which had the same outcome...

Sorry for sounding like a noob on something that is probably really obvious, but I just don't know what is wrong, as that looks fine to me, and using it (this code) without the metadata item(s) works just fine...

Why bother?

Quote

March 20, 201510 yr

Author

This means that
itemRegist.ingots
is
null
at the point where this code runs.

THAT WOULD BE WHY!

I always do that and never notice why v_v Thanks

I tried registering ores before registering items... Sometimes I feel like a complete idiot

Why bother?

Quote

March 20, 201510 yr

Another thing might be this: in your ItemStack constructor you might be filling in the parameters wrongly: the first parameter is the Item, the second is the stacksize and the third is the metadata/item damage. So in the first case you're not actually defining a damage value (the constructor thus sets it to 0). In the second, you're setting the damage value to 3 for each ItemStack.

So, assuming this is what you want, here's the correction:

OreDictionary.registerOre("ingotCopper", new ItemStack(itemRegist.ingots));
	OreDictionary.registerOre("ingotLead", new ItemStack(itemRegist.ingots, 3, 1));
	OreDictionary.registerOre("ingotTin", new ItemStack(itemRegist.ingots, 3, 2));
	OreDictionary.registerOre("ingotNickel", new ItemStack(itemRegist.ingots,3, 3));
	OreDictionary.registerOre("ingotAluminum", new ItemStack(itemRegist.ingots, 3, 4));
	OreDictionary.registerOre("ingotSilver", new ItemStack(itemRegist.ingots, 3, 5));

Quote

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.

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

Reply to this topic...

https://forums.minecraftforge.net/topic/28628-oredictionary-issues/

Followers

Go to topic listing

IPS spam blocked by CleanTalk.

Announcements

How to change player renderer and transform model parts?

I have been trying for a while now to make a custom player renderer, and replace the vanilla player renderer with it. So far I've come up with a custom player renderer class that extends vanilla PlayerRenderer:
package com.FireDude123.BOTW.entity.renderer; import com.mojang.blaze3d.vertex.PoseStack; import net.minecraft.client.player.AbstractClientPlayer; import net.minecraft.client.renderer.MultiBufferSource; import net.minecraft.client.renderer.entity.player.PlayerRenderer; import net.minecraft.client.renderer.entity.EntityRendererProvider; import net.minecraftforge.client.event.RenderPlayerEvent; import net.minecraftforge.common.MinecraftForge; public class PoseablePlayerRenderer extends PlayerRenderer { public PoseablePlayerRenderer(EntityRendererProvider.Context ctx, boolean slim) { super(ctx, slim); System.out.println("here too"); } @Override public void render(AbstractClientPlayer p_117788_, float p_117789_, float p_117790_, PoseStack poseStack, MultiBufferSource p_117792_, int p_117793_) { System.out.println("didnt get here lol"); model.leftArm.xRot=(float)Math.toRadians(160); super.render(p_117788_, p_117789_, p_117790_, poseStack, p_117792_, p_117793_); } } As you can see, the intended purpose of this is to raise the player's left arm by 160 degrees. However, combined with this logic in ClientModEvents:
@Mod.EventBusSubscriber(modid = MODID, bus = Mod.EventBusSubscriber.Bus.MOD, value = Dist.CLIENT) public static class ClientModEvents { @SubscribeEvent public static void onClientSetup(FMLClientSetupEvent event) { EntityRenderers.register((EntityType<? extends AbstractClientPlayer>)(EntityType<?)EntityType.PLAYER, ctx -> new PoseablePlayerRenderer(ctx, true)); EntityRenderers.register(Entities.MAGNESIS_BLOCK.get(), com.FireDude123.BOTW.entity.renderer.BlockDisplayRenderer::new); EntityRenderers.register(Entities.REMOTE_BOMB.get(), ThrownItemRenderer::new); EntityRenderers.register(Entities.CRYONIS_ICE.get(), com.FireDude123.BOTW.entity.renderer.BlockDisplayRenderer::new); EntityRenderers.register(Entities.STASIS_BLOCK.get(), FallingBlockRenderer::new); } @SubscribeEvent public static void registerLayerDefinitions(EntityRenderersEvent.RegisterLayerDefinitions event) { event.registerLayerDefinition(new ModelLayerLocation(new ResourceLocation(BOTW.MODID, "paraglider"), "main"), ParagliderLayer::createBodyLayer); } }(I also have a paraglider layer here for something else, it's working perfectly fine, also I used the slim setting because the player is slim in 1.20.1 forge)
This logic isn't replacing the renderer, as far as I can tell. Can someone please advise as to why, and how to fix it?

By FireDude123 · Posted 15 hours ago15 hr
How to add my mob to another mod's biome in 1.20.1.

I'm on 1.20.1 and was wondering if there was a way to add a mob I am going to make to a other mod's biome (Regions Unexplored in this case). I am trying to figure this out before I start coding the mod. Could someone point me to a good guide on this? I saw some things about biome modifier's but all the resources are either to short, unhelpful or for a different version. Thanks in advance. (i am a beginner but i have java and modding knowledge so this isn't like a "i am new and don't know anything about coding" problem btw)

By ilov3gam3z · Posted 23 hours ago23 hr
Help with file conversion

Many Forge users seek help with file conversions. Similarly, managing your health can benefit from structured tools like the https://wellness-app.com/calculator/fasting-calculator/ and a free intermittent fasting calculator. These tools help you plan and personalize your fasting and eating windows based on your lifestyle and goals. By entering your preferred fasting duration and meal times, you receive a tailored schedule that makes intermittent fasting easier to follow. Just as mastering file conversions improves modding success, using a fasting calculator brings clarity and structure to your health routine, supporting better results over time.

By Brialeblanc · Yesterday at 10:34 AM1 day
Cobblemon invalid player data

Hi everyone, I keep getting "invalid player data" when trying to log onto my friend's server. Log analysis says to remove Night Lights and ImmediatelyFast, but that doesn't work. Any insight is appreciated

Log: https://mclo.gs/uj6pMkd

By CobbleDN · Posted Yesterday at 04:14 AM1 day
Bad pathfinding for big mobs (1.21.1)

I've struggled with this for way too long now, so I have decided to ask for some assistance here because there is almost no information about this online.

I made a hostile mob and I built it like this:
public static final Supplier<EntityType<Bunyip>> BUNYIP = ENTITY_TYPES.register("bunyip" , () -> EntityType.Builder. of(Bunyip::new, MobCategory.MONSTER).sized(3f, 2.5f).eyeHeight(1.75f).build("bunyip"));

However, I have discovered that a BoundingBox of 3 is too big for the vanilla pathfinding to work well. In fact, anything bigger than a block will not work well. This is especially noticeable when having it chase a player in a negative X and/or negative Z direction. The mob starts spinning, walking backwards, walking diagonally, etc.

I am using the Goal system:
protected void registerGoals() { super.registerGoals(); this.goalSelector.addGoal(1, new MeleeAttackGoal(this, 1.25, true)); this.targetSelector.addGoal(2, new NearestAttackableTargetGoal<>(this, Player.class, true, true)); }

This does not seem to be a me issue as the ravager, one of the biggest vanilla mobs, also struggles with proper pathfinding. I am a bit familiar with how Minecraft's pathfinding works, but not enough to make a pathfinding system from scratch (or at least not in a reasonable amount of time). Is there any way to fix this with some tweaks or will I have to make a custom pathfinding system?

By VictorEvers · Posted Tuesday at 08:42 PM1 day

Sign In

Oredictionary issues

Featured Replies

Join the conversation

Posts

How to change player renderer and transform model parts?

How to add my mob to another mod's biome in 1.20.1.

Help with file conversion

Cobblemon invalid player data

Bad pathfinding for big mobs (1.21.1)

Who's Online (See full list)

Important Information

Account

Navigation

Search

Configure browser push notifications

Chrome (Android)

Chrome (Desktop)

Safari (iOS 16.4+)

Safari (macOS)

Edge (Android)

Edge (Desktop)

Firefox (Android)

Firefox (Desktop)