引用自 disarmer：

Mod trying to write log at any raid, but with wrong path separators: https://gist.github.com/disarmer/bc5decb491159d4882966cb0d8bb8649

On linux, valid path separator is slash(/), not backslash(\). Mod trying write "/home/user\Mods\PES.log", unable to do it and raid fails.
Anyway, home dir isn't valid place for log. It would be nice to be able disable log completely

I replaced the separator by system-dependent one.

The location I use is the following:
static readonly string logFile = Path.Combine(@Environment.CurrentDirectory, "Mods", "PES.log");

So, the "@Environment.CurrentDirectory" is evaluated as "/home/user" for linux users? hmm...

Do I understand you correctly, that even with disabled "debug" option in the settings your get this error?

Seems is was fixed, thanks.

> So, the "@Environment.CurrentDirectory" is evaluated as "/home/user" for linux users?

yes, one can run app from any directory, /home/user is default working directory

> that even with disabled "debug" option in the settings your get this error?

yes. It still writing regardless this option

>yes. It still writing regardless this option
This is bad...

It is a legacy tbh. I would change the whole debugging (and I already changed a lot)...
Ah.

引用自 disarmer：

Seems is was fixed, thanks.

> So, the "@Environment.CurrentDirectory" is evaluated as "/home/user" for linux users?

yes, one can run app from any directory, /home/user is default working directory

> that even with disabled "debug" option in the settings your get this error?

yes. It still writing regardless this option

Okay, let me re-phrase it completely.

What you like to have? - I decided (complete change from original mod) to have very precise full log if this option is enabled.

What about allow to select the location? I have no idea how .net framework will behave in virtual environment (on linux especially), however :) Want to test? =)