Jump to content

[1.12] [SOLVED] Recipe JSON - Questions about using Forge's Oredict container item


RazzaAzza

Recommended Posts

Hi guys, I'm trying to use forge ore dictionary with multiple hammer types (multiple metal types) to be utilized in crushing shards and dust. I ran into problems trying to add data and the wildcard value for the ore dictionary type (Shown below).

 

{
  "type": "forge:ore_shapeless",
  "ingredients": [
    {
      "type": "forge:ore_dict",
      "ore": "hammer",
      "data": 32767
    },
    {
      "item": "soa:amethyst",
      "data": 1
    }
  ],
  "result": {
    "item": "soa:amethyst",
    "data": 2,
    "count": 4
  }
}

 

This method doesn't work. Without calling the wildcard value ("data": 32767), it works but stops working after one use. I'm unsure if there is a way using multiple hammers for a recipe like this or I need to do one hammer type per shard to dust recipes. 

 

EDIT: Solved using Choonster's post below using his alternative method with compound ingredients in _constants.JSON and referencing it in my recipe's JSON.

 

Edited by RazzaAzza
[SOLVED] and Rewording
Link to comment
Share on other sites

39 minutes ago, RazzaAzza said:

This method doesn't work. Without calling the wildcard value ("data": 32767), it works but stops working after one use. I'm unsure if there is a way using multiple hammers for a recipe like this or I need to do one hammer type per shard to dust recipes.

The "data" parameter refers to metadata. This is so that a hammer of any damage amount can be used.

If you want multiple hammers, then you need to register them all with the Ore Dictionary.

Apparently I'm a complete and utter jerk and come to this forum just like to make fun of people, be confrontational, and make your personal life miserable.  If you think this is the case, JUST REPORT ME.  Otherwise you're just going to get reported when you reply to my posts and point it out, because odds are, I was trying to be nice.

 

Exception: If you do not understand Java, I WILL NOT HELP YOU and your thread will get locked.

 

DO NOT PM ME WITH PROBLEMS. No help will be given.

Link to comment
Share on other sites

Okay, I've registered my hammers to the Ore Dictionary. All hammers works in this JSON recipe: 

Spoiler

{
  "type": "forge:ore_shapeless",
  "ingredients": [
    {
      "type": "forge:ore_dict",
      "ore": "hammer"
    },
    {
      "item": "soa:brass",
      "data": 1
    }
  ],
  "result": {
    "item": "soa:brass",
    "data": 2,
    "count": 4
  }
}

 

 

However, all of them stops working after each is damaged. I've tried adding "data": 32767 (the wildcard value) after the "ore": "hammer", like this JSON below:

Spoiler

{
  "type": "forge:ore_shapeless",
  "ingredients": [
    {
      "type": "forge:ore_dict",
      "ore": "hammer",
      "data": 32767
    },
    {
      "item": "soa:brass",
      "data": 1
    }
  ],
  "result": {
    "item": "soa:brass",
    "data": 2,
    "count": 4
  }
}

   With the addition, all of them wont work. Is the "data" I placed was in a wrong place or do I need to insert wildcard value somewhere else for the hammers to work (after damage is done during crafting)? 

 

Alternatively using this JSON below (One Hammer per nugget to powder recipe):

Spoiler

{
  "type": "forge:ore_shapeless",
  "ingredients": [
    {
      "item": "soa:iron_hammer",
      "data": 32767
    },
    {
      "item": "soa:brass",
      "data": 1
    }
  ],
  "result": {
    "item": "soa:brass",
    "data": 2,
    "count": 4
  }
}

 

   Using this version, the recipe accepts the Iron Hammer regardless of its damage by using the wildcard value.  Not sure why the previous JSON using Ore Dictionary "hammer" would not accept the wildcard value.

Edited by RazzaAzza
Rewording + Additional notes
Link to comment
Share on other sites

The forge:ore_dict ingredient doesn't accept a data property, because it doesn't make sense to specify the metadata of an arbitrary list of items.

 

To allow a hammer with any damage value to be matched by the hammer ore name, you need to register the hammer to the Ore Dictionary using OreDictionary.WILDCARD_VALUE (32767) as the metadata value.

 

As an alternative to using the ore dictionary, you can use a compound ingredient anywhere you'd use a regular ingredient. Simply use an array of ingredient objects in the JSON instead of a single ingredient object. This will create an ingredient that matches any of the items matched by its child ingredients.

 

