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

No options for certain mods #237

Open
Studly234 opened this issue Jan 7, 2020 · 1 comment
Open

No options for certain mods #237

Studly234 opened this issue Jan 7, 2020 · 1 comment

Comments

@Studly234
Copy link

Issue: Certain mods are not being detected by customoregen. For me, the mods of interest are nuclearcraft and mekanism.

Solution: I was able to get them detected by changing the config file line:
<IfModInstalled name="Mekanism"> to
<IfModInstalled name="mekanism">
This solution also worked for nuclearcraft. I'm not sure if there are any other mod config files with this issue.

@konvaa
Copy link

konvaa commented Apr 18, 2022

How did you exactly edited the config files? If I follow instructions, the default is always replaced. If I place mekanism.xml with corrected case sensitive name into custom folder, I need to get thei nfo also to CustomOreGen_Config_Default file. Unfortunately this one is also being replaced. If I make copy of that file and rename it (removing the _default), no valid settings appears. I mean completely blank window.

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

No branches or pull requests

2 participants