Equivalent Exchange 3

Equivalent Exchange 3

2M Downloads

Linux folder paths - case sensitive

jaeggr opened this issue ยท 4 comments

commented

I first noticed while connecting to a Tekkit server actually, but somewhere in the EE3 mod extraction, some config files are put in the "ee3" folder, and some are put in the "EE3" folder. This causes a mismatched ID error, as well as a missing ID error. I fixed both manually by opening each block config file and making sure they were the same, with the newest ID numbers, but so far a fresh install is broken on a Linux machine because of the case sensitive folder paths. Deleting one folder or the other doesn't work, so now in order to run the mod with my client, it needs two folders with identical contents.
screenshot from 2014-02-07 02 29 46

commented

This shouldn't happen. In the code all of the configuration files are only referenced by their lower case names. Sadly, I don't have a Linux machine to test this.

commented

Delete your ee3 config folders. They will regen with correct paths (your EE3/ folder is an old historical one from before I forced the paths to lower case)

commented

Ok, EE3 wasn't recreated with pre2a.56, but I'm getting the same exact error because in the ee3 folder the block.properties file looks like this:

block {
I:alchemicalChest=2454
I:alchemicalFuel=2455
I:alchemySquare=2457
I:aludel=2452
I:calcinator=2451
I:chalk=2456
I:glassBell=2453
I:infusedCloth=2460
I:infusedPlanks=2462
I:infusedWood=2461
I:researchStation=2458
}

Instead of what was in the EE3 folder below:

block {
I:alchemicalChest=2455
I:alchemicalFuel=3399
I:alchemySquare=2457
I:aludel=2454
I:calcinator=2451
I:chalk=2456
I:glassBell=3400
I:infusedCloth=2460
I:infusedPlanks=2462
I:infusedWood=2461
I:researchStation=2458
}

It might be possible that the server owner needs to delete the same file and reinstall it, but I'm not able to check that at the moment. But to be clear, the second block of text is working for me, and the first is generating the above error.

commented

You are getting the error because yes, your ids are mismatched with the server ones. That's a trivial thing to troubleshoot so I am closing this ticket because it is not a bug with EE3.