Voxel Block Builder Personal Worlds Save Checklist

Personal Worlds are the difference between a disposable sandbox and a lasting Voxel Block Builder portfolio. This World Save Checklist helps you treat saves like a studio habit: confirm you are in the right world, checkpoint after risky edits, verify the world still loads, and document what changed. It pairs with the Build Checklist and assumes you prefer official Passes over unauthorized automation.

Goober Labs positions Personal Worlds as the feature for keeping creations. Public servers are great for social energy; they are a poor vault. If a build matters, it belongs in a Personal World—and that world deserves a closing ritual every session.

Why saves fail in practice

Players rarely lose work because the feature “does not exist.” They lose work because:

• They built on a public server and expected persistence that was never promised.
• They terraformed with Bombastic Pickaxe for an hour and disconnected mid-action without a mental checkpoint.
• They tested a weekly block update directly on the showcase plot.
• They trusted a third-party auto-place / auto-mine claim that desynced placement (Script Safety).
• They owned multiple worlds / plots in their head but saved the wrong one.

This checklist attacks those failure modes one by one.

A. Pre-flight (before you place or mine)

1. Launch from the official experience via Official Links.
2. Confirm you entered the intended Personal World, not a random public server.
3. Stand still and look for landmarks you recognize from last session.
4. If anything looks rolled back or empty, stop digging—verify you opened the correct world before “fixing” anything.
5. Screenshot the spawn approach and the current skyline; these images are your poor-man’s version history.
6. Read Updates on patch days before editing crown-jewel plots.
7. Decide whether tonight is a destructive session (terraforming) or a constructive session (new wings). Avoid mixing both without a midpoint save pause.

B. Mid-session checkpoints

Set a timer if you must. Every 15–20 minutes—or after each completed wing:

1. Holster the pickaxe.
2. Walk a full loop around new geometry to confirm it is what you meant.
3. Trigger / confirm the Personal World save behavior the game provides (use the in-experience save/exit flows—do not rely on rumor macros).
4. Wait for any save confirmation UI or safe-exit pattern you recognize from prior successful sessions.
5. Take a fresh screenshot from the same camera angle as your pre-flight shot.
6. Only then start the next risky carve with Bombastic Pickaxe or a large demolition.

If Fly or 2x Sprint are active, remember movement speed makes it easier to accidentally wander into demolition zones—slow down near finished façades.

C. High-risk operations protocol

Run this mini-list before:

• Flattening a hill that supports existing builds
• Flooding an area for lakes or canals
• Recoloring an entire district with Rainbow Block Pack experiments
• Replacing structural walls with Colored Glass
• Trying Blue Dimension sessions that change how you navigate space
• Testing unverified community advice from Working Scripts overview feature claims (spoiler: skip the scripts; keep the Passes)

Protocol:

1. Checkpoint save + screenshot.
2. Perform the risky edit on a corner sample first.
3. Evaluate.
4. Checkpoint again.
5. Scale the edit to the full region only after the sample works.

D. End-of-session verification

Do not alt-f4 the moment you feel done.

1. Complete the current wall seam or clearly mark incompletes with a temporary block color.
2. Unequip destructive tools.
3. Save / exit using the normal Personal Worlds flow.
4. Optionally rejoin the same Personal World immediately to verify the skyline matches your last screenshot.
5. If verification fails, stop and note the time—do not rebuild blindly over a possible sync delay without checking Updates or retrying a clean join.
6. Store screenshots in a local folder named by date and project (“2026-08-13-greenhouse”).
7. Write next session’s first action in the screenshot filename or a note.

E. Multiplayer and sharing caution

• Agree who owns the Personal World before collaborating.
• Do not share passwords so friends can “save for you.”
• If you host, watch for grief-sized pickaxe swings near finished districts.
• After friends leave, run the end-of-session verification yourself.

F. Update-day variant

When weekly blocks or Verity Pets content ships:

1. Skim Updates and Items.
2. Open a secondary Personal World or a disposable corner as a lab.
3. Test new blocks, pet behavior, and Pass interactions there.
4. Only migrate successful ideas to the main showcase world.
5. Run full end-of-session verification on both worlds if you touched both.

G. Recovery mindset (if something looks wrong)

1. Do not spam place/mine hoping to force a refresh.
2. Rejoin once cleanly.
3. Compare against screenshots.
4. Check whether you entered a different world or a public server.
5. Avoid shady “restore tools” advertised as scripts—they are often stealers.
6. Rebuild from the last known good screenshot using the Build Checklist.

H. Habit stack with the rest of the wiki

• Plan the session with Build Checklist.
• Track rewards on Codes (often zero active codes—still worth a glance).
• Rank Pass purchases on Tier List.
• Learn mechanics in Guides.
• Prefer Passes over injectors via Scripts Hub.
• Confirm destinations on Links.

Quick card (memorize)

Enter correct Personal World → screenshot → edit → checkpoint → screenshot → verify rejoin → note next step.

That single card prevents more heartbreak than any circulating auto-save myth.

Personal Worlds make Voxel Block Builder a long-term creative hobby instead of a coin-flip public lobby. Treat saves with the same respect you give limited blocks and Verity companions. Run this checklist until it feels automatic, and your future cities will still be waiting after the next weekly drop.