Torezu

Your OP said that was something you'd tried already, so I didn't ask. Yes, I would do that, if you haven't.

Your launcher still says you have 6u31, so you probably have multiple versions of Java installed. Get rid of all but the most recent (7u5, in this case). Then drop your RAM allocation on the launcher to 512MB-1GB. You're trying to allocate too much, and Java is whining about it.

I think I speak for everyone when I say, "What do you mean by 'Extra Launch Options?'"

Stick a klein star with some charge on it in your inventory. This isn't really a bug. It's you not knowing how EE works.

Errr, he just told you?

Your Java version needs to be 7 on the server.

What is this "tekkie" of which you speak?

It does look like an RM axe in a deployer. Do you have a tree farm somewhere?

Odd, because those chunk relocations are a sign of world file corruption. If your server hasn't crashed, I don't know what to tell you from here.

Recommended build changed to 3.1.2, so if you were using that, it probably updated. Give us your own bug report, if your situation is different.

Do you have rain turned off in OptiFine? You won't be able to see it.

Your server either doesn't have enough RAM dedicated to it, or more likely its upload or (unlikely) download speed is not high enough to handle the information transfer.

This is usually caused by an exceptionally poor connection to the server, on whichever end, or server-side item lag. However: 1) Are you sure you're using 64-bit Java to match your OS. You don't say. 2) Do you have more than 1 copy of Java? Check your Control Panel. 3) Is there anything in or near that chunk that could cause high lag, like item drops in bulk, etc.?

Then you need to be more detailed with your bug report.

Just remove the Talisman of Repair from the pedestal. Really. You'd have to decompile and edit EE, then you might have to distribute the changes to anyone that wanted to join your server, and...it's not worth it.

Careful with this. Auto-installing on a 64-bit system will often grab 32-bit Java anyway. You want to manually select Java versions if you know which one you want.

Assuming your inventory is corrupted, deleting your player.dat will probably solve the problem. You'll just have to NEI all your stuff back in, though the contents of any bags you were carrying should be fine. I'd just use a klein start in the future.

You have a Talisman of Repair on a Dark Matter Pedestal somewhere. They don't work anyway, so you might as well take it off. That'll stop the console-spam.

Install OptiFine Standard over your current one (into modpack.jar), and see what happens.

Single-player maps store the player's data, inventory mostly, in the world.dat file. SMP maps store all that stuff in the individual [playerName].dat files. That makes the conversions from SMP to SSP Tekkit and back a bit of a challenge. I honestly don't even know how easy it would be to do.

Launcher log! Go!

Post the whole launcher log, and stop bumping. It's annoying us. Use code tags or pastebin to avoid a threadstrosity.

Please use the search bar.

Two things: 1) That's your server log, not your launcher log, which would be much more helpful for diagnosing a launcher problem. 2) Max memory is always going to be 1.5GB unless you manage to get a 64-bit OS and Java to match.

This is not a bug. This is intentional. Figure out which plugin offers protections for the area the quarry is trying to dig, or part of it, and figure out how to allow the [buildCraft] fake player to bypass those. If you can't do that or don't want to try and don't mind the possibility of quarries being used to grief, type "/OP [buildcraft]" (without the quotes) into the in-game chat window, or the same thing without the / into the server console.