RE-UE4SS

Unreal Engine 4/5 Scripting System

Lua scripting system platform, C++ Modding API, SDK generator, blueprint mod loader, live property editor and other dumping utilities for UE4/5 games.

Major features

• Lua Scripting API: Write lua mods based on the UE object system
• Blueprint Modloading: Spawn blueprint mods automatically without editing/replacing game files
• C++ Modding API: Write C++ mods based on the UE object system
• Live Property Viewer and Editor: Search, view, edit & watch the properties of every loaded object, great for debugging mods or figuring out how values are changed during runtime
• UHT Dumper: Generate Unreal Header Tool compatible C++ headers for creating a mirror .uproject for your game
• C++ Header Dumper: Generate standard C++ headers from reflected classes and blueprints, with offsets
• Universal UE Mods: Unlock the game console and other universal mods
• Dumpers for File Parsing: Generate .usmap mapping files for unversioned properties
• UMAP Recreation Dumper: Dump all loaded actors to file to generate .umaps in-editor
• Other Features, including Experimental features at times

Targeting UE Versions: From 4.7 To 5.8

The 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.

Basic Installation

The easiest installation is via downloading the non-dev version of the latest non-experimental build from Releases and extracting the zip content to {game directory}/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.

Command Line Options

If RE-UE4SS is installed via proxy DLL, the following command line options are available:

• --disable-ue4ss - Temporarily disable UE4SS without uninstalling by launching the game with this argument.
• --ue4ss-path <path> - Specify a custom path to UE4SS.dll. Supports both absolute paths (e.g., C:\custom\UE4SS.dll) and relative paths (e.g., dev\builds\UE4SS.dll relative to the game executable directory). Useful for testing different UE4SS builds without modifying installation files.

Environment Variables

RE-UE4SS supports the following environment variables:

• UE4SS_MODS_PATHS - Semicolon-separated list of additional mods directories to load. Paths are processed in reverse order (first entry has highest priority), similar to the PATH variable. Example: C:\SharedMods;D:\GameMods;E:\TestMods.

Links

Full installation guide

Fixing compatibility problems

Lua API - Overview

Generating UHT compatible headers

Custom Game Configs

Creating Compatible Blueprint Mods

UE4SS Discord Server Invite

Unreal Engine Modding Discord Server Invite

Build requirements

• A computer running Windows.
  • Linux support might happen at some point but not soon.
• A version of MSVC that supports C++23:
  • MSVC toolset version >= 14.43.0
  • MSVC version >= 19.43
  • Visual Studio version >= 17.13
  • More compilers will hopefully be supported in the future.
• Rust toolchain >= 1.73.0
• CMake >= 3.22
• A build system: either Ninja or MSVC (included with Visual Studio)

Build instructions

1. Clone the repo.
2. Execute this command: 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.

Building from CLI

Build Modes

The build modes are structured as follows: <Target>__<Config>__<Platform>

Currently supported options for these are:

• Target

  • Game - for regular games on UE versions greater than UE 4.21
  • LessEqual421 - for regular games on UE versions less than or equal to UE 4.21
  • CasePreserving - for games built with case preserving enabled

• Config

  • Dev - development build
  • Debug - debug build
  • Shipping - shipping(release) build
  • Test - build for tests

• Platform

  • Win64 - 64-bit windows

Basic Build Commands

To build UE4SS with CMake, use the following commands:

# Configure with Ninja (recommended for faster builds, single-configuration)
cmake -B build_cmake_Game__Shipping__Win64 -G Ninja -DCMAKE_BUILD_TYPE=Game__Shipping__Win64

# Build with Ninja
cmake --build build_cmake_Game__Shipping__Win64

# Or configure with MSVC (multi-configuration, allows switching configs without reconfiguring)
cmake -B build_cmake_Game__Shipping__Win64 -G "Visual Studio 17 2022"

# Build with MSVC (requires --config flag)
cmake --build build_cmake_Game__Shipping__Win64 --config Game__Shipping__Win64

Configuration Options

CMake allows you to configure various build options. Here are some useful options:

Proxy Path

By default, UE4SS generates a proxy based on C:\Windows\System32\dwmapi.dll. To change this, set the CMake variable:

cmake -B build -DUE4SS_PROXY_PATH="<path to proxy dll>" -DCMAKE_BUILD_TYPE=Game__Shipping__Win64

Profiler Flavor

By default, UE4SS has profiling disabled (None). To enable profiling, you need both a profiler flavor AND a build configuration that includes STATS:

# STATS are enabled by default in Dev and Test builds
cmake -B build -DPROFILER_FLAVOR=<Tracy|Superluminal|None> -DCMAKE_BUILD_TYPE=Game__Dev__Win64