If you need to use this compound ingredient in multiple places, you can specify in _constants.json like this and reference it in a recipe like this.

Edited by Choonster
  • Like 1
  • Thanks 1

Please don't PM me to ask for help. Asking your question in a public thread preserves it for people who are having the same problem in the future.

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

    • They were already updated, and just to double check I even did a cleanup and fresh update from that same page. I'm quite sure drivers are not the problem here. 
    • i tried downloading the drivers but it says no AMD graphics hardware has been detected    
    • Update your AMD/ATI drivers - get the drivers from their website - do not update via system  
    • As the title says i keep on crashing on forge 1.20.1 even without any mods downloaded, i have the latest drivers (nvidia) and vanilla minecraft works perfectly fine for me logs: https://pastebin.com/5UR01yG9
    • Hello everyone, I'm making this post to seek help for my modded block, It's a special block called FrozenBlock supposed to take the place of an old block, then after a set amount of ticks, it's supposed to revert its Block State, Entity, data... to the old block like this :  The problem I have is that the system breaks when handling multi blocks (I tried some fix but none of them worked) :  The bug I have identified is that the function "setOldBlockFields" in the item's "setFrozenBlock" function gets called once for the 1st block of multiblock getting frozen (as it should), but gets called a second time BEFORE creating the first FrozenBlock with the data of the 1st block, hence giving the same data to the two FrozenBlock :   Old Block Fields set BlockState : Block{minecraft:black_bed}[facing=east,occupied=false,part=head] BlockEntity : net.minecraft.world.level.block.entity.BedBlockEntity@73681674 BlockEntityData : id:"minecraft:bed",x:3,y:-60,z:-6} Old Block Fields set BlockState : Block{minecraft:black_bed}[facing=east,occupied=false,part=foot] BlockEntity : net.minecraft.world.level.block.entity.BedBlockEntity@6d1aa3da BlockEntityData : {id:"minecraft:bed",x:2,y:-60,z:-6} Frozen Block Entity set BlockState : Block{minecraft:black_bed}[facing=east,occupied=false,part=foot] BlockPos{x=3, y=-60, z=-6} BlockEntity : net.minecraft.world.level.block.entity.BedBlockEntity@6d1aa3da BlockEntityData : {id:"minecraft:bed",x:2,y:-60,z:-6} Frozen Block Entity set BlockState : Block{minecraft:black_bed}[facing=east,occupied=false,part=foot] BlockPos{x=2, y=-60, z=-6} BlockEntity : net.minecraft.world.level.block.entity.BedBlockEntity@6d1aa3da BlockEntityData : {id:"minecraft:bed",x:2,y:-60,z:-6} here is the code inside my custom "freeze" item :    @Override     public @NotNull InteractionResult useOn(@NotNull UseOnContext pContext) {         if (!pContext.getLevel().isClientSide() && pContext.getHand() == InteractionHand.MAIN_HAND) {             BlockPos blockPos = pContext.getClickedPos();             BlockPos secondBlockPos = getMultiblockPos(blockPos, pContext.getLevel().getBlockState(blockPos));             if (secondBlockPos != null) {                 createFrozenBlock(pContext, secondBlockPos);             }             createFrozenBlock(pContext, blockPos);             return InteractionResult.SUCCESS;         }         return super.useOn(pContext);     }     public static void createFrozenBlock(UseOnContext pContext, BlockPos blockPos) {         BlockState oldState = pContext.getLevel().getBlockState(blockPos);         BlockEntity oldBlockEntity = oldState.hasBlockEntity() ? pContext.getLevel().getBlockEntity(blockPos) : null;         CompoundTag oldBlockEntityData = oldState.hasBlockEntity() ? oldBlockEntity.serializeNBT() : null;         if (oldBlockEntity != null) {             pContext.getLevel().removeBlockEntity(blockPos);         }         BlockState FrozenBlock = setFrozenBlock(oldState, oldBlockEntity, oldBlockEntityData);         pContext.getLevel().setBlockAndUpdate(blockPos, FrozenBlock);     }     public static BlockState setFrozenBlock(BlockState blockState, @Nullable BlockEntity blockEntity, @Nullable CompoundTag blockEntityData) {         BlockState FrozenBlock = BlockRegister.FROZEN_BLOCK.get().defaultBlockState();         ((FrozenBlock) FrozenBlock.getBlock()).setOldBlockFields(blockState, blockEntity, blockEntityData);         return FrozenBlock;     }  
  • Topics

×
×
  • Create New...

Important Information

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