UE5CEDumper — Unreal Engine 4/5 dumper (C++ DLL + Cheat Engine bridge + Avalonia UI).
About this release
Mostly fixes, plus a few Proxy Deploy additions. The biggest change: game folders, install paths and exe names with non-English characters, repeated spaces or symbols — EVERSPACE™ 2, DragonSword Awakening, No Man's Sky (not UE game, just as test case) — now work from injection through Cheat Engine to the exports. As before, the list is only what you are likely to notice; small fixes are not listed.
This is the final round of old code review.
New
- Proxy Deploy: "Use confirmed-working proxy". For a game whose working proxy type is already known, Deploy puts that type into a clean folder (after a reinstall, say), whatever type is selected above.
- Proxy Deploy never adds a second proxy of ours to a game that already has another type. Two of them in one game get in each other's way, and removing one could delete the one that worked. The row says why it was skipped; Undeploy first to switch type.
- Force-null now works on weak object pointer fields.
- High-DPI screens (e.g. 4K at 225 %): the main tab strip takes two rows instead of three, both Snapshot grids have room, and Class Pivot's field picker and results fit in the window — the long explanations moved into tooltips.
Fixed
- Injecting through the Cheat Engine table or the generated scripts from a folder with non-English characters could fail silently, or load the DLL half-working. It now uses a path Cheat Engine can open, or tells you why it cannot.
- Cheat Engine addresses (
module+offset) did not resolve for exe names with non-English characters: they now use the module name Cheat Engine itself sees. - An apostrophe in the exe name broke the trainer script, and an
&made the CE XML export invalid. - An exe name ending in a space or a dot got a log folder that could not be opened.
inject-ue.ps1could not find the DLL in a folder whose name has brackets, and broke paths with spaces when it restarted itself as administrator.UE5CEDumper.CTcould forget or misread its DLL folder: a drive root such asE:\, or recent files with non-English paths.- Starting a scan while the game was still loading could fail with an internal error. It now completes, and finds GObjects even that early.
- Stock UE 5.3 games (e.g. DragonSword, Avowed) were detected as 5.4. The Gravity Direction card works from 5.3, not only 5.4.
- Function flags were read from the wrong place in some games (e.g. DRAGON QUEST XI S, where one function in five had garbage parameter counts), which affected function lists and calls.
- DRAGON QUEST XI S: maps keyed by names read the wrong entries.
- Development / DebugGame builds and the UE editor (
-game): names now resolve and name numbers are correct (UE 4 and 5). In Development / DebugGame games on UE 5.4 and later, the name table is now found by a pattern made for those builds instead of a last-resort one, which cuts that step by a quarter to a third. - More memory layouts are measured on the running game instead of assumed from its version (UE 4.9–4.14 enums, UE 5.2, 5.7+, 5.8, soft object paths), so unusual builds are read correctly more often.
- Weak object pointers show null, null (stale) or unreadable instead of raw hex, and a target that is being destroyed is marked
[garbage]— on UE 5.0–5.3 too. - Find References now finds delegate bindings kept in "sparse" storage (e.g. CharacterMovement's), and says when it had to skip them.
- CE XML export of a very large container stops at Cheat Engine's 60,000-entry limit and is marked TRUNCATED, instead of producing a table that is silently too big.
- Instance Finder: a truncated copy tells you which setting to lower (Array Limit), and an export can no longer mix one walk's rows with another instance or limit.
- Cheat Engine: after re-injecting the DLL, freezes and function calls could stop working for the rest of the session. An older invoke helper already loaded in Cheat Engine is now replaced by the newer one.
- Unticking Fly, Keep Foreground or See-through in Cheat Engine could pop a dialog over the game.
- See-through was refused with "Not supported on this game build" on games that do support it (a regression in v3546).
- CSX export: string fields had half their real byte size.
- Snapshots: a complete capture could be reported as partial, and SPC Query's pickers now mark partial captures.
- Dump All, the Dump Explorer and exports could have their final status overwritten by a late progress message.
- After a reconnect, Property Search did not show the Force holds that were still active.
- A busy AOBMaker connection was reported as "open Cheat Engine" or "reinstall the plugin".
- Proxy Deploy: Update All ignored Force Overwrite; a Deploy that changed nothing reported "deployed"; a proxy-named file that cannot be read is now left alone and reported; and a game whose exe name another game also ships is marked as ambiguous, with a Load column that says when the load may be the other game's.
- The UI now runs on Avalonia 12.1.3.
⚠ Force Overwrite is remembered between sessions. If it is ticked, Update All now rewrites every deployed proxy of ours — a running game's proxy then reports "Target in use".
ℹ️ To use
UE5Dumper.dllas a Cheat Engine plugin, put it in a folder whose path is plain English letters. Cheat Engine itself cannot load a plugin from a path with non-English characters (it reports error 126).
Details for anyone who wants them: v3546…v3560
⚠ If anything regresses for you, fall back to v3546.
Setup
- Deploy proxy DLL from UI's Proxy Deploy tab (recommended), inject via UI's Proxy Deploy tab (AntiVirus may block UI; add it to exclude list), inject via the bundled Cheat Engine table (
UE5CEDumper.CT), or drop the proxyversion.dllinto the game'sBinaries\Win64(manual mode). - If neither
version.dllnordinput8.dllis loaded by your game, trydxgi.dll; if that filename is already taken (ReShade commonly uses it), trywinmm.dll. - See
Readme.mdfor details.
The exe is unsigned — Windows SmartScreen / antivirus may warn on first run. Verify the download with the included
.sha256.
Inject scripts likeinject-ue.ps1orUE5DumpUI.exemay be labeled as a hacking tool by antivirus. Add them to your exclusion list, or review the code in this repository and compile it yourself.