taladar

Actually it is Windows that does something special here by making two different binary values equivalent in the sorting order. That isn't the point though. The point is that the launcher could fix this easily by renaming everything in the mods directory to lowercase and reduce all those "Saving chunks" bugs caused by a loading order different from that of the technic devs.

I have been using the Technic Launcher for a while now on Linux and had the occasional issue caused by mod loading order. After trying to get the dev version of the Technic Pack running today that had been out for a month and running into numerous issues like that again I thought that the developers couldn't release a version this buggy so I thought about the issue from a different angle. Mods seem to be loaded in alphabetical order of filenames in the mods directory (thus tips here and elsewhere to rename mods with certain letters at the start of the name to change the order). On a case-sensitive filesystem all files with capital letters are usually listed first (lower ASCII codes) before lower case is listed. So the order of mod loading is A...Z a...z instead of A a B b ... Z z. Trying this theory I simply renamed all files in mods to their lowercase equivalent and suddently all my problems disappeared, Minecraft launched and I could create a new world and walk around, open my inventory,... all stuff that had caused crashes with various exceptions in the logs before. So I would strongly suggest that the launcher does not depend on the case of the filenames when loading mods or, if that code is beyond your reach to change in Minecraft itself or the JVM that the files are all renamed to lower case (or all upper case but all lower is easier on the eyes). That way mod loading order should be identical on all supported platforms.