DiscordLogSync

1.0.4

• Updated BepInEx dependency to 5.4.2333

1.0.3

• Windows compatibility for RawStdout source — the fd-level pipe intercept now works on Windows via P/Invoke into ucrtbase.dll (_dup, _dup2, _pipe, _read, _write, _close). This works because ucrtbase.dll is the Universal CRT shared across Unity's native engine and all managed code in the process.

  Silent failure mode: If the Unity build were statically linked against the CRT (extremely unlikely on modern Unity 6), _dup2 would still succeed but Unity's native writes would go to a separate fd table, never passing through the pipe. The plugin would start cleanly and BepInEx-sourced lines would still appear in Discord — but world save lines and other native stdout output would be silently absent. You would only notice by their absence. On Linux this concern does not apply.

1.0.2

• Add configurable Source setting: BepInEx (default), Console, or RawStdout
• BepInEx — original ILogListener approach, unchanged
• Console — intercepts managed Console.Out via Console.SetOut()
• RawStdout — experimental, Linux only; intercepts stdout at the OS file descriptor level using pipe()+dup2(), capturing world saves, ZDO counts, and all native stdout writes that bypass BepInEx entirely. Falls back to BepInEx source on init failure.
• Fix recovery message title to include server name and timestamp
• Fix shutdown message to use consistent em-dash formatting

1.0.1

• Add server name and timestamp to the message title
• Don't double up timestamps in the message content
• Show log event source and level

1.0.0

• Initial release
• Pipes all BepInEx and Unity logs to a Discord webhook in near-real-time
• Local buffer file flushed on every line — nothing lost on unexpected shutdown
• FIFO queue — oldest logs sent first, catches up automatically after bursts
• Crash recovery — leftover buffer from previous session sent on next startup flagged as recovered
• Configurable send interval and max message size