LexManos

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.

I highly doubt that MC will get into a state that would make 100% automatic ID management to be feasible. However, specifically when it comes to mods grabbing ids on first install, Forge already has the tools to make everything that uses forge to work together IF the modder decides to use it. The 'auto id picker' from RP is actually just the getBlock function in Forge Config. So, ID Resolver style hack and smash, probably not gunna happen without Vanilla MC introducing some things that need to be done. But if modders take 10 seconds to call a function they can get a free ID without issue. So if you have conflicts, go yell at the modders.

Wow copy paste up the wazoo, please go learn some java code structure. But ya.. Enchanting stuff or doing whatever you want is possible now.

kinda need the full log, but it looks like you have a issue with your setup that causes the decompiled code to not recompile. Typically it actually shows the error.

Dont edit base classes...

Something in your code has a hard reference to client side only classes, fix it. From the looks of it it looks like your main mod class has the hard reference.

Make sure you are using the version of forge that the mystcraft tells you you should. Its a installation issue, follow the directions better.

Download this: http://files.minecraftforge.net/fmllibs/fml_libs.zip and extract to /lib in your .minecraft folder.

Caused by: java.lang.IllegalArgumentException: Slot 208 is already occupied by dan200.computer.shared.BlockPeripheral@3d0cd13f when adding forestry.core.gadgets.BlockMill@147d9e69 read your damn logs -.- this has nothing to do with forge -.-

Look at the code, its straight forward.... Its the fuzz in placement, when a player spawns...

What launcher are you using? Use the standard launcher or a compatible launcher.

Caused by: java.lang.ClassNotFoundException: net.minecraft.client.Minecraft at cpw.mods.fml.relauncher.RelaunchClassLoader.findClass(RelaunchClassLoader.java:125) Mod issue not ours, he references a client only class. Go complain to him

1) Dont use colors and shit like that its really annoying 2) Why the hell are you using a version of forge that is 100 builds out of date? 3) ModLoader mods work just fine with Forge 4) Straight forward issue, you have issues in the elemental creepers mod which I know works with forge just fine.

-.- How many times can you screw up installing forge and mystcraft? Follow the damn instructions this is getting annoying. Aside from that your 'before' world has no region data, meaning, it has no world. Which is why it generates a new one...