This guide is for players moving from the old shell-script-based linux-steam-setup to the AppImage launcher.
- Peacock and Node.js move into the launcher-managed install directory.
- The old
peacock.serviceis replaced with the launcher's service definition. - If your old service started automatically or was already running, the launcher restores that state.
- Legacy patcher files such as
PeacockPatcher.exeandWineLaunch.batare removed from detected game folders. - The old batch-file injection flow is retired. Use ZHMModSDK with OnlineTools after migrating.
- Make sure the legacy install still exists on disk.
- Close HITMAN 3 before starting migration.
- If you edited your old setup manually, keep the legacy directory until you confirm the new launcher setup works.
- Launch the AppImage.
- Select Migrate from old setup.
- Confirm the detected folder, or choose Browse for folder… if your install lives somewhere else.
- Start migration.
- When the wizard finishes, keep the old directory until you have tested the new setup once.
After migration, do not go back to WineLaunch.bat, Hitman 3 (Peacock).desktop, or PeacockPatcher.exe.
Instead:
- In the launcher, open Manage ZHMModSDK.
- Install ZHMModSDK into your HITMAN 3 directory.
- Start the game normally through Steam or Heroic.
- Open the SDK panel in-game and enable OnlineTools.
- In OnlineTools, use Help → Load Old Patcher Settings.
- Confirm the server address is
localhost:3000unless you changed the Peacock port.
If you changed the Peacock port in the launcher settings, use localhost:PORT with your selected port instead.
- Check Manage Service in the launcher and confirm the service is installed.
- If you want Peacock running in the background automatically, ensure Enable on Boot is set.
- Start HITMAN 3 and verify OnlineTools connects successfully.
- Delete the old legacy directory only after you are satisfied the new setup works.
- If Peacock is not reachable, open Manage Service in the launcher and verify the service is running.
- If OnlineTools is missing, reinstall ZHMModSDK from the launcher and restart the game.
- If you still have old patcher files in a custom game folder the launcher did not detect, remove
PeacockPatcher.exeandWineLaunch.batmanually and continue using the normal game launch path.