RPG Maker is one of the most widely supported engine families. The save format depends on the version:

Finding Save Files

RPG Maker MV / MZ (Windows):

• Inside the game folder: [GameFolder]/www/save/ or [GameFolder]/save/

• Files named file1.rpgsave, file2.rpgsave, etc.

• Some games store saves in %APPDATA%/[GameName]/

RPG Maker MV / MZ (Mac):

• ~/Library/Application Support/[GameName]/

• Or right-click the app → "Show Package Contents" → Contents/Resources/app.nw/save/

RPG Maker VX Ace / VX:

• Usually in [GameFolder]/Save/

• Files named Save01.rvdata2 (VX Ace) or Save01.rvdata (VX)

RPG Maker XP:

• Inside the game root directory under a folder named Save/

• Files named SaveXX.rxdata

RPG Maker 2000/2003:

• Files have .lsd extension

• Location varies by game

What You Can Edit

After uploading your save, you'll see a tree structure. Common keys to search for:

• party._gold or gold — Your currency

• party._items — Inventory items (add item IDs and quantities)

• _actors — Character stats. Look for _level, _exp, _paramPlus (attack, defense, etc.)

• variables — Story flags, relationship values, progress markers

• switches — Boolean game flags

Pro tip: Use the search bar in the editor to find "gold" or your character's name quickly.

Important: RPG Maker MV/MZ saves are Base64-encoded JSON. The online editor handles decoding automatically. If you try to edit manually, you'll need to Base64 decode, then LZString decompress (for MV), edit the JSON, then reverse the process.

Limitations: Some games encrypt their saves with a developer-specific key. If the editor shows "Failed to parse," encryption may be the cause.

Ren'Py is a visual novel engine that uses Python's pickle system to save game state.

Finding Save Files

Windows:

• %APPDATA%/RenPy/[GameName]/

• The %APPDATA% folder is typically C:\Users\[YourName]\AppData\Roaming\

Mac:

• ~/Library/RenPy/[GameName]/

Linux:

• ~/.renpy/[GameName]/

Android:

• /data/data/[package.name]/files/saves/ (requires root or ADB access)

What You Can Edit

Ren'Py saves contain:

• Basic types: integers, strings, floats, booleans

• Compound types: lists, tuples, sets, dictionaries

• Creator-defined objects

The editor scans for variables and displays them. Look for:

• Money/gold/credits — Usually a simple integer

• Relationship values — Often named after characters

• Story flags — Booleans or integers tracking progress

Warning: Only edit values you recognize. Ren'Py saves can contain complex object references, and modifying the wrong thing can corrupt your save or cause the game to crash.

Persistent data: Ren'Py also stores "persistent" data (unlocked galleries, endings seen) separately. These may not appear in regular save files.

Unity games are the most varied when it comes to save formats. There's no single standard.

Common Save Methods

1. PlayerPrefs — Key-value storage (Registry on Windows, XML files on Android/iOS)

2. JSON files — Human-readable, easy to edit

3. XML files — Structured text, common on mobile

4. Binary files — Custom serialized data (harder to edit)

5. Easy Save 2/3 (.es3) — Popular Unity asset store plugin

Finding Save Files

Windows:

• PlayerPrefs (Registry): HKEY_CURRENT_USER\Software\[CompanyName]\[ProductName]

• File-based saves: %USERPROFILE%\AppData\LocalLow\[CompanyName]\[ProductName]\

• Steam Cloud: %ProgramFiles(x86)%\Steam\userdata\[YourSteamID]\[AppID]\remote\

Mac:

• ~/Library/Application Support/[CompanyName]/[ProductName]/

• ~/Library/Preferences/

Linux:

• ~/.config/unity3d/[CompanyName]/[ProductName]/

Android (rooted):

• /data/data/[package.name]/shared_prefs/ (PlayerPrefs XML files)

Android (non-rooted with ADB):

• Use adb backup and extract with android-backup-extractor

iOS:

• App's Documents folder (accessible via iTunes file sharing or third-party tools)

What You Can Edit

For PlayerPrefs XML files, you'll see entries like:

• Coins or Gold — Integer values

• PlayerLevel — Integer

• UnlockedLevels — Often comma-separated strings

• SoundEnabled — 0 or 1

For JSON saves, you'll see a structured tree. Look for fields like inventory, stats, playerData, currency.

Complex data: Some games store serialized JSON as a string inside a single PlayerPrefs key. Copy that string into a JSON formatter, edit it, then paste it back.

Binary formats: If the file is binary/encrypted, the editor may display raw data or be unable to parse it. Games with custom encryption or checksums are harder to modify.

Unreal Engine games typically use the GVAS (Game Variable Archive Serializer) format.

Finding Save Files

Windows (packaged games):

• %LocalAppData%\[ProjectName]\Saved\SaveGames\

• The full path is usually C:\Users\[YourName]\AppData\Local\[ProjectName]\Saved\SaveGames\

Windows (in-editor):

• [ProjectFolder]/Saved/SaveGames/

Mac:

• ~/Library/Application Support/Epic/[ProjectName]/Saved/SaveGames/

Linux:

• ~/.config/Epic/[ProjectName]/Saved/SaveGames/

What You Can Edit

UE saves contain string, int, long, float, double, and bool variables. Common names:

• Money, Gold, Currency

• Items — Inventory arrays

• Stats — Health, level, XP

• bUnlocked[Something] — Boolean flags (UE naming convention)

Note: UE4 and UE5 use compatible save formats . A save from UE4 can generally be edited with the same tools as UE5, though the project name in the path may differ.

Godot is less standardized than Unity or Unreal. Save formats vary widely.

Finding Save Files

Windows:

• %APPDATA%/Godot/app_userdata/[ProjectName]/

• The full path is C:\Users\[YourName]\AppData\Roaming\Godot\app_userdata\[ProjectName]\

Mac:

• ~/Library/Application Support/Godot/app_userdata/[ProjectName]/

Linux:

• ~/.local/share/godot/app_userdata/[ProjectName]/

Common Formats

• .tres — Godot text resource file (human-readable, editable in a text editor)

• .res — Binary resource file

• .cfg / .ini — Configuration files (often for settings)

• .json — If the developer chose JSON serialization

• .save — Custom binary (varies by game)

What You Can Edit

For .tres files (text resources), you can often edit them directly in a text editor. Look for variables like:

• skill_points — Integer

• character_name — String

• skills — Dictionary of unlocked abilities (change 0 to 1 to unlock)

• gold / money — Currency

Example: In one Godot game, the save file contained "skill_points": 0 and a skills dictionary with entries like "strength": 0. Changing these values in a text editor worked directly.

For binary .save files, use the online editor. Godot's binary format uses FileAccess methods like get_var() and store_var(), which the editor can parse.