Jump to content

Recipe Serialization for Custom Tipped Arrows


VoidCallerZ

Recommended Posts

I have a compressed variant of all vanilla tipped arrows. I followed all the code from vanilla for registering, effects etc. Now the arrows have appeared (Color still needs fixing aswell though) but the recipes don't work.

Now I see vanilla has RecipeSerializer.java where the TIPPED_ARROW recipe is registered with a TippedArrowRecipe::new

 

I have my own TippedArrowRecipe (UcTippedArrowRecipe) and I'm trying to register the recipe through UcRecipeSerializer.java, but when I do so I get the error "java.lang.IllegalStateException: Can not register to a locked registry. Modder should use Forge Register methods.". I can see I need to use Forge Register methods, but I'm not sure how to implement this properly. From looking up on Google I mostly get 1.16.x versions using IRecipe, which doesn't seem to exist in 1.18.x

 

public interface UcRecipeSerializer<T extends Recipe<?>> extends IForgeRegistryEntry<UcRecipeSerializer<?>>
{
    SimpleRecipeSerializer<UcTippedArrowRecipe> COMPRESSED_TIPPED_ARROW = register("crafting_special_compressed_tipped_arrow", new SimpleRecipeSerializer<>(UcTippedArrowRecipe::new));

    static <S extends UcRecipeSerializer<T>, T extends Recipe<?>> S register(String pKey, S pRecipeSerializer)
    {
        return Registry.register(Registry.RECIPE_SERIALIZER, pKey, pRecipeSerializer);
    }
}

This interface is then called in UcRecipes.java which is the recipes class for datageneration.

SpecialRecipeBuilder.special(UcRecipeSerializer.COMPRESSED_TIPPED_ARROW).save(consumer, "compressed_tipped_arrow");

 

Any help in the right direction would be appreciated!
And please ask if there are any additional questions or more code is required.

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

    • A friend found this code, but I don't know where. It seems to be very outdated, maybe from 1.12? and so uses TextureManager$loadTexture and TextureManager$deleteTexture which both don't seem to exist anymore. It also uses Minecraft.getMinecraft().mcDataDir.getCanonicalPath() which I replaced with the resource location of my texture .getPath()? Not sure if thats entirely correct. String textureName = "entitytest.png"; File textureFile = null; try { textureFile = new File(Minecraft.getMinecraft().mcDataDir.getCanonicalPath(), textureName); } catch (Exception ex) { } if (textureFile != null && textureFile.exists()) { ResourceLocation MODEL_TEXTURE = Resources.OTHER_TESTMODEL_CUSTOM; TextureManager texturemanager = Minecraft.getMinecraft().getTextureManager(); texturemanager.deleteTexture(MODEL_TEXTURE); Object object = new ThreadDownloadImageData(textureFile, null, MODEL_TEXTURE, new ImageBufferDownload()); texturemanager.loadTexture(MODEL_TEXTURE, (ITextureObject)object); return true; } else { return false; }   Then I've been trying to go through the source code of the reload resource packs from minecraft, to see if I can "cache" some data and simply reload some textures and swap them out, but I can't seem to figure out where exactly its "loading" the texture files and such. Minecraft$reloadResourcePacks(bool) seems to be mainly controlling the loading screen, and using this.resourcePackRepository.reload(); which is PackRepository$reload(), but that function seems to be using this absolute confusion of a line List<String> list = this.selected.stream().map(Pack::getId).collect(ImmutableList.toImmutableList()); and then this.discoverAvailable() and this.rebuildSelected. The rebuild selected seemed promising, but it seems to just be going through each pack and doing this to them? pack.getDefaultPosition().insert(list, pack, Functions.identity(), false); e.g. putting them into a list of packs and returning that into this.selected? Where do the textures actually get baked/loaded/whatever? Any info on how Minecraft reloads resource packs or how the texture manager works would be appreciated!
    • This might be a long shot , but do you remember how you fixed that?
    • Yeah, I'll start with the ones I added last night.  Wasn't crashing until today and wasn't crashing at all yesterday (+past few days since removing Cupboard), so deductive reasoning says it's likeliest to be one of the new ones.  A few horse armor mods and a corn-based add-on to Farmer's Delight, the latter which I hope to keep - I could do without the horse armor mods if necessary.  Let me try a few things and we'll see. 
    • Add crash-reports with sites like https://mclo.gs/ Add this mod: https://www.curseforge.com/minecraft/mc-mods/packet-fixer/files/5416165
  • Topics

×
×
  • Create New...

Important Information

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