Toldea

Could not find Server jar, decompile requires both client and server. Forge requires both a fresh .minecraft instance AND the server.jar, download the server.jar from the minecraft website and put it in the jars folder.

This: public static final Block oreCopper = new oreCopper(oreCopperBlockID, 0); Is called before this: oreCopperBlockID = config.getOrCreateBlockIdProperty("Block Id for Copper", 200).getInt(); So your oreCopperBlockID just has garbage data in it, which will indeed probably mess up minecraft in one way or another. With a config file you have to initiate your blocks and items after you load the config file, so for instance in your init/preinit method, e.g.: public static Block oreCopper; @Init public void load(FMLInitializationEvent event) { Configuration config = new Configuration(event.getSuggestedConfigurationFile()); config.load(); oreCopper = new oreCopper(config.getOrCreateBlockIdProperty("Block Id for Copper", 200).getInt(), 0); config.save(); }

The simple answer would be there is a reason both vanilla minecraft and mods don't already do this. Consider the following: you install Redpower. "Ohai base let me completely destroy you and generate a volcano in your location ". Just generating ores might not have such a direct effect, but could still do some unexpected things. For instance triggering huge sand collapses or again stuff like redpower's marble generation will change your world quite a bit. You are still free to try of course, just note that it might end up destroying your world a bit.

Try running updatemcp before installing forge.

Here are a few general tutorials specifically for 1.3.2 -> http://wuppy29.blogspot.nl/2012/08/forge-modding-132.html However a lot of things aren't extremely different from 1.2.5, so if you can't find an updated tutorial just use an old one and take a look at the 'upgrading to 1.3.1' tutorial on the forge wiki.

Build 200 is really old, try installing the latest build.

Sure go ahead and place it anywhere you like. The config system is nothing more than a File and a Configuration object, place them anywhere you like. Note though that it is in no way needed though to keep a separate variable for each block/item id. In fact I personally find it very redundant to do so. I personally like to just call config.getOrCreateBlockIdProperty directly when initialising the blocks. I also dislike personally setting the id for each entry. I just have one nextBlockID variable which I give a starting value and then just increment with each block call. But again the only thing you have to do is initialize the File and Configuration objects, then create your objects and finally not forget to save the config to disc. How and where you do this is all up to personal preference

Strange. What build of Forge are you using? I'm on FML 3.0.98.304 / Forge 4.0.0.217 and calling this works perfectly fine: FMLClientHandler.instance().displayGuiScreen(entityPlayer, new FireCraftGuiClassChange());

No offense to the author, but I wouldn't take a tutorial on writing a property file written by someone who can't write 'property' correct too serious . Take a look at the advanced config tutorial on the wiki (http://www.minecraftforge.net/wiki/How_to_make_an_advanced_configuration_file). While it is 'technically' out of date, it still works fine for 1.3.2.

What are you exactly trying to accomplish that doesn't work for you? Calling displayGuiScreen does nothing more than just display a gui screen. What this gui screen then displays is up to its own implementation. Are you having problems displaying a gui screen? Cause calling displayGuiScreen should work fine. Any logic past that has nothing to do with displaying the gui screen and should be handled in the actual implementation of the gui. So for a custom inventory screen I'd imagine you'd just want to call displayGuiScreen, but your GuiMLBPegasus() constructor probably should contain an argument for the inventory object, so it can access it and display its contents.

If you want to give an item to the player, you can do something like this: FMLClientHandler.instance().getClient().thePlayer.inventory.addItemStackToInventory(new ItemStack(Item.coal, 1)); This would give the player 1 coal. Change Item.coal to whatever item you want to give and '1' to the amount you want to give.

For getting the currently equipped item, use: FMLClientHandler.instance().getClient().thePlayer.getCurrentEquippedItem();