Skip to content

Latest commit

 

History

History
62 lines (47 loc) · 2.54 KB

README.md

File metadata and controls

62 lines (47 loc) · 2.54 KB
Raw

Dumper-7

SDK Generator for all Unreal Engine games. Supported versions are all of UE4 and UE5.

How to use

  • Compile the dll in x64-Release
  • Inject the dll into your target game
  • The SDK is generated into the path specified by Settings::SDKGenerationPath, by default this is C:\\Dumper-7
  • See UsingTheSDK for a guide to get started, or to migrate from an old SDK.

Support Me

KoFi: https://ko-fi.com/fischsalat
Patreon: https://patreon.com/user?u=119629245

Changelog

Summary:

  • Added TUObjectArrayWrapper which automatically initializes GObjects the first time it's accessed
  • Added predefined member ULevel::Actors to the SDK
  • Added support for more Properties
  • Functions with EFunctionFlags::Static are now automatically called on the classes' DefaultObject
  • Fixed name-collisions between classes/structs, between enums, between members/functions, and between packages
  • Fixed cyclic dependencies
  • Fixed incorrect size/alignment on classes

You can find the full changelog for the new GeneratorRewrite in Changelog.md.

Overriding Offsets

  • Only override any offsets if the generator doesn't find them by itself

  • All overrides are made in Generator::InitEngineCore() inside of Generator.cpp

  • GObjects

    ObjectArray::Init(/*GObjectsOffset*/, /*ChunkSize*/, /*bIsChunked*/);
    /* Make sure only to use types which exist in the sdk (eg. uint8, uint64) */
InitObjectArrayDecryption([](void* ObjPtr) -> uint8* { return reinterpret_cast<uint8*>(uint64(ObjPtr) ^ 0x8375); });

  • FName::AppendString

    FName::Init(/*FName::AppendStringOffset*/);

  • ProcessEvent

    Off::InSDK::InitPE(/*PEIndex*/);

Issues

If you have any issues using the Dumper, please create an Issue on this repository
and explain the problem in detail.

  • Should your game be crashing while dumping, attach Visual Studios' debugger to the game and inject the Dumper-7.dll in debug-configuration. Then include screenshots of the exception causing the crash, a screenshot of the callstack, as well as the console output.

  • Should there be any compiler-errors in the SDK please send screenshots of them. Please note that only build errors are considered errors, as Intellisense often reports false positives. Make sure to always send screenshots of the code causing the first error, as it's likely to cause a chain-reaction of errors.

  • Should your own dll-project crash, verify your code thoroughly to make sure the error actually lies within the generated SDK.