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

NomiLabs configuration not loading correctly #200

Closed
5 tasks done
lynxx131 opened this issue Sep 5, 2024 · 2 comments
Closed
5 tasks done

NomiLabs configuration not loading correctly #200

lynxx131 opened this issue Sep 5, 2024 · 2 comments

Comments

@lynxx131
Copy link

lynxx131 commented Sep 5, 2024

Your CleanroomMC Discord Username

No response

Cleanroom Version

universal-0.2.3-alpha+build.5.run.696

Java Version

Java 21

Graphics Card Vendor

NVidia

Bug Report

For some reason the NomiLabs mod included with Nomifactory CEu does not load it's config correctly under Cleanroom, the pack ships a config file called nomilabs.cfg but when launching under Cleanroom this file is ignored and a new file called nomilabs is created in the config directly with what appears to be all default values.

This issue does not occur under vanilla Forge.

Mod List

All mods included in Nomifactory 1.7a Curseforge pack + Fugue 0.16.3 and Scalar 2.11.

MMC Instance Notes

This instance is built using Github Action.

Using installer artifact from commit: b132d86
Action URL: https://github.com/CleanroomMC/Cleanroom/actions/runs/10658856743

Final Checklist

  • I have searched the issues and haven't found a similar issue.
  • I have read the known incompatibilities and this is not related to one of those.
  • I have installed Fugue and it does not fix this issue.
  • I am using experimental branch and have installed Scalar and it does not fix this issue.
  • I am running a test build from Cleanroom Github Actions. (Or, if I've compiled it myself I plan to fix the issue)
@kappa-maintainer
Copy link
Collaborator

Try run.698 (when the build is out)

@lynxx131
Copy link
Author

Upgraded to build 699 and this issue appears to have gone away and the config directory looks correct.

Thanks

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