From 0816d987f81bf356ad2233eb1669cddc7f6e7652 Mon Sep 17 00:00:00 2001 From: Dusk-92 Date: Mon, 31 Aug 2026 22:45:53 +0200 Subject: [PATCH] Document automatic Discord companion startup --- native/DiscordPresence/README.md | 18 +++++++++++++++--- 1 file changed, 15 insertions(+), 3 deletions(-) diff --git a/native/DiscordPresence/README.md b/native/DiscordPresence/README.md index 39b7832..850a7f5 100644 --- a/native/DiscordPresence/README.md +++ b/native/DiscordPresence/README.md @@ -2,8 +2,18 @@ This test branch builds two 32-bit native Windows components: -- `DiscordPresence.dll` — loaded by VanillaFixes; reads WoW 1.12.1 character state read-only. -- `DiscordPresence.exe` — invisible companion that launches `VanillaFixes.exe WoW_Modernized.exe`, reads the status file, and talks to Discord IPC. +- `DiscordPresence.dll` — loaded by VanillaFixes; reads WoW 1.12.1 character state read-only, writes the status snapshot, and starts the companion from its worker thread after WoW startup. +- `DiscordPresence.exe` — invisible companion that only reads the status file and talks to Discord IPC. It no longer launches WoW. + +The normal game launch path stays unchanged: + +``` +Play Modernized WoW + -> VanillaFixes.exe WoW_Modernized.exe + -> WoW_Modernized.exe + -> DiscordPresence.dll + -> DiscordPresence.exe +``` The OctoWoW Discord Application ID is built into `DiscordPresence.exe`: @@ -24,4 +34,6 @@ Runtime data is stored under: discord_application_id (optional override) ``` -The DLL never connects to Discord. The companion never reads or writes WoW memory. +The companion is never launched from `DllMain`; it is started only from the DLL worker +thread after the startup delay. The DLL never performs Discord IPC, and the companion +never reads or writes WoW memory.