Rai-The-Jultak

Ah I see, that does seem like a lot, especially as this is for *a modpack. with a world. and a server.* and not all the mods are going to have this in mind. I’ll take a look out of curiosity but I’m likely just going to do a workaround where I just strategically convert all these blocks into stained clay or something and then replace them back using an editor following the world conversion.

Hello! I’m in the long awaited process of updating my mod from 1.12 to 1.18. I made a test world with an array of the original blocks in 1.12 and dropped it into my dev environment and upon loading the world, the blocks were not loaded. Is there a way to ensure they get copied over properly? I have all the names (registration and resource locations) spelled the same way, along with the same directories across both versions of the mod. Update: I have yet to make a language file too, but I assumed that wouldn’t make a difference.

That’s a great overview, thanks!

Hello, I'm currently updating an older geology-themed mod of mine which had a workaround of several "base" ores that, upon world generation, they would change into their final state according to y-level. Specifically I am looking for a method called when the block is naturally generated in the world. Since its looking like onBlockAdded is gone, are loot tables + blockstate jsons the proper way to do this?

Thanks, I'll get that moved over! Figured out the main problem. I included ModelLayerLocation when constructing, which ended up overriding the model layer and the information was getting dropped on the way to EntityRenderers. public SteamEngineRenderer(EntityRendererProvider.Context pContext, ModelLayerLocation pLayer) { super(pContext, ModelLayers.MINECART); } Compiling gave this error: error: incompatible types: invalid constructor reference event.registerEntityRenderer(STEAM_ENGINE.get(), SteamEngineRenderer::new); ^ constructor SteamEngineRenderer in class SteamEngineRenderer cannot be applied to given types required: Context,ModelLayerLocation found: Context reason: actual and formal argument lists differ in length Removing it did the trick. public SteamEngineRenderer(EntityRendererProvider.Context pContext) { super(pContext, ModelLayers.MINECART); } I'm going to make a github and maybe even a tutorial for this at some point.

Hello! I am attempting to spin off the vanilla furnace cart to add some additional features. In my main mod class, I am getting this error when adding the entity and renderer. I included the renderer as a method reference but IntelliJ does not seem to recognize it as one. I'd appreciate any help as this seems to be the only thing standing between me and better furnace carts. Currently I'm going about making a separate entity, but I'm wondering if there's an easier way that could avoid this issue altogether too. 'register(net.minecraft.world.entity.EntityType<? extends T>, net.minecraft.client.renderer.entity.EntityRendererProvider<T>)' in 'net.minecraft.client.renderer.entity.EntityRenderers' cannot be applied to '(net.minecraftforge.registries.RegistryObject<net.minecraft.world.entity.EntityType<com.rai.klajultweaks.vehicle.SteamEngineEntity>>, <method reference>)' Client-side registration in main mod file private void clientsetup(final FMLClientSetupEvent event) { EntityRenderers.register(ModEntities.STEAM_ENGINE,SteamEngineRenderer::new); } Renderer package com.rai.klajultweaks.vehicle; import net.minecraft.client.model.geom.ModelLayerLocation; import net.minecraft.client.model.geom.ModelLayers; import net.minecraft.client.renderer.entity.EntityRendererProvider; import net.minecraft.client.renderer.entity.MinecartRenderer; public class SteamEngineRenderer extends MinecartRenderer { public SteamEngineRenderer(EntityRendererProvider.Context pContext, ModelLayerLocation pLayer) { super(pContext, ModelLayers.MINECART); } }