We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
If you diff the old and the new (0.9.4) BepInEx.cfg:
BepInEx.cfg
[Logging.Console] < Enabled = false 11c10 < ForceBepInExTTYDriver = false --- > ForceBepInExTTYDriver = true 28c27 < WriteUnityLog = false --- > WriteUnityLog = true
Resulting in every log message to be logged twice:
[Info : Unity Log] 03/10/2021 21:30:58: Sending disconnect msg 03/10/2021 21:30:58: Sending disconnect msg [Info : Unity Log] 03/10/2021 21:30:58: Disposing socket 03/10/2021 21:30:58: Disposing socket [Info : Unity Log] 03/10/2021 21:30:58: Stopping listening socket 03/10/2021 21:30:58: Stopping listening socket [Info : Unity Log] 03/10/2021 21:30:58: Last socket, unregistering callback 03/10/2021 21:30:58: Last socket, unregistering callback [Info : Unity Log] 03/10/2021 21:30:58: ZSteamSocket UnregisterGlobalCallbacks, existing sockets:0 03/10/2021 21:30:58: ZSteamSocket UnregisterGlobalCallbacks, existing sockets:0
The text was updated successfully, but these errors were encountered:
We are not responsible for issues related to BepInEx.
Please report them in their GitHub repository.
https://github.com/BepInEx/BepInEx
Sorry, something went wrong.
set WriteUnityLog = false in BepInEx.cfg fixed the duplicated messages for me
WriteUnityLog = false
No branches or pull requests
If you diff the old and the new (0.9.4)
BepInEx.cfg
:Resulting in every log message to be logged twice:
The text was updated successfully, but these errors were encountered: