Where Are Prodeus Save Files Located?
Prodeus splits Unity data into SaveGames, Settings and Maps folders under LocalLow BoundingBoxSoftware, with registry echo and Humble variants.
Last updated
Prodeus divides its Unity footprint three ways. SaveGames for campaigns, Settings for options, Maps for sideloaded and restored content, all under a BoundingBoxSoftware company folder. Registry keys echo the config side.
Store variants rename the company layer. Humble and Microsoft builds write under their own trees with CloudSaveGames in place of SaveGames. Cloud behavior splits between vendor listings and user reports, so local copies stay mandatory.
Where Prodeus stores this, by platform
%USERPROFILE%\AppData\LocalLow\BoundingBoxSoftware\Prodeus\SaveGames
Campaign saves with Settings and Maps siblings under the standard company root. Registry echoes config separately. Humble builds rename the company layer with CloudSaveGames inside.
<SteamLibrary>/steamapps/compatdata/964800/pfx/
Steam Play prefix for App ID 964800. The LocalLow tree mirrors inside the prefix drive. Company-variant split follows the seller on every platform.
Frequently asked questions
How do I back up Prodeus?
Copy the whole %USERPROFILE%\AppData\LocalLow\BoundingBoxSoftware\Prodeus folder with the game closed. Campaign saves, settings and sideloaded maps each hold their own child. Registry keys echo config and travel separately through reg export.
Why is my Prodeus folder named Humble Bundle?
It runs the Humble Bundle tree with CloudSaveGames instead of SaveGames. MS Store builds follow the same rename. Standard Steam and GOG builds use the BoundingBoxSoftware root, so match the tree to the seller.
Does Prodeus use Steam Cloud?
Through its own server per community reports rather than Steam userdata as primary. The vendor lists Cloud support while users describe server-side syncing. Local folder copies remain the dependable backup either way.
Notice an outdated path? Let us know.