Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Fix ModEXT.txt issues #49

Merged
merged 2 commits into from
Jun 5, 2016
Merged

Fix ModEXT.txt issues #49

merged 2 commits into from
Jun 5, 2016

Conversation

yamgent
Copy link

@yamgent yamgent commented May 5, 2016

Creating a ModExt.txt symlink to ModEXT.txt is a bad idea for filesystems that does not support files having the same name with different casing. symlink is also not compatible with Windows anyway.

Instead the root of the problem is fixed by modifying the code to load the correct file.

yamgent added 2 commits May 5, 2016 13:38
Does not work on Mac and Windows, and git unable to deal with
file thrashing with another file of similar name.
Some file systems are case-sensitive, so use proper casing.
@DanielGibson
Copy link

I think this makes sense. 👍

@yamgent
Copy link
Author

yamgent commented Jun 5, 2016

Anything wrong with the PR?

@icculus
Copy link
Owner

icculus commented Jun 5, 2016

Anything wrong with the PR?

Nope, sorry for the delay!

--ryan.

@icculus icculus merged commit d723153 into icculus:master Jun 5, 2016
@yamgent yamgent deleted the mod-ext-fix branch June 5, 2016 06:26
@DanielGibson
Copy link

hmm I just noticed that in my serious sam installation, the file actually seems to be called ModExt.txt, not ModEXT.txt.
We should find a way to support both (unfortunately, LoadStringVar() doesn't return if it was successful)

@DanielGibson
Copy link

ok, supporting both wasn't that hard after all, added a fix to #56

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants