I believe we can set up custom loggers in WebSocketSharp's WebSocket object. We should have it log somewhere other than stderr or wherever it currently goes since in Unity games that almost always ends up in the Unity player logs which is disparate from where other errors typically go (such as stdout, modloader logs, etc.).
We can possibly provide options to allow callers to provide their own loggers and then provide another NuGet package with logger implementations for things like BepInEx or Hollow Knight's ModdingApi, as examples.
I believe we can set up custom loggers in WebSocketSharp's
WebSocketobject. We should have it log somewhere other than stderr or wherever it currently goes since in Unity games that almost always ends up in the Unity player logs which is disparate from where other errors typically go (such as stdout, modloader logs, etc.).We can possibly provide options to allow callers to provide their own loggers and then provide another NuGet package with logger implementations for things like
BepInExor Hollow Knight'sModdingApi, as examples.