Tekkit 1.6.4 EE3 ID mismatches - out of the box

[Simba]

I've attempted to try today's recommended Tekkit 1.6.4 build.  The Technic Launcher asked me if I'd like to update, and I went ahead and extracted a brand new Tekkit_Server_v1.2.6.zip on my server.  No existing world and a fresh, mostly unaltered server.properties.  Both the client and the server are running in a Debian Linux environment with java jre1.7.0_51.

 

When I try to connect, I get:

 

Forge Mod Loader has found ID mismatches

Complete details are in the log file

 

ID 3400 from Mod EE3 Is missing

ID 3399 from Mod EE3 is missing

ID 2454 is mismatched between world and game

ID 2455 is mismatched between world and game

 

 

 

This is in ForgeModLoader-client-1.log:

 

2014-02-20 00:41:09 [FINE] [fml.ItemTracker] The difference set is not equal: only on left={3400=Item 3400, Type com.pahimar.ee3.block.BlockGlassBell, owned by EE3, ordinal 0, name block.glassBell, claimedModId null, 3399=Item 3399, Type com.pahimar.ee3.item.ItemBlockAlchemicalFuel, owned by EE3, ordinal 0, name block.alchemicalFuel, claimedModId null}: only on right={2452=Item 2452, Type com.pahimar.ee3.block.BlockAludelBase, owned by EE3, ordinal 0, name block.aludel, claimedModId null, 2453=Item 2453, Type com.pahimar.ee3.block.BlockGlassBell, owned by EE3, ordinal 0, name block.glassBell, claimedModId null}: value differences={2454=(Item 2454, Type com.pahimar.ee3.block.BlockAludelBase, owned by EE3, ordinal 0, name block.aludel, claimedModId null, Item 2454, Type com.pahimar.ee3.item.ItemBlockAlchemicalChest, owned by EE3, ordinal 0, name block.alchemicalChest, claimedModId null), 2455=(Item 2455, Type com.pahimar.ee3.item.ItemBlockAlchemicalChest, owned by EE3, ordinal 0, name block.alchemicalChest, claimedModId null, Item 2455, Type com.pahimar.ee3.item.ItemBlockAlchemicalFuel, owned by EE3, ordinal 0, name block.alchemicalFuel, claimedModId null)}

2014-02-20 00:41:09 [sEVERE] [fml.ItemTracker] FML has detected item discrepancies

2014-02-20 00:41:09 [sEVERE] [fml.ItemTracker] Missing items : {3400=Item 3400, Type com.pahimar.ee3.block.BlockGlassBell, owned by EE3, ordinal 0, name block.glassBell, claimedModId null, 3399=Item 3399, Type com.pahimar.ee3.item.ItemBlockAlchemicalFuel, owned by EE3, ordinal 0, name block.alchemicalFuel, claimedModId null}

2014-02-20 00:41:09 [sEVERE] [fml.ItemTracker] Mismatched items : {2454=(Item 2454, Type com.pahimar.ee3.block.BlockAludelBase, owned by EE3, ordinal 0, name block.aludel, claimedModId null, Item 2454, Type com.pahimar.ee3.item.ItemBlockAlchemicalChest, owned by EE3, ordinal 0, name block.alchemicalChest, claimedModId null), 2455=(Item 2455, Type com.pahimar.ee3.item.ItemBlockAlchemicalChest, owned by EE3, ordinal 0, name block.alchemicalChest, claimedModId null, Item 2455, Type com.pahimar.ee3.item.ItemBlockAlchemicalFuel, owned by EE3, ordinal 0, name block.alchemicalFuel, claimedModId null)}

 

 

The previous recommended version of Tekkit worked just fine, "out of the box".

 

I'm not very familiar with the inner workings of Minecraft, mods and item id numbers and whatnot, so what is the best course for troubleshooting/resolving this issue?

 

[Grotnicki]

I've found out that client version create 2 config directories for EE on my Fedora 20 (linux) machine, my friend on Windows 7 machine has no problems with logging into server. After copying files from client EE3 to ee3 and overwriting files it worked.

[Simba]

Tekkit 1.2.6b seemed to fix this but now that 1.2.7 is out, it's doing exactly the same thing.  Adding a lower-case ee3 symlink or copy of the EE3 config directory doesn't seem to have any affect.

[Skuli]

Tekkit 1.2.6b seemed to fix this but now that 1.2.7 is out, it's doing exactly the same thing.  Adding a lower-case ee3 symlink or copy of the EE3 config directory doesn't seem to have any affect.

 

Somehow the client config folder was capitalized, again.

 

I'll try to track down where in the process this is happening, but on the client-side, rename EE3 to ee3 and see if that fixes your problem.

 

I'll push out a 1.2.7b this morning to rename the client-side EE3 config automatically.