Search the Forums BEFORE making a new post.

Setting output path for generated custom recipes

Posted July 10, 20205 yr

Hello all, new day, new low effort meme

On to the problem, I've decided to do datagen for the recipes for my grinder, which you can see here:
https://github.com/MistaOmega/Opes/blob/master/src/main/java/mistaomega/opes/datagen/GrindingRecipeBuilder.java

It's basically a slightly rewritten ShapedRecipeBuilder without things like keys and whatnot

The thing I would like to do is set a constant location for what I make, say for example, I need a recipe for diamonds from diamond ore, this will go under opes/recipes/grinder/diamond.json

I thought this line would be the culprit: https://github.com/MistaOmega/Opes/blob/master/src/main/java/mistaomega/opes/datagen/GrindingRecipeBuilder.java#L84

More importantly the "pathIn" field, but no matter what I change it to, it always outputs as minecraft/recipes/diamond.json

Where could I set this file path so that it goes where I would like it to?

Thank you all, covid safe hugs to whoever has the big brain to solve❤️

~Omega

Edited July 10, 20205 yr by MistaOmega

Quote

July 10, 20205 yr

Not sure but you did not pass your mod id into the resource location?

Quote

July 10, 20205 yr

You use the #build(Consumer) overload of your GrindingRecipeBuilder, which uses the registry name of the result ItemStack for the recipe ID. In all of your cases, the items come from vanilla Minecraft ("minecraft:diamond", "minecraft:glowstone", etc.), meaning the recipe ID is the same so they are stored under the "minecraft" namespace. Use the #build(Consumer, ResourceLocation) overload to pass in your own custom recipe ID ("opes:grinder/diamond" for 'data/opes/recipes/grinder/diamond').

Quote

July 10, 20205 yr

Author

8 hours ago, sciwhiz12 said:

You use the #build(Consumer) overload of your GrindingRecipeBuilder, which uses the registry name of the result ItemStack for the recipe ID. In all of your cases, the items come from vanilla Minecraft ("minecraft:diamond", "minecraft:glowstone", etc.), meaning the recipe ID is the same so they are stored under the "minecraft" namespace. Use the #build(Consumer, ResourceLocation) overload to pass in your own custom recipe ID ("opes:grinder/diamond" for 'data/opes/recipes/grinder/diamond').

10 hours ago, poopoodice said:

Not sure but you did not pass your mod id into the resource location?

Thank you both

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/88218-setting-output-path-for-generated-custom-recipes/

Followers

Go to topic listing

IPS spam blocked by CleanTalk.

Announcements

Is this forum active?

hello everyone..!

By WinX · 2 hours ago2 hr
How to add my mob to another mod's biome in 1.20.1.

tysm

By ilov3gam3z · 15 hours ago15 hr
Orbital strike cannon fishing rod mod

was focused on school so didnt respond u think ur gonna get 1.21+ done by this week? @FoxyWoxy

By Astoxy · 21 hours ago21 hr
How to add my mob to another mod's biome in 1.20.1.

You can add mob spawns using Forge's Biome Modifiers feature. I won't go into details on how to use a data generator for them, but here's a simple example:
{ "type": "forge:add_spawns", // Required "biomes": "#namespace:biome_tag", // Accepts a biome id, [list of biome ids], or #namespace:biome_tag "spawners": { "type": "namespace:entity_type", // Type of mob to spawn "weight": 100, // int, spawn weighting "minCount": 1, // int, minimum pack size "maxCount": 4 // int, maximum pack size } }This JSON file would go somewhere like this: data/modid/forge/biome_modifier/your_biome_modifier.json

By Jonathing · Yesterday at 12:10 AM1 day
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 Thursday at 12:07 AM2 days

Choonster

Sign In

Setting output path for generated custom recipes

Featured Replies

Join the conversation

Posts

Is this forum active?

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

Orbital strike cannon fishing rod mod

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

How to change player renderer and transform model parts?

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)