3.19.3

Caution

Do not use this on Warmane. Their anti-cheat flags performance injectors and
memory optimization tools as illegal software regardless of intent, and the
result is a permanent ban on your account.

Warning

On WoW Circle the DLL gets you disconnected - Turning on No Client Patches
in the launcher stops it, and also turns every optimization off.
Or use the !LuaBoost addon without the DLL.

Fixed

• Entering the world with ReShade loaded. The hook on
  InitializeCriticalSection has its own switch, Critical Section Hook (All
  Modules), and it is off. Reported by Hoshi [HSR].
• Hooks on Windows and CRT exports answer the game only. ReShade, DXVK,
  overlays and drivers get the real function. The switch is System Hooks: Game
  Only.
• MAX PERFORMANCE leaves an unproven switch at its own default. Anything
  marked [+] or [!] is yours to tick.
• Quitting the game writes no access violation to the log.
• Two clients started from one game folder each get their own log file and
  their own compiled-script store.
• Manual Lua collection survives a UI reload, and with it the emergency
  collection that starts at 300 MB of Lua memory.
• An intercepted Lua error keeps its traceback.

Faster

• The game's string hash runs on an SSE2 replacement. The game hashes
  strings about twenty-seven million times an hour. The replacement is checked
  against the game's own routine for its first 4096 calls and on one call in a
  thousand after that; a single disagreement hands every later call back.
• Eight of the hottest replacements run without an exception frame once a
  million calls have gone by with nothing for the guard to catch.
• New SSE2 replacements, each off by default and each checking itself
  against the game's own routine before it is used: particle vertex fill, UI
  batch fill, ray against triangle (1.89x), collision ray outcode (16.43x),
  quaternion unpack (7.33x).

Reports

• A marked frame is in the dump it triggered. The flight recorder keeps the
  frames nearest the mark.
• A slow frame says what ran inside it: a Lua compile over 20 ms, a change
  in address-space pressure, a loading boundary, a lua_State swap. When several
  slow frames share one report, the worst of them is named beside the one
  written up.
• A crash dump identifies the build it came from without a log beside it.

Installing

Unpack all files into the folder with Wow.exe, replacing what is there:

• wow_optimize.dll
• wow_optimize_launcher.exe
• version.dll

Start the game through wow_optimize_launcher.exe.

Reporting something

Send the log from Logs\ whole, without trimming the first lines: they name the
build it came from. If the game crashed, send the .dmp from Crashes\ with it.