Closed xzores closed 3 months ago
I had same error the other day, fixed it for now by creating an empty ols.json file at the location. ols must have trouble detecting if the file exists.
Oh and ofc it's now missing again after an update, not ideal :p
@Hyrtwol Whether the global file exists or not, should not have any affect on anything, except that it won't use it then. I could stop writing out the error, but it's better to show where it tried to look.
Are you saying something doesn't work if the global file doesn't exist? I would expect more people to have complained about it. Must people don't even know about the global config.
This is related to https://github.com/DanielGavin/ols/issues/316
Fixed in #316
sry for the late reply, the missing global ols.json don't cause any issues. maybe nice if it could be a warning instead
@Hyrtwol Yeah most likely should be. Technically all of the ols.json missing are technically not errors.
After the new update I get a new error: