GotoLink

GameRegistry.registerPickupHandler(new PickupHandler()); Once is enough. The rest sounds good.

You can have damage and NBT. See vanilla enchanted/named tools.

Make the change as soon as the packet is received. You can't know if an outside code can be executed before the next packet arrives. Ho and do some checks, like the packet channel.

I don't know if you still have this in your Packet handler, but just in case: private static String identificationName; @Override public void onPacketData(INetworkManager manager, Packet250CustomPayload packet, Player player) { ByteArrayDataInput reader = ByteStreams.newDataInput(packet.data); identificationName = reader.readUTF(); } Don't store a (static : value, actually do something to the tile entity.

You added the player's inventory slots first to your container, so they get the first slots.

I don't know anything about Bukkit, but I'll give my opinion (on your ideas ) Option 1: Reflection. If Bukkit are good and give an appropriate answer to their registering methods, this could be as simple as any code, except you catch more exceptions. Option 2: Brings the syncing issue. I don't know how Forge+Bukkit would load mod+plugin (order, dependency ?), might be messy. About the syncing, I'll say that Forge should keep priority. Isn't the purpose of the Bukkit part for compatibility only ?

You are using two different variables. They don't know about each other unless read/write NBT happens, which doesn't that often. The one "name" variable was good.

You are calling a client only class in a common file. Instant server crash.

No, you shouldn't.

...and what do you get in the reobf folder ?

EntityFX particle = new EntitySpellFXDamage(w, player.posX, player.posY, player.posZ,a,-b,c); FMLClientHandler.instance().getClient().effectRenderer.addEffect(particle); Where did you put this ?

setTickRandomly(true); @Override public void updateTick(World world, args) { if(!world.isRemote) world.spawnEntityInWorld(new EntityItem(...)); }

It makes sense with what addSlotToContainer(Slot) does. Man, extend TileEntityFurnace, use GuiFurnace and ContainerFurnace, and you'll be done with it. Seriously.

Don't assume any logic behind it, benchmarking on Minecraft terrain generation is useless. Mew probably felt like it had an impact, while any other change could have done that. Obviously you need to iterate over the blocks, it would be utterly stupid not to. I prefer to use Iterator by the way

That the receiving hand of the event system. Don't forget to post the event when it should be sent. Event myEvent = new CustomEvent(args); MinecraftForge.EVENT_BUS.post(myEvent); //if(myEvent.isCanceled) ...

@Override public boolean handleRenderType(ItemStack item, ItemRenderType type) { // TODO Auto-generated method stub return true; } @Override public boolean shouldUseRenderHelper(ItemRenderType type, ItemStack item, ItemRendererHelper helper) { // TODO Auto-generated method stub return true; } Try return false ? Did you ClientRegistry.bindTileEntitySpecialRenderer(args); ?

Changing the player dat file would only affect it if you do it before the player logs in. If you do it after, your saved data will be overwritten on player log out and won't come into effect at all. Make an external program for the client to run before he starts his game. Why do you want to change that data ?

RenderGameOverlayEvent.

Man, if you don't understand how to use the code... learn Java, seriously.

Packets. Send the needed info to client side.

EntityAIHurtByTarget ?

Man, if you want to keep it simple and don't care about modifiers, AttributeInstance oldSpeed = player.func_110148_a(SharedMonsterAttributes.field_111263_d); oldSpeed.func_111128_a(oldSpeed.func_111125_b()*change); that is all.

Not only is it good practice, but more efficient and doesn't breach Minecraft license. Check your transferStackInSlot method in Container, i see some magic numbers that could be wrong. Also make sure you use mergeItemStack(ItemStack, int, int , boolean) correctly. Be aware that you added your slots first, then the player internal inventory, then the player inventory bar. The order is important.

I'd rather think it is downloaded automatically.

@Mazetar If you have organized the generation in chunks, it is a good idea, indeed. Don't expect much improvement though.