Whats wrong with getting the location as a "start in" directory? That way you could run the exact same executable with two completely different looks (for two worlds, presumably), if you created two ini files and changed your shortcut accordingly.
And if you have a bad ini file (or a non existant one at the path listed) check the other common places for a good one, and if still not, have it default to the default MC values.
If we just used the MC path (or world path, or whatever) we wouldn't be able to customize MC itself for different worlds in the global preferences sense. While there isnt a whole lot there, this would allow complete control (things like sandbox, or connecting preferences, or tabs, or whatever). As well as allowing multiple users to have their own setups completely independant of one another.
I have never had a problem with a shortcut telling a program to start in the wrong directory. If the shortcut is configured improperly, thats another story, but its not a bug. It'd be like trying to call a script function with the wrong set of arguments, the script will yell at you. In this case, we just use default values (maybe we also want to have a message popup saying 'No configuration files were found at any of the locations specified, if this is unintended, then you might try [this] or [that].' |