Jump to content

EntityItem: What is that?!?


kauan99

Recommended Posts

Here I am again, with my poor English and poorer mod coding skills, to bother you guys once more.

 

So, I've completed some successful tests, creating a few blocks that do crazy stuff like making it rain and turning night into day and vice versa. Preparing the way so one day I can master GUI, TileEntities, NBT and Containers and all that circus.

 

I've been reading the code for BlockContainer, and BlockChest for hours now (didn't touch the TileEntity code itself, but I'm being able to figure out it's role everytime it appears in the code - thanks to Senitiel and specially Mazetar for his brief crystal clear explanation on a lot of complex concepts).

 

Suddenly, a wild EntityItem appears. I read it's code. There's not much of it. But I can't understand what it is. Maybe it's something simple that I can't understand due to exaustion? It's like some kind of "box" around an ItemStack, I think? but I can't understand why it exists.

 

What's even more amazing is that I understood the rest of the code so far! With all those par1, par2, par3, parFuckYouCode... Who's to blame for those cursed meaningless names? Forge? MCP? Notch?

 

So, to make it clear, what is an EntityItem? Why do we need that class?

 

Thanks!

 

edit: yeah... at the end of the method I'm reading (BlockChest.breakBlock()) there's yet another surprise: at the very last line of the method there's a call to World.func_96440_m(). What the hell?  :'(

WIP mods: easyautomation, easyenergy, easyelectronics, easymoney, easytrasportation, easysecurity, easymultiverse, easyfactions, easymagick, easyalchemy, easyseasons

Link to comment
Share on other sites

Oh, so that's the names of things prior to deobfuscation! It makes perfect sense now (I was not sure of the meaning of obfuscation/deobfuscation before now. God, I'm stupid).

 

Ok, so EntityItem is a dropped ItemStack. Still weird, but ok. I can live with that. Thanks!!

WIP mods: easyautomation, easyenergy, easyelectronics, easymoney, easytrasportation, easysecurity, easymultiverse, easyfactions, easymagick, easyalchemy, easyseasons

Link to comment
Share on other sites

Oh, so that's the names of things prior to deobfuscation! It makes perfect sense now (I was not sure of the meaning of obfuscation/deobfuscation before now. God, I'm stupid).

 

Ok, so EntityItem is a dropped ItemStack. Still weird, but ok. I can live with that. Thanks!!

 

[*]That's not quite correct :P The names prior to the deobfuscation (the "real" obfuscation encountered in the original minecraft.jar) has names like "a" or "z" or "xy". If you run the deobfuscation, the names will first be translated to so-called "SRG"-names (indices given by MCP), which are called "func_xxxx" for methods/functions or "field_xxxx" for fields/variables. After that, these will be translated into "CSV"-names and they'll get "sense-making" names like "registerIcon(...)" or the like. If the CSV mappings don't contain such a name, the name will simply stay like "func_xxx/field_xxx".

[*]It's not that weird ;) The ItemStack is only for seperately instantiating items (you may notice the actual item class is only instanciated once) to save NBTTags (enchantments, for example), save the damage value (tools) / metadata (dyes) and the stack size. The EntityItem is only there for "outside" interactions with the environment (like picking them up or dying in lava/fire).

Don't ask for support per PM! They'll get ignored! | If a post helped you, click the "Thank You" button at the top right corner of said post! |

mah twitter

This thread makes me sad because people just post copy-paste-ready code when it's obvious that the OP has little to no programming experience. This is not how learning works.

Link to comment
Share on other sites

I'm still confused about deobfuscation and all that, but I think that's not critical knowledge for mod codding, so I'm not gonna try to learn any further about that. I totally understand EntityItem now, thank you very much for clarifying that, SanAndreasP!

