LexManos

The pickup event is specifically designed to be server side, the client really shouldn't be doing ANYTHING client side. So if you need to do something spectacular client side, then you eityher 1) are doing it wrong or 2) should probably hook into something else. As for having the extra data that you need, this is fairly simple, the item is picked up AFTER the event fired, the item passed in is the full and complete item stack, and the player passed in is the player that is grabbing the item. You can use those peices of information to do whatever the hell you want. As for the actual handeling, there is a flag to stop everything, as well as a flag that marks it so that the vanilla pickup {adding to the inventory} doesnt happen, yet your event can still process as it wished. So in reality... I don't think this event needs to change at all.

There is no exe in the source dist, you just follow the instructions and run install.sh

Im gunna say you didnt link with the decompiled source properly, as that field should exist just fine. But it wont if you link against the obfusicated classes.

There should be nothing that effects the keyboard inpput, just make sure you're passing it to the correct window/applet.

Ugh fuck it to tired to hold your hand, and obviously you are not willing to do your own research -.- https://github.com/Forkk/MultiMC/blob/master/MultiMC/Launcher/MultiMCLauncher.java Note lines 59-80. Done.

Im pretty sure that mcmod.info files won't become mandatory, so you're just gunna have to live with the fact that some mods don't have them. As for Forge shipping a file with the version.. I could of sworn I did, but looks like I didn't so we do now: https://github.com/MinecraftForge/MinecraftForge/commit/f10073dc457d48e6a6a4fb68b09d6680cdc3c8db As for detecting FML/MC versions, thats been in fmlversion.properties for a while.

1) that link is fucking old 2) read the license

Dont edit base classes in your launcher -.- Your edits are getting overwriten by forge cuz we have to edit that class. Take a look at how other launchers do it, its super simple.

You would have to edit all the classes related to generating and decorating the chunks. Which screws up compatibility with other mods. The simplest, and best solution, is to reserve the block ids < 256 to be soley for world gen.

The ore dictionary is for modders to use, not for users like yourself, go speak with the mod authors if you want them to use it not us.

World generation is limited to 256 for the base construction. It cant be changed beyond that without horribly breaking compatibility with other mods. However, the number of mods that do that deep of world gen is few and far between, so there shouldn't be an issue with your guys playing nice together.

As long as you set the directory that MC returns in Minecraft.getMCDir() properly {its simple you just set 1 field} then you're fine. If you don't then it'll autogenerate and go for it.

There is a difference between local smp And dedicated smp, but ya, this issue is caused by the mod having hard references to client side only classes. Theres nothing we can do with it. Go bitch at risu to stop being client side only.

This is caused by your not installing forge properly. start from scratch and make sure you stick only forge in your jar, using a good archive tool such as 7zip.

RTFL

You're calling a client side only function on the server.. stop it.

Considering that there are vanilla block that use that just fine and work just fine, im going to say that you've screwed up somewhere.

Please check your code before responding, 1) it's horrible code, 2) Thats not how those functions work, go read the ore dict javadocs, its' there. I've also written samples if you search.

MC's brewing system is not designed as a 'X+Y=Z' It is a series of bit twiddeling, which is actually fairly basic to understand once you know basic bit manipulation. Any re-write of the system to make it more 'user friendly' or 'understandable' would be something that isn't within our range to do in Forge. If you want to make and ship a completely different brewing system, go for it, but, its not in Forge. And dont bump 2 month old threads -.-

Forge isnt for bukkit. If you're not trying to put it on bukkit, post a log.

The first issue was that somehow one of your configs got corrupt, then well, you went and ballsed up everything else in your attempts to fix. So.. start from scratch.

No. I've explained why forge will not do this many times.

Dont make a recursive loop? Make sure you dont load a chunk while you're generating the chunk.. AE: Check your boundaries and only work in the same chunk.

There are hooks in Forge for it and have been for quite a while, go take a look at BlockFire.. fairly logical place to start..

No, if anyone finds out what it is, dont post else ban.