Startup crash from having the mods folder as a symlink destination
mosharky opened this issue ยท 3 comments
Describe the bug
A startup crash occurs due to "Missing or unsupported mandatory dependencies", where Connector Extras isn't detecting Connector.
Steps to reproduce
- Create a mods folder as a symbolic link, such that your launchers instance has the destination of the link
- Add Sinytra Connector, Connector Extras, and Forgified Fabric API
- Launch the instance
- Startup crash will occur with error: "Missing or unsupported mandatory dependencies: Mod ID: 'connectormod', Requested by: 'connectorextras_architectury_bridge', Expected range: '[1.0.0-beta.18,)', Actual version: '[MISSING]'"
Logs
Additional context
- Seems like Connector Extras isn't detecting Connector properly
- This was tested on Prism Launcher and CurseForge
- Only Connector Extras and its dependencies were used in the test
- The crash doesn't occur if my instance's mods folder is the source of a symlink
If you're wondering why I'd want to have a symlink, its because Prism can't export in the curse modpack format, and that adding/updating mods is a hassle with Prism, so I'm using CurseForge to manage the mods.
Does this work with mods other than Connector? The error comes from FML'd dependency resolver, and Connector Extras doesn't come with any custom logic for locating dependencies.
Yup, I tested it with Moonlight Lib + Supplementaries. No crash or dependency issues.
