Skip to content

README.md

Latest commit

 

History

History
72 lines (54 loc) · 3.77 KB

README.md

File metadata and controls

72 lines (54 loc) · 3.77 KB
Raw

Splitgate Internal

C++ internal library and launcher for Splitgate (UE4): injected overlay menu with exploits, cheats, qol gameplay features, and Python scripting.

Preview

In-game menu Overlay in-game

Usage

• Build the project or download the latest precompiled binaries from here

• Make sure Launcher.exe and Internal.dll in the same folder

• Have a Python 3.x installed (the same version the DLL was built against — e.g. python314.dll for a Python 3.14 build). The embedded interpreter loads it from the install and finds its standard library there. Do not copy python3XY.dll next to Internal.dll or into the game folder — that makes Python look for its stdlib in the wrong place ("Could not find platform independent libraries").

• Start the game

• Open Launcher.exe

• Use the Ins button to show/hide the gui

Compile

To compile the project make sure you have Visual Studio 22, vcpkg integrated with MSBuild and any Python 3.x installed

Important

Internal embeds Python (via pybind11 + <Python.h>), so a Python 3.x installation is required to compile.

Internal/python.props auto-detects the newest 64-bit Python installed under C:\Python3XY or recorded by the official installer in the registry (which covers per-user and all-user installs in any folder) — no configuration needed for a default install. Internal is an x64 build, so a 64-bit Python is required.

If Python is installed somewhere custom that isn't picked up, set the SPLITGATE_PYTHON_DIR environment variable to your Python root (the folder containing include\ and libs\), or pass /p:PythonRoot=<dir> to MSBuild. Whichever version is selected must match the python3XY.dll present at runtime.

  • Install Internal dependencies: 
    cd Internal
vcpkg install
  • Compile using Visual Studio

Documentation

  • Settings — configuration structs, persistence, file location
  • Features — the feature framework and how to add one
  • Hooking — injection and how the game's functions are hooked
  • Debugging — reading logs, the in-game console, and crash stack traces
  • Game dump — the Dumpspace SDK dump for Splitgate (offsets, JSON schema)
  • Backend redirect — routing the game to a private server (+ early injection)
  • Scripting — embedding Python and writing user scripts
  • Testing — the gtest project and how to run it
  • Style & linting — clang-format / clang-tidy setup
  • UE4 cheatsheet — living RE reference: key objects, offsets, and snippets

Credits

Inspiration and references: