You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This guide is for players moving from the old shell-script-based `linux-steam-setup` to the AppImage launcher.
4
+
5
+
## What Changes
6
+
7
+
- Peacock and Node.js move into the launcher-managed install directory.
8
+
- The old `peacock.service` is replaced with the launcher's service definition.
9
+
- If your old service started automatically or was already running, the launcher restores that state.
10
+
- Legacy patcher files such as `PeacockPatcher.exe` and `WineLaunch.bat` are removed from detected game folders.
11
+
- The old batch-file injection flow is retired. Use ZHMModSDK with OnlineTools after migrating.
12
+
13
+
## Before You Start
14
+
15
+
1. Make sure the legacy install still exists on disk.
16
+
2. Close HITMAN 3 before starting migration.
17
+
3. If you edited your old setup manually, keep the legacy directory until you confirm the new launcher setup works.
18
+
19
+
## Migration Steps
20
+
21
+
1. Launch the AppImage.
22
+
2. Select **Migrate from old setup**.
23
+
3. Confirm the detected folder, or choose **Browse for folder…** if your install lives somewhere else.
24
+
4. Start migration.
25
+
5. When the wizard finishes, keep the old directory until you have tested the new setup once.
26
+
27
+
## Switch From The Old Patcher Method
28
+
29
+
After migration, do not go back to `WineLaunch.bat`, `Hitman 3 (Peacock).desktop`, or `PeacockPatcher.exe`.
30
+
31
+
Instead:
32
+
33
+
1. In the launcher, open **Manage ZHMModSDK**.
34
+
2. Install ZHMModSDK into your HITMAN 3 directory.
35
+
3. Start the game normally through Steam or Heroic.
36
+
4. Open the SDK panel in-game and enable **OnlineTools**.
37
+
5. In OnlineTools, use **Help** → **Load Old Patcher Settings**.
38
+
6. Confirm the server address is `localhost:3000` unless you changed the Peacock port.
39
+
40
+
If you changed the Peacock port in the launcher settings, use `localhost:PORT` with your selected port instead.
41
+
42
+
## After Migration
43
+
44
+
1. Check **Manage Service** in the launcher and confirm the service is installed.
45
+
2. If you want Peacock running in the background automatically, ensure **Enable on Boot** is set.
46
+
3. Start HITMAN 3 and verify OnlineTools connects successfully.
47
+
4. Delete the old legacy directory only after you are satisfied the new setup works.
48
+
49
+
## Troubleshooting
50
+
51
+
- If Peacock is not reachable, open **Manage Service** in the launcher and verify the service is running.
52
+
- If OnlineTools is missing, reinstall ZHMModSDK from the launcher and restart the game.
53
+
- If you still have old patcher files in a custom game folder the launcher did not detect, remove `PeacockPatcher.exe` and `WineLaunch.bat` manually and continue using the normal game launch path.
6. (Optional) Select **Manage ZHMModSDK** to install the SDK into your Hitman 3 directory
30
+
5. Select **Manage Service** → **Install Service** → **Start Service** to have Peacock running in the background
31
+
6. (Optional) Select **Enable on Boot** to have Peacock start automatically when you log in
32
+
7. (Optional) Select **Manage ZHMModSDK** to install the SDK into your Hitman 3 directory
33
+
34
+
## Migrating From The Legacy Setup
35
+
36
+
If you were using the old shell-script setup, open the launcher and select **Migrate from old setup**.
37
+
38
+
- The launcher copies your Peacock and Node.js files into the new managed location.
39
+
- Any existing `peacock.service` is replaced with the launcher-managed service definition.
40
+
- If the old service was enabled or running, that state is restored after migration.
41
+
- Old `PeacockPatcher.exe` and `WineLaunch.bat` files are removed from detected game folders.
42
+
- After migration, switch to **ZHMModSDK + OnlineTools** for patching. Do not keep using the old batch-file injection flow.
43
+
44
+
See [MIGRATION.md](MIGRATION.md) for the full migration checklist.
32
45
33
46
## Navigation
34
47
@@ -37,7 +50,6 @@ A TUI (Terminal User Interface) application for managing [Peacock](https://thepe
37
50
|`↑``↓`| Move between menu items |
38
51
|`Enter`| Select / confirm |
39
52
|`Esc`| Go back |
40
-
|`q`| Quit (from main menu) |
41
53
42
54
## Connecting to Peacock
43
55
@@ -117,7 +129,7 @@ cargo appimage
117
129
118
130
## Legacy Setup
119
131
120
-
The old shell-script-based setup files are preserved in the [`legacy/`](legacy/) directory for reference. The launcher includes a migration wizard to move an existing legacy install to the new location.
132
+
The old shell-script-based setup files are preserved in the [`legacy/`](legacy/) directory for reference. The launcher includes a migration wizard to move an existing legacy install to the new location, and the recommended path is documented in [MIGRATION.md](MIGRATION.md).
0 commit comments