MCL-22692Unable to play on Forge
After last launcher update Minecraft Forge has several problems with loading mods (crashes / missing data / mods ... ), checked if it's really launcher problem twice on different minecraft versions (1.7.10, 1.12) / modpacks (GregTech New Horizons, Nomifactory) hosted on CurseForge.
Environment
Windows 10, intel 64bit
Linked Issues
Created Issue:
Unable to play on Forge
After last launcher update Minecraft Forge has several problems with loading mods (crashes / missing data / mods ... ), checked if it's really launcher problem twice on different minecraft versions (1.7.10, 1.12) / modpacks (GregTech New Horizons, Nomifactory) hosted on CurseForge.
Environment
Windows 10, intel 64bit
![[Mod] markderickson](../../../data/avatars/users/18946.svg){kind=small}
duplicates
Minecraft Launcher version 2.3.481 introduces a severe regression that is causing Minecraft clients to treat the launcher's workDir as the Java default filesystem path (java.nio.file.FileSystem).
While this issue appears to not significantly affect vanilla unmodified Minecraft clients, it results in a severe adverse effect on all Minecraft mod loaders (Quilt, Fabric, Forge) that are configured in the launcher to use a custom game directory, which is a configuration that is used by a significant portion of Minecraft's playerbase.
Many Minecraft mods use java.nio.file.Paths.get() to derive the current Minecraft instance's profile directory in order to store data such as configuration files or other cached data, which is important to keep separate between instances that may belong to wildly different versions of Minecraft. This also causes the Launcher workDir to become unnecessarily polluted.
Please note that this is not to say that vanilla unmodified Minecraft clients are completely unaffected — this issue is also causing all client logs even for vanilla unmodified clients to be written to the incorrect directory.
This behaviour can be tested by observing the value returned by java.nio.file.Paths.get("config/").toAbsolutePath().
On a Minecraft client launched from Minecraft Launcher 2.3.462 (the last working version, still usable via the --skipUpdate argument), this returns the correct configured game profile directory — for example, ${HOME}/Library/Application Support/minecraft/1.19.2/config on macOS.
On a Minecraft client launched from Minecraft Launcher 2.3.481, this returns an incorrect value of ${HOME}/Library/Application Support/minecraft/config, which is incorrectly treating the launcher's workDir value as the game profile directory.
The root cause of this can be traced down to the default JRE filesystem path being returned from java.nio.file.FileSystem.getDefault() being incorrect on clients launched from Launcher 2.3.481.
※ EDIT: This issue is also most likely the root cause of MCL-22670 and MCL-22692.
※ EDIT 2: Other related issues: MC-257316 (incorrect project).
Does
MCL-22670describe your issue?This issue is most likely being caused by
MCL-22685.The "missing data" symptom you're describing seems to line up, as the bug causes mod data to be read from and written to the wrong location.
Thank you for your report!
We're tracking this issue in
MCL-22670, so this ticket is being resolved and linked as a duplicate.If you would like to add a vote and any extra information to the main ticket it would be appreciated.
If you haven't already, you might like to make use of the search feature to see if the issue has already been mentioned.
Quick Links:
📓 Bug Tracker Guidelines – 💬 Community Support – 📧 Mojang Support
📓 Project Summary – ✍️ Feedback and Suggestions – 📖 Game Wiki
– I am a bot. This action was performed automatically! The ticket was resolved by one of our moderators, and I left this message to give more information to you.