Dusk/Modernization-Tool
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases 5 Wiki Activity

Document automatic Discord companion startup

Browse Source
This commit is contained in:
Dusk-92
2026-08-31 22:45:53 +02:00
parent 75c77c6b71
commit 0816d987f8
1 changed files with 15 additions and 3 deletions
Download Patch File Download Diff File Expand all files Collapse all files
native/DiscordPresence/README.md
+15 -3
View File
@@ -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.