Draco18s

UUID = Universally Unique Identifier You're not supposed to be able to change it.

Player dies -> Items automagically dropped.

What do you mean by "save an integer"?

ItemStack itemStack = slots[i]; slots[i].stackSize = 0; Mmm...pointers.... (Tip: ItemStack is passed by reference, not by value. When you set the stack size there, you're returning a stack of size zero: itemStack === slot[i] ).

Entirely possible I figure that the dragon is handled similarly to other mobs that duplicating it would follow similar logic, but I guess not.

Do you also have EntityRegistry.registerModEntity(...) somewhere?

RenderingRegistry.registerEntityRenderingHandler(Class<? extends Entity> entityClass, Render renderer)

Might want to take a peek at my project: https://github.com/Draco18s/Artifacts/tree/master/draco18s/artifacts/item https://github.com/Draco18s/Artifacts/tree/master/draco18s/artifacts/components It'll take a little parsing to find the exact parts you're looking for, but ComponentDamage handles increasing the player's attack value the same way vanilla swords do.

JDGUI by itself is usually sufficient. Most mods don't obfuscate themselves, so you're left with only the Minecraft obfuscated parameters, but most you can figure out just by the context, the rest you can lookup using MCP I actually peeked inside Twilight Forest at the Anti-Builder to see if it had done anything special/clever to minimize get, save, check, and reset blocks (as I needed similar functionality). It was just a standard 3 dimensional for loop. I've also poked my nose into Mystcraft on occasion (notably when trying to figure out how to use XCompWiz's API, I'll get confused over the usage of one parameter, so I pull up base and take a look at how he was using it).

!!! Do not create a new renderer, one is passed to you for all special renderers. Creating a new one will likely give you an "already tesselating" error.

You mean like renderer.renderBlockUsingTexture(Block.stone, x, y, z, textureIcon);

Yup, that too.

"/textures Make that "textures A / is automatically inserted for you between your mod ID and your texture path: Cyborg53373_Elementum:/textures/gui/cellingMachineGUI.png That : is converted to a / when it attempts to load files.

"Preloading" textures hasn't been necessary since 1.5.0 with the new texture system. Vanilla handles that for you.

Here's what I used: List l = worldObj.getEntitiesWithinAABB(EntityItem.class, AxisAlignedBB.getAABBPool().getAABB(xCoord-3, yCoord-3, zCoord-3, xCoord+3, yCoord+3, zCoord+3)); And it worked.

Except that if I attempt to register a texture using setTextureName("MyMod:someImage.png") and use the same casing when I build my folder structure it will fail. If I recall correctly, it works in Eclipse, but does not work when compiled and zipped. I don't have a convenient setup at the moment to produce a test case, but I've had the problem and when I tell people to always use lower case, it works.

Yes. ItemStack has a writeToNBT function. Just pass in a new NBTTagCompound and you'll get the "stored" version back out. Then just add that tag to another tag. All container objects do this to save their contents.

Do you or do you not know what "a static reference" and a "a non-static field" are?

You need to approach your problem from a different direction. onUpdate is called once every 1/20th of a second. If you need to wait 1 second you need to.... Let onUpdate get called 20 times.

X, Y, Z, BlockID, Delay (in ticks)

You haven't done any of the things suggested to you, your block class is still basically empty. You haven't set its name, texture, hardness, resistance, or anything.

...You are correct. It's iron golems that are in hostile. (And this emphasizes why the package differentiation is almost meaningless). I unfortunately don't have a solution for you. All my mob coding has been taking something that's close to what I want and modifying it.

(You don't need to override registerIcons, but it will work using the same details as my post) this.setTextureName("MODID" + ":" + "BLOCKNAME") Where MODID is whatever you want to name your assets folder and BLOCKNAME is whatever you want to name the texture file. These must be lower case (if they're not, they will be converted). Now go to /src/minecraft/assets and create a new folder there called MODID, inside that a folder called textures inside that a folder called blocks inside that add your texture file named BLOCKNAME.png Voila. http://www.minecraftforge.net/wiki/Icons_and_Textures

Look at what you do have access to and figure out if any of those objects have access to what you need, or can get it.

I think zombies use EntityMob, but yes. EntityAnimal doesn't have the attack function. Which is why wolves are in the hostile mobs package.