Skip to content

Proxy Deploy

Jump to bottom
bbfox0703 edited this page Jun 25, 2026 · 2 revisions

🌐 English · 繁體中文 · 日本語

Proxy Deploy

The Proxy Deploy tab lets you scan for UE games installed via Steam, deploy a proxy DLL to each game folder, and manage proxy updates across multiple games. This is the recommended method to inject UE5CEDumper into games without using Cheat Engine — just place the proxy DLL, launch the game normally, and connect the UI.

Quick Start

See Quick-Start for build and installation basics. This page covers deployment after you have built the proxy DLLs.

The Main Workflow

1. Select a Proxy Type

At the top of the Proxy Deploy tab, choose which DLL to deploy:

Proxy Type When to Use
version.dll (recommended) Start here first. Loaded by virtually every Windows process during normal operation, broadest game compatibility. The proxy loads at a safe time (under GetFileVersionInfo / COM / manifest parsing), not during the early loader lock. Default choice.
dinput8.dll Fallback when version.dll conflicts with an installer check or anti-tamper shim. Some games check that version.dll is the "real" Windows version before allowing save loads — if deploying version.dll causes the game to refuse to load saves or run, try dinput8.dll.
dxgi.dll Fallback for rare D3D11/D3D12 games that import neither version.dll nor dinput8.dll in their main EXE (e.g., some SQUARE ENIX or Bandai Namco titles). Since every D3D11/D3D12 UE game imports dxgi.dll, this proxy loads reliably when the other two don't.

The UI shows tooltips explaining each choice; hover to read more.

2. Scan for Games

Click the Scan Steam button. The UI will:

  1. Locate your Steam installation (via the registry or default path).
  2. Parse libraryfolders.vdf to find all configured Steam library folders.
  3. Walk SteamApps/common/ to find UE game folders.
  4. Identify game executables and their Binaries/Win64/ directories.

When complete, the scan displays all detected games in the table. The Status column shows whether the selected proxy type is NotDeployed, DeployedCurrent, DeployedOutdated, DeployedOtherType, or OtherProxy.

3. Select Games

By default, no games are selected. Use the buttons or checkboxes to choose which games to deploy to:

  • All — select every game in the list.
  • None — clear all selections.
  • Invert — toggle the selection state of every game.
  • Click individual checkboxes in the leftmost column to select one game at a time.

4. Deploy to Selected Games

With games selected, click Deploy to copy the proxy DLL to each game's Binaries/Win64/ folder. The UI will show a summary when finished (e.g., "Deployed: 5 success, 0 failed").

Once deployed, the game's Status column shows DeployedCurrent with the installed proxy version. The proxy DLL will load automatically the next time you run the game.

Update & Redeploy

Redeploying a Single Proxy Type

If you rebuild the proxy DLLs (via build.ps1), use Deploy again with Force Overwrite unchecked to skip games that already have the same version. Check Force Overwrite to replace them anyway, even if the version matches.

Updating All Deployed Proxies at Once

Click Update All to scan every game's Binaries/Win64/ folder and update any of your proxy DLLs (version.dll, dinput8.dll, dxgi.dll) that are already deployed to the latest version built in the UI's proxy/ directory. This is useful when you've rebuilt a new version and want to roll it out to all games at once without picking them individually.

The Update All workflow:

  1. Finds the latest version of every proxy type you have in the UI's proxy/ folder.
  2. For each game, checks which of your proxy DLLs are already deployed.
  3. Updates only the deployed proxies for each game (e.g., if a game has version.dll and dinput8.dll, it updates both independently). The update is independent of which proxy type radio button is currently selected.
  4. Reports the number updated, already up-to-date, and failed.

Note: A single deployed proxy of any type is normal and does not warn. If you accidentally deploy multiple proxies (e.g., both version.dll and dinput8.dll) to the same game, the Status column will show a warning — only one proxy activates at runtime, so this is likely a mistake. Use Undeploy to remove the unwanted one.

Removing a Proxy

Select games and click Undeploy to delete the proxy DLL from the selected games' folders. The UI will only delete DLLs it recognizes as its own (by ProductName in the PE header); if another program's proxy DLL exists, Undeploy refuses to touch it.

When the Proxy Doesn't Load or Crashes the Game

If the UI can't connect to a game after deploying a proxy (or if the game crashes on startup):

  1. Check the game log: Look in the game folder for diagnostic log output. The proxy writes via logging calls, though the exact log file location and format depend on your build configuration.

  2. Switch proxy types:

    • If version.dll doesn't connect or crashes → try dinput8.dll.
    • If dinput8.dll doesn't connect or crashes → try dxgi.dll.
    • If dxgi.dll doesn't connect or crashes → try the next available proxy.

    Each proxy loads at a different point in the Windows loader sequence, so one that fails may succeed. The tab lets you redeploy by simply selecting a different radio button, choosing the same games again, and clicking Deploy (with Force Overwrite checked if the old proxy is still there).

  3. If no proxy works (EA launcher, Epic Games Launcher, games with aggressive anti-tamper):

    • The game's launcher or anti-cheat may block proxy DLLs entirely.
    • Fall back to Cheat Engine DLL injection: use Cheat Engine to load and inject UE5CEDumper.dll after the game is running. The DLL still detects the UE version and exposes the same pipe-based UI connection.
    • See Quick-Start for the CE injection workflow (Option A).

The Proxy Placement

The UI's proxy/ subfolder contains the built proxy DLLs:

  • proxy/version.dll — Deploy if chosen.
  • proxy/dinput8.dll — Deploy if chosen.
  • proxy/dxgi.dll — Deploy if chosen.

When you click Deploy, the proxy is copied to the target game's Binaries/Win64/ directory (the Binaries Path column shows the exact location). The service handles the modular-build placement; you don't need to manually navigate there.

If you're using a modular UE build (e.g., Satisfactory with separate CoreUObject-Win64-Shipping.dll), the proxy is still placed in the game's main Binaries/Win64/ folder and loads the dependencies from there.

Troubleshooting

Issue Solution
No games found after scan Steam is not installed, or no UE games are in your Steam library. Verify Steam is running and check SteamApps/common/ contains at least one UE game folder.
"Source DLL not found" error The proxy DLL was not built. Run build.ps1 -Target ProxyDLL (or -Target All to build everything) to create the DLL.
"File locked" when deploying The game is still running or a file is open. Close the game and any editor using that folder, then try again.
UI cannot connect after deploy See "When the Proxy Doesn't Load or Crashes the Game" above. Try switching proxy types and redeploying.
Multiple proxy DLLs warning in Status You accidentally deployed two or more proxies (e.g., version.dll and dinput8.dll) to the same game. Click Undeploy to remove the unwanted ones, then redeploy only the one you want.
Game crashes with deployed proxy The proxy type may conflict with the game's loader. Switch to a different proxy type and redeploy (with Force Overwrite checked).

Related Pages

  • Quick-Start — Build the proxy DLLs and set up the UI.
  • Home — Overview and feature guide.
  • Live-Walker — Browse running game objects in real-time.
  • Object-Tree — Navigate the game's class hierarchy.
  • Instances — Find all instances of a specific class.

Clone this wiki locally