[!NOTE] Profiling requires STATS support. By default, Dev and Test configurations include STATS, while Shipping and Debug do not. You can manually enable STATS for any configuration by adding compile definitions:

cmake -B build -DPROFILER_FLAVOR=Tracy -DCMAKE_BUILD_TYPE=Game__Shipping__Win64 -DCMAKE_CXX_FLAGS="-DSTATS"

Helpful CMake Commands

Command	Description
cmake -B <build_dir> -G <generator>	Configure the project with a specific generator (Ninja or "Visual Studio 17 2022")
cmake --build <build_dir>	Build with Ninja (single-config generator)
cmake --build <build_dir> --config <mode>	Build with MSVC (multi-config generator, --config required)
cmake --build <build_dir> --clean-first	Clean and rebuild (add --config <mode> for MSVC)
cmake --build <build_dir> --target <target>	Build a specific target (add --config <mode> for MSVC)
cmake --build <build_dir> --verbose	Build with verbose output (add --config <mode> for MSVC)

Opening in an IDE

Visual Studio

CMake has built-in support for generating Visual Studio solutions:

cmake -B build -G "Visual Studio 17 2022"

Then open the generated .sln file in the build directory.

Alternatively, Visual Studio 2022 has native CMake support - you can open the folder directly in Visual Studio and it will automatically detect the CMakeLists.txt file.

CLion / Other CMake IDEs

Most modern IDEs (CLion, Visual Studio Code with CMake Tools, etc.) have native CMake support. Simply open the project folder and the IDE will automatically detect and configure the CMake project.

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.

Cross-Compiling Windows Binaries on Linux

UE4SS supports cross-compilation from Linux to Windows using two approaches: xwin (recommended) or msvc-wine.

Prerequisites for All Cross-Compilation

• Rust toolchain >= 1.73.0 with the x86_64-pc-windows-msvc target:

  rustup target add x86_64-pc-windows-msvc
  

• CMake >= 3.22
• Ninja build system

Option 1: Cross-Compiling with xwin (Recommended)

xwin downloads and packages the Microsoft CRT headers/libraries and Windows SDK headers/libraries needed for cross-compilation, without requiring a Windows installation.

Prerequisites

• LLVM/Clang with Windows target support:

  # On Ubuntu/Debian
  sudo apt install clang lld llvm
  
  # On Arch Linux
  sudo pacman -S clang lld llvm
  

• xwin:

  cargo install xwin
  

Setup

1. Download the Microsoft tools and SDK using xwin (this only needs to be done once):

   xwin --accept-license splat --output ~/.xwin
   

   This will download approximately 300MB and can take a few minutes.

2. Set the XWIN_DIR environment variable:

   export XWIN_DIR=~/.xwin
   

Building Manually with CMake

# Configure with xwin-clang-cl toolchain (uses clang with MSVC-compatible flags)
XWIN_DIR=~/.xwin cmake -B build_xwin \
  -G Ninja \
  -DCMAKE_BUILD_TYPE=Game__Shipping__Win64 \
  -DCMAKE_TOOLCHAIN_FILE=cmake/toolchains/xwin-clang-cl-toolchain.cmake

# Or use xwin-clang toolchain (uses clang with GNU-style flags)
XWIN_DIR=~/.xwin cmake -B build_xwin \
  -G Ninja \
  -DCMAKE_BUILD_TYPE=Game__Shipping__Win64 \
  -DCMAKE_TOOLCHAIN_FILE=cmake/toolchains/xwin-clang-toolchain.cmake

# Build
cmake --build build_xwin

Building with build.sh Script

# Set XWIN_DIR
export XWIN_DIR=~/.xwin

# Build with xwin-clang-cl
./tools/buildscripts/build.sh --toolchain xwin-clang-cl

# Or build with xwin-clang
./tools/buildscripts/build.sh --toolchain xwin-clang

# Build specific configuration
./tools/buildscripts/build.sh --toolchain xwin-clang-cl --build-config Game__Debug__Win64

# Clean build with verbose output
./tools/buildscripts/build.sh --toolchain xwin-clang-cl --clean --verbose

Option 2: Cross-Compiling with msvc-wine

msvc-wine uses actual MSVC tools running under Wine. This provides maximum compatibility but requires more setup.

Prerequisites

• Wine:

  # On Ubuntu/Debian
  sudo apt install wine wine64 winbind
  
  # On Arch Linux
  sudo pacman -S wine samba
  

• msvc-wine - Follow their installation guide to install MSVC tools
• Clang (for wine-clang-cl mode) or use MSVC's cl.exe (for wine-msvc mode)

Setup

1. Install msvc-wine following the official instructions. By default, this installs to `~