Easy To Use Command Line Modding Utility For Unreal Engine Games 4.0-5.7
Automates creation, and placement, of mod archives, and other various actions.
example.mp4
- Supports Unreal Engine versions: 4.0-5.7
- Supports loose file modding (unreal assets, not in a mod archive, like a .pak)
- Supports modding iostore games
- Automatic mod creation and placement
- Automatic engine cooking, and packaging
- Automatic game running
- Automatic editor running
- Event management system
- Process management events
- Window management events
- Automatic script/exec running events
- Supports creation of mod archives, through unreal_pak, repak, and engine made archives
- Ability to add launch params to various script/exec running
- Supports games with alternative packing structures (example game: Kingdom Hearts 3)
- Supports packing edited files, through the persistent_files dir, or through the Event Management System
- Easily configure what files end up in your final mod(s) and how with the Mod list within the config
- Supports loading from json file, so you can have multiple projects easily
- Logging
- Colorful printouts
- Ability to run in the background, with no windows
- And more...
Tempo is distributed as a single package, tempo-cli, which relies on tempo-core.
# With pip.
pip install git+https://www.github.com/tempo-cli# Or pipx.
pipx install git+https://www.github.com/tempo-cli# Or uv.
uv add git+https://www.github.com/tempo-cliIf you prefer prebuilt executables, downloads are available for Windows and Linux in the Releases section:
- Windows:
tempo_cli.exe - Linux:
tempo_cli
For a step-by-step guide on setting up and using tempo-cli, check out the Getting Started Guide.
tempo-cli's documentation is available at tempo-organization.github.io/tempo-cli.
Additionally, the command line reference documentation can be viewed with tempo_cli --help.
If you encounter a bug or issue, please submit a report on the issues page.
When creating an issue, please provide as much information as possible, including:
- Steps to reproduce the issue
- What you expect to happen, versus what is happening
- Any error messages or logs
- Your system operating system
Contributions are always appreciated, but please keep in mind the following:
- Before coding new features, try to make an issue to see if the idea/implementation needs any tweaking, or is out of scope
- Make sure your changes pass all pre-commit checks
Currently we support Windows (x86-64 and i686) and Linux (x86-64 and aarch64).
Yes, the license fully allows this, and we would love to see it.
tempo-cli relies on these tools from the community to provide it's full functionality.
- Jmap - Unreal Engine reflection data format and extractor
- Repak - Unreal Engine .pak file library and CLI in rust
- Retoc - Unreal Engine IoStore CLI packing/unpacking tool
- UE4SS - Injectable LUA scripting system, SDK generator, live property editor and other dumping utilities for UE4/5 games
- Patternsleuth - Unreal Engine address scanner and test suite
- Umodel - Viewer and exporter for Unreal Engine 1-4 assets (UE Viewer)
- Stove - an editor for cooked unreal engine 4/5 maps
- Spaghetti - a function hooker for cooked unreal engine blueprints
- Fmodel - Unreal Engine Archives Explorer
- Kismet Analyzer - Unreal Engine blueprint/kismet script reverse engineering and modding utilities
- UAssetGUI - A tool designed for low-level examination and modification of Unreal Engine game assets by hand
- Suzie - Unreal Engine Editor runtime class generation from dumped game reflection data
- Commitizen - Create committing rules for projects, auto bump versions, and auto changelog generation
tempo-cli is licensed under
- GNU General Public License version 3 (LICENSE or https://opensource.org/license/gpl-3-0)
Unless you explicitly state otherwise, any contribution intentionally submitted for inclusion in tempo-cli
by you, as defined in the GNU General Public License version 3, shall be licensed as above, without any
additional terms or conditions.