WIP mods: easyautomation, easyenergy, easyelectronics, easymoney, easytrasportation, easysecurity, easymultiverse, easyfactions, easymagick, easyalchemy, easyseasons

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

    • I am not using hardcoded recipes, I'm using Vanilla's already existing code for leather armor dying. (via extending and implementing DyeableArmorItem / DyeableLeatherItem respectively) I have actually figured out that it's something to do with registering item colors to the ItemColors instance, but I'm trying to figure out where exactly in my mod's code I would be placing a call to the required event handler. Unfortunately the tutorial is criminally undescriptive. The most I've found is that it has to be done during client initialization. I'm currently trying to do the necessary setup via hijacking the item registry since trying to modify the item classes directly (via using SubscribeEvent in the item's constructor didn't work. Class so far: // mrrp mrow - mcmod item painter v1.0 - catzrule ch package catzadvitems.init; import net.minecraft.client.color.item.ItemColors; import net.minecraft.world.item.Item; import net.minecraftforge.registries.ObjectHolder; import net.minecraftforge.fml.event.lifecycle.FMLClientSetupEvent; import net.minecraftforge.fml.common.Mod; import net.minecraftforge.eventbus.api.SubscribeEvent; import net.minecraftforge.client.event.ColorHandlerEvent; import catzadvitems.item.DyeableWoolArmorItem; @Mod.EventBusSubscriber(bus = Mod.EventBusSubscriber.Bus.MOD) public class Painter { @ObjectHolder("cai:dyeable_wool_chestplate") public static final Item W_CHEST = null; @ObjectHolder("cai:dyeable_wool_leggings") public static final Item W_LEGS = null; @ObjectHolder("cai:dyeable_wool_boots") public static final Item W_SOCKS = null; public Painter() { // left blank, idk if forge throws a fit if constructors are missing, not taking the chance of it happening. } @SubscribeEvent public static void init(FMLClientSetupEvent event) { new Painter(); } @Mod.EventBusSubscriber private static class ForgeBusEvents { @SubscribeEvent public static void registerItemColors(ColorHandlerEvent.Item event) { ItemColors col = event.getItemColors(); col.register(DyeableUnderArmorItem::getItemDyedColor, W_CHEST, W_LEGS, W_SOCKS); //placeholder for other dye-able items here later.. } } } (for those wondering, i couldn't think of a creative wool helmet name)
    • nvm found out it was because i had create h and not f
    • Maybe there's something happening in the 'leather armor + dye' recipe itself that would be updating the held item texture?
    • @SubscribeEvent public static void onRenderPlayer(RenderPlayerEvent.Pre e) { e.setCanceled(true); model.renderToBuffer(e.getPoseStack(), pBuffer, e.getPackedLight(), 0f, 0f, 0f, 0f, 0f); //ToaPlayerRenderer.render(); } Since getting the render method from a separate class is proving to be bit of a brick wall for me (but seems to be the solution in older versions of minecraft/forge) I've decided to try and pursue using the renderToBuffer method directly from the model itself. I've tried this route before but can't figure out what variables to feed it for the vertexConsumer and still can't seem to figure it out; if this is even a path to pursue.  The vanilla model files do not include any form of render methods, and seem to be fully constructed from their layer definitions? Their renderer files seem to take their layers which are used by the render method in the vanilla MobRenderer class. But for modded entities we @Override this function and don't have to feed the method variables because of that? I assume that the render method in the extended renderer takes the layer definitions from the renderer classes which take those from the model files. Or maybe instead of trying to use a render method I should be calling the super from the renderer like   new ToaPlayerRenderer(context, false); Except I'm not sure what I would provide for context? There's a context method in the vanilla EntityRendererProvider class which doesn't look especially helpful. I've been trying something like <e.getEntity(), model<e.getEntity()>> since that generally seems to be what is provided to the renderers for context, but I don't know if it's THE context I'm looking for? Especially since the method being called doesn't want to take this or variations of this.   In short; I feel like I'm super super close but I have to be missing something obvious? Maybe this insane inane ramble post will provide some insight into this puzzle?
  • Topics

×
×
  • Create New...

Important Information

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