Injectable LUA scripting system, SDK generator, live property editor and other dumping utilities for UE4/5 games
Lua scripting system platform, C++ Modding API, SDK generator, blueprint mod loader, live property editor and other dumping utilities for UE4/5 games.
.usmap
mapping files for unversioned properties.umaps
in-editorThe goal of UE4SS is not to be a plug-n-play solution that always works with every game. The goal is to have an underlying system that works for most games. You may need to update AOBs on your own, and there's a guide for that below.
The easiest installation is via downloading the non-dev version of the latest non-experimental build from Releases and extracting the zip content to /{Gameroot}/GameName/Binaries/Win64/
.
If your game is in the custom config list, extract the contents from the relevant folder to Win64
as well.
If you are planning on doing mod development using UE4SS, you can do the same as above but download the zDEV version instead.
Generating UHT compatible headers
Creating Compatible Blueprint Mods
Unreal Engine Modding Discord Server Invite
git submodule update --init --recursive
Make sure your Github account is linked to your Epic Games account for UE source access.
Do not use the --remote
option because that will force third-party dependencies to update to the latest commit, and that can break things.
You will need your github account to be linked to an Epic games account to pull the Unreal pseudo code submodule.There are several different ways you can build UE4SS.
Configure the project using this command: xmake f -m "<BuildMode>"
The build modes are structured as follows: <Target>__<Config>__<Platform>
Currently supported options for these are:
Target
Game
- for regular gamesCasePreserving
- for games built with case preserving enabledConfig
Dev
- development buildDebug
- debug buildShipping
- shipping(release) buildTest
- build for testsPlatform
Win64
- 64-bit windowsNow to build it, just run xmake
To generate Visual Studio project files, run the xmake project -k vsxmake2022
command.
Afterwards open the generated .sln
file inside of the vsxmake2022
directory
Note that you should also commit & push the submodules that you've updated if the reason why you updated was not because someone else pushed an update, and you're just catching up to it.
Note the following about how xmake interacts with VS
The vs. build plugin performs the compile operation by directly calling the xmake command under vs, and also supports intellisense and definition jumps, as well as breakpoint debugging.
This means that modifying the project properties within Visual Studio will not affect which flags are passed to the build when VS executes xmake
. XMake provides some configurable project settings
which can be found in VS under the Project Properties -> Configuration Properties -> Xmake
menu.
If you want to update git submodules, you do so one of three ways:
git submodule update --init --recursive
to update all submodules.git submodule update --init --recursive deps/<first-or-third>/<Repo>
.
Do not use the --remote
option unless you actually want to update to the latest commit.cd
into the submodule directory for that dependency and execute git checkout <branch name or commit>
.
The main dependency you might want to update from time to time is deps/first/Unreal
.All contributors since the project became open source: https://github.com/UE4SS-RE/RE-UE4SS/graphs/contributors