Skip to content
This repository was archived by the owner on Jan 18, 2024. It is now read-only.

Home

Jump to bottom
funjoker edited this page Aug 1, 2023 · 16 revisions

Welcome to the TrinityCore 4.3.4.15595 wiki

This page is going to address all TCPP related information.

Please check https://trinitycore.info/ for general information about TrinityCore (e.g. setup).

I need a full client

Please check I need a full client

Note: If you followed the "I need a full client" part, you can skip this part!

Both Windows and MacOS need a valid WoW.mfil in the World of Warcraft root dir with following content:

version=2
server=akamai
    location=http://dist.blizzard.com.edgesuite.net/wow-pod-retail/EU/15050.direct/
manifest_partial=wow-15595-0C3502F50D17376754B9E9CB0109F4C5.mfil

Make sure you protect the file from changes by setting write protection (Windows) or locked (MacOS)

How to connect using connection_patcher

Windows:

You have to patch the following game components:

  • the Wow.exe or Wow-64.exe
  • the Battle.net.dll or Battle.net-64.dll (happens automatically)
  • the Wow authentication modules which will be downloaded and patched by the connection patcher itself. If the connection patcher should somehow fail to retrieve the auth modules, you can find a backup dump of the modules here: https://github.com/The-Cataclysm-Preservation-Project/AuthModules
  1. You have to download all modules by yourself. https://github.com/The-Cataclysm-Preservation-Project/AuthModules/tree/master/Windows The path must be exactly the same "C:/ProgramData/Blizzard Entertainment/Battle.net/Cache/..." as represented in the repository.
  2. Get a Clean Wow.exe and a clean Battle.net.dll (4.3.4.15595) and/or Wow-64.exe and Battle-64.net.dll (look at 'I need a full client') !!! DO NOT HAVE THEM IN USERS FOLDER (e.g. C:/Users/braindead/Wow) CHOOSE A PATH LIKE C:/Games/WoW/ !!!
  3. Drag Wow.exe and/or Wow-64.exe on connection_patcher
  4. Check log if everything worked
  5. Rename the existing Wow.exe and Battle.net.dll and/or Wow-64.exe and Battle-64.net.dll OR move them to another folder
  6. Rename the Wow_patched.exe and the Battle.net_patched.dll and/or the Wow-64_patched.exe and Battle-64.net_patched.dll to: Wow.exe Battle.net.dll Wow-64.exe Battle-64.net.dll
  7. If you have a Launcher.exe rename it into something else (e.g. Launcher-Backup.exe)

THE EXE AND DLL FILES MUST BE ORIGINAL! You can NOT patch a exe file that has already been patched for private servers. If you have been playing on other private server with your WoW.exe, your exe is defitnively NOT original.

MacOS:

You have to patch the following game components:

  • the 'World of Warcraft-64.app' (in fact the components inside are being patched)
  • the Wow authentication modules which will be downloaded and patched by the connection patcher itself. If the connection patcher should somehow fail to retrieve the auth modules, you can find a backup dump of the modules here: https://github.com/The-Cataclysm-Preservation-Project/AuthModules
  1. Get a clean 'World of Warcraft-64.app' (look at 'I need a full client')
  2. Open Terminal and drag connection_patcher on it and after that the 'World of Warcraft-64.app' and hit Return/Enter.
  3. Check log if everything worked
  4. Rename the existing 'World of Warcraft-64.app' OR move them to another folder
  5. Rename 'World of Warcraft-64_patched.app' to 'World of Warcraft-64.app'
  6. If you have a Launcher.app rename it into something else (e.g. Launcher-Backup.app)
  7. Go to '/Users/Shared/Blizzard/Battle.net/Cache/19/c9/' folder and locate the '19C91B68752B7826DF498BF73ACA1103C86962A9A55A0A7033E5AD895F4D927C.auth' file
  8. Rightclick and select 'Get Info' and check 'Locked'

Screenshot 2022-02-24 at 01 21 42 This is important!

Linux:

Linux is not supported. The new patching method requires the client to have access to the programm data directory which is not emulated by Wine or Proton so unless you can replicate that filesystem 1:1 do not expect the patcher to work on your OS. The auth modules are a crucial component for the login process so skipping them will not work.

THE APP MUST BE ORIGINAL! You can NOT patch an app file that has already been patched for private servers. If you have been playing on other private server with your 'World of Warcraft-64.app', your app is defitnively NOT original.

I have patched everything, what now?

Once the patching is complete you should have a Wow-patched.exe or a Wow-64-patched.exe as well as a battle.net-patched.dll or a battle.net-64-patched.dll. If that is the case, delete the original battle.net.dll and replace it with the patched version. Once it's done you are set to go

How to connect using client_launcher and client_patcher

Note 1: client_launcher_32 will only run 32bit Wow and client_launcher_64 only 64bit Wow

Note 2: You need client_launcher_XX.exe AND client_patcher_XX.dll

Note 3: Minimum Boost version is 1.74 (Windows)

Step 1: Get Clean Wow.exe and Battle.net.dll or the 64bit version

Step 2: Make sure there is no original Launcher.exe inside WoW folder

Step 3: Get client_launcher_32.exe and client_patcher_32.dll or client_launcher_64.exe and client_patcher_64.dll and place them into wow folder.

Step 4: Run client_launcher

Additional options:

--console (displays client_patcher console (it's the AllocConsole of Wow Process)

--path -> path to Wow folder if launched outside wow folder

Troubleshooting

Please check Troubleshooting for connecting

Clone this wiki locally