BADIDEASCUM / COMMUNITY LAB
SCUM Building Restore · Admin tool

New wipe.
Same home.

Keep the places your community built. Export selected bases before a wipe, then create a new save with those buildings restored.

Download for Windows Read the guide ↗
v0.1.0-test.1 · Windows x64 · 44.9 MB · Portable app
Your choice of basesOne owner, several, or everyone
A separate output fileOriginal saves stay untouched
Works with local filesNo hosting password required
01 / The workflow

Save before. Restore after.

Keep a full backup as well as your building archive. You’ll need access to stop your server and manage its save files.

BEFORE THE WIPE

Archive your buildings.

  1. Stop the server & download the save

    Wait until the server has stopped completely. Download its closed SCUM.db and keep a full, untouched save backup.

  2. Open the restore tool

    Extract the downloaded ZIP and run SCUM-Building-Restore.exe. Choose Open save / archive and select your pre-wipe database.

  3. Choose owners, then bases

    Select one, several or all owners. On the right, check the individual bases you want to keep. A selected base includes its teammates’ building pieces.

  4. Export your selection

    Choose Export selected bases to create a .scumbuild archive. Store it alongside your original backup.

Only keeping a community centre? Select its owner, then leave just that base checked.

AFTER THE WIPE

Build a restored save.

  1. Prepare the new server save

    Let owners create their characters on the new server. Stop it, then download its new SCUM.db.

  2. Open the archive & match players

    Select your bases and choose Restore into a new save. Open the post-wipe database. Review the account-ID matches for every owner and builder.

  3. Review & create the output

    Check the preview and choose a new filename. The tool creates SCUM-restored.db and a JSON report. Existing files are never overwritten.

  4. Test, then upload

    Test on a separate server copy first. When satisfied, stop the destination server and back up its current save. Upload a copy of the output as SCUM.db, start the server and check it in game.

Check structures, doors, flags, colours, ownership, building permissions and shelters before using the restored save live.

02 / What comes with you

Buildings, with clear limits.

This release supports save schema version 73. Source and destination schemas must match.

Included in the archive

  • Completed structural building pieces
  • Colours and patterns
  • Flags and shelter links
  • Original building coordinates
  • Owner mapping to destination players

Not restored by this release

  • Locks and attached item entities
  • Chests and their contents
  • Vehicles, gardens and unfinished blueprints
  • Player progression, money and squads
  • Raid-protection timers and active flag takeovers
03 / Hosting

Your server.
Your save files.

Use the same workflow on your own machine or with a hosting provider such as GGHost.

DOWNLOAD→PROCESS LOCALLY→UPLOAD

You need access to the database.

Your hosting panel, backup tools or SFTP must let you download and replace the server save. In-game admin permissions alone are not enough. If access is restricted, ask hosting support to export and import the file.

The tool runs on your computer and does not connect to your hosting account. GGHost access varies by game; live restoration there has not been tested.

GGHost’s SFTP instructions ↗
04 / If something needs attention

Before you hit restore.

A player is missing after the wipe

Have them create a character on the new server, stop the server and download a fresh save. Alternatively, explicitly map their ownership to another existing player. Every listed owner and builder needs a match. Manual mapping changes ownership; automatic matching uses account IDs, not display names.

The tool reports an active WAL or journal

Use a fully closed server save. Never replace a running server’s database or discard active WAL/journal files to bypass the check. Ask your host for a closed save export if needed.

A base already exists in the destination

Identical geometry with the same base owner is skipped on repeat import. Exact partial overlaps are blocked. The tool does not repair or update existing bases, and it does not evaluate terrain clearance or every possible spatial collision.

The save version or schema is unsupported

This release accepts database version 73 and matching source/destination schemas. A game update may make an older archive incompatible. The tool does not migrate saves, so retain your full original backup.

Something looks wrong after uploading

Stop the server and restore the complete backup you made immediately before uploading. Check server logs and the generated restoration report. Keep experimental restoration on a separate test server until you have verified the result in game.

Can I share an archive publicly?

Keep it private. Building archives contain player account IDs and building positions. The downloadable application and source code do not include your server saves.

05 / Release details

What has been checked.

42DATABASE CHECKS PASSED

Checks cover multiple owners, changed player IDs, shared builders, flags, colours, shelters, repeated imports, overlap rejection, schema checks and unchanged input files.

These used synthetic data with the observed native schema. The real backup used for the read-only loading check contained no bases. Neither establishes in-game compatibility.

The Windows build succeeded. The Wine smoke-test environment could not initialise, so interactive Windows UI operation remains unverified.

Test report ↗SHA-256 checksums ↗Source code ZIP ↓Offline instructions ↓

Start with a backup.

Portable Windows app. .NET included. No installation or admin privileges required.

Download the test release ↓