Jump to content
  • 0

Tekkit server error (Clevercraft, not IC2Advanced Machines)


Question

Posted

Launcher/pack Version: Technic Launcher 0.5.4.4

Operating System: Windows 7 64bit

Version of Java: 1.7.0_03

Description of Problem: Tekkit server fails to launch after updating from 2.0 to 2.1.1, the following errors show up which were not fixed by any of the help found in the IC2 Advanced machines thread. I have the latest version of java 7, I have removed java6 from running, I have set a JRE classpath in system options and still the server pops these errors up, any help you can provide would be appreciated.

Error Messages: http://pastebin.com/QRngPZkr

Link to pastebin of log: http://pastebin.com/QRngPZkr

5 answers to this question

Recommended Posts

  • 0
Posted

Well, that's a new one. Can't say I've ever seen a crash caused by a mod trying to add the only block in it to the same slot twice.

Go to config/ModLoader.cfg and look for the line "mod_Clevercraft=on". Change on to off. See if that fixes the crash.

  • 0
Posted

Yeah I just tried to do this on advice from a fellow tekkit player, but that made an error with forestry instead, going out on a limb I guess if I turned forestry off, something else would crash - thanks for the quick reply though, really keen on getting back to building awesome machines

  • 0
Posted

Is it possible that you upgraded to 2.11 and have duplicates of each mod in your mods folder?

If that is indeed the case, you just need to delete the older version of each mod.

  • 0
Posted

Is it possible that you upgraded to 2.11 and have duplicates of each mod in your mods folder?

If that is indeed the case, you just need to delete the older version of each mod.

When extracting the new server's zip/rar I set it to overwrite everything, but after checking what you suggested my problem was fixed - thanks alot. I hadn't previously used this mod so for 3 days I pretty much let everything run on default, next time there is a patch I will check the mod folder.

  • 0
Posted

Overwriting didn't work because the file names were changed. This was the major point of the tiny update to fix linux installs. I imagine this won't be an issue again.

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
×
×
  • Create New...