Jump to content

[1.8] Keep IItemRenderer, or implement a programmatic way to generate models


TrashCaster

Recommended Posts

I would like to see IItemRenderer stay because I need to generate the model based on various ambiguous NBT tags.

 

For example, a player creates an item with custom components, based on any possible input, and the model in hand is a collaboration of all those items.

 

I really need this feature for a mod I am working on, so some way of creating models through the mod's code, and not through model files, would be best.

Link to comment
Share on other sites

The theory is to never need to create models in code EVER again.

But to simply configure/combine/tweak models in code.

This way everything is well defined, caching can be done for performance enhancements, modelers/resource pack creators can edit things, less complicated rendering code, the list goes on.

 

So in your use case you would need to sit back and think of what the best approach is. It may be a radical shift from your current code but the benefits are plentiful.

I do Forge for free, however the servers to run it arn't free, so anything is appreciated.
Consider supporting the team on Patreon

Link to comment
Share on other sites

So you want your model to render a series of sub-models based on nbt, when you're given the nbt to handle in a function that returns a IModel you could simply return a new/cached model that is a wrapper that combines all the sub-models.

I do Forge for free, however the servers to run it arn't free, so anything is appreciated.
Consider supporting the team on Patreon

Link to comment
Share on other sites

I want to render the same compiled model for being on the ground, in the inventory, in hand in first person, and in hand in third person.

 

This is why I need IItemRenderer.

 

It had the ability to render said model, which I would be rendering on the go based on the blocks stored in the itemstack.

 

Rendering it on the head is relatively simple, as there is the RenderPlayerEvent.

 

But there's no "RenderItemEvent". IItemRenderer was that event, essentially.

 

I want to iterate through a list of itemstacks stored on the itemstack (via a compound tag list) that is either equipped, or in hand/inventory/on the ground, and render each block.

 

If it's possible to do that without the use of IItemRenderer, then it would be very swell to have a link returned.

 

I'm all for keeping the methods of rendering to the new default way, but we at least need a way to compile our own unique, per-itemstack models on the fly.

 

As for your suggestion, if it still pertains to the above re-defined description, how would I go about doing that? Do we already have tutorials made for going from using the old IItemRenderer + GL function and Tessellator method to this new system? If it isn't possible to do what I am describing with the new rendering method, then why abandon a functional component, that does get it done, without limiting the creative boundaries of Minecraft. I would say it should be noted to use the new system as much as possible, but if you really must, then feel free to use the old method.

Link to comment
Share on other sites

Ah, ok. I see it got added in a version later than I was using. I'm updating as we speak, and I will try this.

 

Thanks for the quick replies, it is much obliged.

 

Any further questions, and I will post in the support section.

 

Thanks a bunch. Feel free to close/lock this thread.

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.