From 43b27e674a388329fe93a874f662cfd837bc0f1c Mon Sep 17 00:00:00 2001
From: Alexa <53471801+Alexa-RR@users.noreply.github.com>
Date: Sat, 30 May 2026 02:13:35 +0300
Subject: [PATCH] advanced-setup: patch client via MelonLoader, not BepInEx

The BepInEx client patcher is gone; document the MelonLoader installer
(install-melon.ps1 on the version branch) dropping DorkNet.ClientMod
into Mods/ instead of a BepInEx plugin into BepInEx/plugins/.
---
 docs/advanced-setup.md | 11 +++++++----
 1 file changed, 7 insertions(+), 4 deletions(-)

diff --git a/docs/advanced-setup.md b/docs/advanced-setup.md
index 57a1695..a546198 100644
--- a/docs/advanced-setup.md
+++ b/docs/advanced-setup.md
@@ -103,17 +103,20 @@ server is ready at `https://api.your-server.example.com/healthz`.
 
 ## Patching the client to point here
 
-Same patcher as Easy mode, but you'll run it from the command line:
+Same patcher as Easy mode, but you'll run it from the command line. The
+CLI installer ships on the version-specific branch (e.g.
+`december-2020-12-18`):
 
 ```powershell
-.\tools\install-plugin.ps1 `
+.\tools\install-melon.ps1 `
   -RecRoomPath "C:\path\to\Recroom_Release_Data" `
   -PhotonAppId "<your-photon-realtime-app-id>" `
   -PhotonVoiceAppId "<your-photon-voice-app-id>"
 ```
 
-The installer drops the DorkNet BepInEx plugin into the client's
-`BepInEx/plugins/` and writes its config under `BepInEx/config/`.
+The installer drops the DorkNet MelonLoader mod (`DorkNet.ClientMod`)
+into the client's `Mods/` folder and writes its config under
+`MelonLoader/UserData/`.
 
 ## Admin UI