Don't log error when a mod folder isn't found - #600
Merged
KANAjetzt merged 1 commit intoJul 22, 2026
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Per default, the mod loader throws errors when the mods-unpacked folder or the Steam workshop folder isn't found.
However, on a clean install of a game without any mods installed, this is the expected setup.
Only once you download something from the Steam workshop or load a mod from some other source do these folders exist.
Now instead of reporting this configuration as an ERROR, its only an INFO resulting in a clean startup.
Before:
After: