Cross-platform support is a secondary goal after producing a functional Windows client. We can source functions from 0.5.5 (build 3494) (OS X) and 0.7.0 (build 3694) (Linux). The result would be an approximation of a cross-platform 0.5.3 client however we can't confirm what's authentic for the time.

When this project is complete we should have ~400k lines of code and 22k+ functions in this repo. These figures are based on information from the original client.

This isn't a reimplementation project taking advantage of modern standards. We're supporting the original toolchain and following every bit of original information we can use.

1. C/C++ standards must be restricted to the features available in Visual C++ 6.0 (1998)
2. Use Windows datatypes. All platforms used the same datatypes at the time.

All of the original source file paths have been created as empty files ahead of time, and registered in CMake. Use them as you write functions. You should not need to add any new .cpp files, but feel free to create headers.

Firstly, you'll need to install CMake no matter what OS you're on: cmake.org

Older Visual Studio versions are untested and depending how far back you go, may have incompatibilities with newer CMake. The codebase should work anyways. Good luck if you go that route!

Inside the Build folder there are a couple scripts:

• vs2022-setup.bat: Have CMake produce a Visual Studio 2022 solution.
• vc6-setup.bat: Have CMake produce NMake makefiles for Visual C++ 6.0. Visual C++ 6.0 must be installed to C:\Program Files (x86)\Microsoft Visual Studio 6.0\

Inside the Build folder there are several scripts:

• xcode-setup.sh: Have CMake produce an Xcode project targeting native macOS.
• native-setup.sh: Have CMake produce Makefiles targeting your default toolchain.
• mingw-setup.sh: Have CMake produce Makefiles targeting MinGW.
• wine.sh: Install, setup cmake, build, and run Visual C++ 6.0 makefiles via Wine. This can take several minutes the first time.

Inside the Build folder there are a few scripts:

• native-setup.sh: Have CMake produce Makefiles targeting your default toolchain.
• mingw-setup.sh: Have CMake produce Makefiles targeting MinGW.
• wine.sh: Install, setup cmake, build, and run Visual C++ 6.0 makefiles via Wine. This can take several minutes the first time.

You can copy everything in your game client folder to WoW/Client/ to keep track of things easily. The instructions here are written with this as an example path.

The original game client was meant to use a launcher so you have to pass -uptodate if you launch it directly, and be sure to create a file in the same folder called wow.ses containing your username/password on separate lines.

To accomplish these goals we're rewriting every function in the original WoWClient.exe, and loading these replacements at runtime using Detours. With this approach the game client will stay playable while we work towards complete coverage.

The hook can run in two ways, either by proxying fmod.dll calls so it gets loaded on startup or through injection (use whatever injector you want). The first method is more reliable and recommended.

To set up the dll proxy

1. Rename the original WoW/Client/fmod.dll to WoW/Client/fmod2.dll
2. Copy WoW/WowHook.dll to WoW/Client/fmod.dll
3. Start WoW/Client/WoWClient.exe -uptodate

This will be in an incomplete state until the project covers a majority of critical functions.

1. Set your working directory to the WoW/Client/ folder.
2. Run the Wow project.

Original executables:

• WoW.exe: This was produced from UpdateClient.cpp, it was called WoW due to the update process during the alpha/early beta. The map file is UpdateClient.map
• WoWClient.exe: This was produced from Client.cpp, it was called WoWClient due to the update process during the alpha/early beta. The pdb file is Wowae.pdb (Wow + Assertions Enabled build)
• WowError.exe: todo explanation
• WowUpdateHelper.exe: todo explanation

Libraries:

• Expat 1.95.5
• FreeType 2.0
• Lua 5.0
• Zlib 1.1.4