Carnal Instinct Cheats: Console Commands, Save Paths, and Quick Keys
Carnal Instinct runs on Unreal Engine, which means its console, save format, and memory structure follow Epic's standard blueprint. The developer, Team Carnal Instinct, left the UE developer console accessible in most release builds, and the .sav files are standard Unreal serialized archives that can be backed up, replaced, or shared without proprietary tools.
The game has also migrated engines during Early Access — from UE4 to UE5 — which split the save file locations and changed the internal executable name. Players on older builds find data in one folder; players on current UE5 builds find it in another. This guide covers both paths, the console activation, verified native commands, and why old saves from before version 0.1.5 are considered toxic.
How to Open the Developer Console
Press the ~ (tilde) key during gameplay. A command line drops down from the top of the screen. The console accepts standard Unreal Engine commands, though not all native cheats function identically in modified engine builds.
If the tilde key does not respond, the likely causes are:
- The keyboard layout maps tilde to a different physical key (common on non-US layouts).
- The game build has console access disabled via a launch flag.
- The player is in a menu or loading screen where input is captured by the UI layer.
Verified Console Commands
Community testing confirms the following Unreal native commands function in current builds. Results vary by patch, so players should test on a dummy save first.
| Command | Effect | Status |
|---|---|---|
| god | Toggles invincibility. The player takes no damage from enemies or environmental hazards. | Confirmed on most builds |
| fly | Enables free flight. The player can move vertically and bypass terrain obstacles. | Confirmed on most builds |
| ghost | Enables noclip. The player passes through walls, floors, and collision boundaries. | Confirmed on most builds |
| walk | Disables fly and ghost, returning movement to normal grounded physics. | Confirmed on most builds |
Other standard UE commands such as slomo, fov, and showcollision may also function, but community verification is sparse. The game is built on a modified engine branch, so some native cheats are stripped or altered.
Quick Save and Quick Load
The game supports hard-coded quick save and quick load keys that bypass the menu entirely:
- P — Quick save
- O — Quick load
These are not rebindable through the in-game settings and function at any time during gameplay except during cutscenes or dialogue sequences where input is restricted.
Save File Locations: The UE4 vs. UE5 Split
Because Carnal Instinct transitioned from Unreal Engine 4 to Unreal Engine 5 during Early Access, the save folder path depends on which engine version the current build uses. The game does not migrate saves automatically between these folders.
| Engine Version | Path |
|---|---|
| UE4 (Legacy) | %LOCALAPPDATA%\Carnal_Instinct\Saved\SaveGames |
| UE5 (Current) | %LOCALAPPDATA%\Carnal_Instinct_UE5\Saved\SaveGames |
| Alternative (Some Standalone Builds) | %USERPROFILE%\AppData\Local\CarnalInstinct\Saved\SaveGames |
To reach these folders quickly, press Windows Key + R, type %localappdata%, and navigate to the appropriate subfolder. The AppData directory is hidden by default in Windows, so manual navigation from File Explorer requires enabling "Hidden items" in the View tab.
Inside the SaveGames folder, files follow Unreal's standard naming convention: SaveGame_0.sav, SaveGame_1.sav, and so on. Slot 0 corresponds to the first manual save slot in the game's load menu. The game also maintains an auto-save file that overwrites independently of manual slots.
Community Save Files
For players who want to skip progression entirely, community archives distribute 100% completed .sav files. These typically include maxed character stats, all abilities, all items, and unlocked gallery content. Installation requires extracting the downloaded .sav into the SaveGames folder and ensuring the filename matches an empty slot (for example, renaming to SaveGame_1.sav for slot 2).
Because the game uses Unreal's serialized save format, these files are not human-readable and cannot be edited with a text editor. Hex editing is theoretically possible but impractical without knowledge of the specific struct layout for that build.
The Old Save Problem
The developer has explicitly warned that saves from prior to version 0.1.5 are not recommended and may cause serious game-breaking bugs. During Early Access, the team regularly updates SaveGame objects and interactables, which renders older serialized data incompatible with newer code. If a player loads a pre-0.1.5 save into a current build, common symptoms include missing quest items, broken NPC interactions, and infinite loading screens.
The only fix is to start a new save file. There is no migration tool or save converter. Players returning after a long hiatus should treat current builds as fresh starts.
Honest Warnings
- Back up the entire SaveGames folder before installing community saves. Overwriting a slot destroys the original progress permanently. Copy the folder to the Desktop or an external drive first.
- UE4 saves do not work in UE5 builds. If the game was updated from UE4 to UE5, the old save folder is orphaned. The game reads from the new Carnal_Instinct_UE5 path and ignores the legacy folder entirely.
- Console commands are inconsistent. Unreal native cheats like god and fly are not guaranteed to function on every patch. Some builds have them disabled or partially stripped. Test on a throwaway save before relying on them in a main playthrough.
- Steam Cloud can conflict with manual saves. If Steam Cloud is enabled, it may overwrite a manually installed community save file on next launch. Disable Steam Cloud for Carnal Instinct in the Steam library properties before importing external saves.
- Quick save does not create a new slot. The P key overwrites the current quick save buffer. It is not a substitute for manual save rotation.
Frequently Asked Questions
Do console commands disable achievements?
No. Carnal Instinct is a single-player title with no anti-cheat layer. Steam achievements unlock normally regardless of console use or save file imports.
Why does the console not open?
Most common causes: the keyboard layout lacks a direct tilde key (try ` or ö on European layouts), the build has console access disabled, or the player is in a menu state that captures all keyboard input. There is no alternative activation method if the tilde key is hard-disabled in the build.
Can saves be transferred between PCs?
Yes. Copy the entire SaveGames folder from the source machine and paste it into the identical path on the target. Ensure both machines are running the same engine version (UE4 or UE5) and the same game patch.
Why does the game crash when loading an old save?
Version mismatch. Saves from before 0.1.5 or from a different engine generation contain serialized data that the current build cannot parse. Start a new game.
Is there a way to edit stats without console commands?
Not practically. The .sav format is a binary Unreal archive. Text editing is impossible, and hex editing requires knowledge of the specific struct offsets for that build. The console commands god and fly are the only widely reported methods for altering gameplay state.
Does the game support Steam Cloud?
Yes, on current builds. However, Steam Cloud can overwrite manually imported saves. Players installing community saves should disable cloud sync for Carnal Instinct in Steam properties to prevent automatic reversion.
Bottom Line
Carnal Instinct's Unreal Engine foundation makes it a different beast from the typical Ren'Py or Unity title. The tilde console is there but unreliable, the save files shifted folders when the game jumped from UE4 to UE5, and old saves are actively toxic to current builds. For guaranteed results, god and fly are the safest console bets — when they work. For instant progression, community .sav files drop into the SaveGames folder. Just remember to disable Steam Cloud first, back up the originals, and never load a save older than version 0.1.5.
