Marie's Adventure Save Files & Backups

Marie’s Adventure is a single-player Windows H-RPG. Your progress lives in local save files, and launch-week players already report load failures and multi-hour lag on a single slot. This page explains how to back up safely before www hotfixes, multiples save-scumming, or Defender restores — without inventing a Cloud feature Steam does not list for app 4819360.

Pair with Troubleshooting, Known Issues, and Controls for F5 / title-load habits.

Steam Cloud: what the store actually lists

Steam public categories for Marie’s Adventure include Single-player, Steam Achievements, and Family Sharing. They do not include Steam Cloud. Until the store page shows a cloud icon (or the developer announces otherwise), assume:

• Saves will not auto-sync between PCs.
• Reinstalling Steam can orphan files if you delete userdata carelessly.
• Manual zip backups are mandatory for serious runs.

If Steam later enables Cloud, re-check this page — we will update Release Notes when metadata changes.

Where to look for save data

RPG Maker–style Windows builds often store slots in one of these places (check all before panicking):

Location pattern	Notes
Game install save / www/save	Common for exported web/RPG Maker packages
%APPDATA% or %LOCALAPPDATA% vendor folders	Survives some reinstalls
Steam userdata\\<SteamID>\\4819360\\	Steam-side storage for app 4819360
Documents / My Games	Less common, still worth searching

On Steam: right-click Marie’s Adventure → Manage → Browse local files to open the install root, then search for recent .rpgsave, .save, or numbered slot files. Exact filenames vary by engine export — copy the entire folder that updates when you save in-game.

Backup checklist (do this weekly)

1. Exit the game completely.
2. Locate the active save folder using the table above.
3. Zip-copy to Desktop\\MariesAdventure-Saves-YYYYMMDD.zip.
4. Keep a second copy on another drive or USB if you hunt multiples.
5. Label slots: story, multiples, altomyostr so you never overwrite the wrong timeline.

Before every www hotfix

Hotfixes overwrite the game directory. Saves usually live outside www, but partial merges and Defender restores have eaten progress before. Sequence:

1. Backup saves (zip).
2. Close the game.
3. Copy hotfix www with full overwrite (Known Issues).
4. Launch, load Sylva save, confirm Inn and pregnancy UI still read correctly.
5. If load fails, restore the zip before trying a second hotfix layer.

Multiples save-scum workflow

Community multiples hunting saves in front of the Sylva Inn clerk after conception. Practical hygiene:

• Dedicated slot — never your only story save.
• Confirm milk capacity with the Pregnancy Tracker after the walk-to-~25% check.
• Reload from title if the engine soft-locks mid-scene (Controls F5 notes).

Load failures and long-session lag

Launch-day Steam threads mention saves that refuse to load and lag after 4–5 hours on one file. Try in order:

1. Restart Windows game client; load from title menu.
2. Copy the corrupt-looking slot aside; test an older backup.
3. Verify Steam files / re-download itch archive if install files were quarantined.
4. Avoid JoiPlay when diagnosing PC load bugs.

Transferring between PCs

Without Cloud:

1. Zip saves on PC A.
2. Install the same storefront build on PC B (Steam vs itch vs DLsite packages can differ).
3. Paste into the matching folder on PC B.
4. If Steam ever shows Cloud later, disable it temporarily while merging folders so remote empty saves do not clobber local progress.

Related pages

• System Requirements — Windows-only install baseline.
• Where to Buy — stay on one storefront for patch parity.
• Achievements — why multiples slots matter.
• Wiki Overview — index.

Backups are boring until the day Defender deletes an exe mid-run. Zip early, label slots, and treat Cloud as unavailable until Steam says otherwise.