Jump to content

Leaderboard

Popular Content

Showing content with the highest reputation on 11/11/24 in all areas

  1. The information from xndir worked for me. Alsp in my case, similar errors appear for fluid blocks in the new version, indicating that adjustments are also necessary. Without these changes, an error message stating “block id not set” will appear. The following code example demonstrates how to correctly configure the fluid block: public static final RegistryObject<LiquidBlock> EXAMPLE_FLUID_BLOCK = BlocksRegister.BLOCKS.register( "example_fluid_block", () -> new ExampleFluidBlock( EXAMPLE_FLUID, Block.Properties.ofFullCopy(Blocks.WATER) .noCollission() .strength(1000.0F) .noOcclusion() .setId( ResourceKey.create( ForgeRegistries.BLOCKS.getRegistryKey(), ResourceLocation.parse( String.format("%s:%s", ExampleMod.MOD_ID, "example_fluid_block") ) ) ) ) );
    1 point
  2. Fabric explains it a bit here, Forge needs to provide a guide for 1.21.3 since the examples are Fabric specific: https://fabricmc.net/2024/10/14/1212.html EDIT: This seems to work but I don't know if this is the proper way to do it. Truly an annoying change especially if you have lots of items and blocks: Old: public static final RegistryObject<Item> ITEM_EGG = ITEMS.register("egg", () -> new Item(new Item.Properties())); New: ITEM_EGG = ITEMS.register("egg", () -> new Item(new Item.Properties().useItemDescriptionPrefix().setId(ResourceKey.create(Registries.ITEM, ResourceLocation.parse("modid:egg"))))); Neo also has more on the topic: https://neoforged.net/news/21.2release/
    1 point
×
×
  • Create New...

Important Information

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