Build a Base and Steal private-server risk — the API vs description conflict and the AFK transfer bug

The official description says one thing, the API says another

Build a Base and Steal’s official Roblox description advertises make-a-private-server copy as a feature. Third-party trackers including OP.GG and Rolimons echo that line.

But the Roblox games metadata API (https://games.roblox.com/v1/games/multiget?universeIds=10356701370) returns:

• createVipServersAllowed: false
• maxPlayers: 6
• price: 0

And OP.GG lists VIP Servers: Not Allowed for universe ID 10356701370.

The conflict appears to be a copy/paste artifact in the developer description rather than a runtime difference. Either:

• the developer copy was added in anticipation of a feature that has not yet shipped, or
• the public-server VIP gating was rolled out but the API flag is stale.

Either way, don’t pay for a private server subscription until the developer confirms VIP gating is live in-game. A subscription purchased against a non-functional VIP gate is non-refundable through Roblox standard support.

The AFK transfer bug

Across the steal-sim family (Steal a Brainrot, Build a Base RNG, and the broader base-defense cohort), players report a recurring pattern:

“I queued my private server, went AFK, came back 6 hours later, and my session had been transferred to a public server.”

The transferred session exposes the AFK base to public raids. The bug originates in how Roblox handles session resumption when a player disconnects from a private server whose owner has left — the client often resumes the avatar in the next-available public server rather than failing closed.

Build a Base and Steal may or may not exhibit this bug title-specifically. Until verified, assume the worst case:

• Limit your offline horizon to the 24-hour free cap on a public server.
• If you’re on a private server, manually log out before you go AFK so the next session is a fresh join.
• Use the AFK Income Calculator to model your expected offline cash under the 24h cap and budget your Rebirths around that.

What “safe” looks like today

Until replayable fun games confirms the API-vs-description conflict is resolved, the safest configuration is:

1. No private server subscription. Use the free public server.
2. Collect cash every 24 hours. Don’t trust longer horizons until the AFK transfer bug is ruled out.
3. Park two Common pets at most. Anything you can replace in a single +Luck roll is not worth defending.

If the developer later publishes a confirmed VIP-server workaround, this article will be updated with the verified method.

Sources and verification

What to read next

• AFK Income and Cap — model your offline cash under the 24h free cap.
• Beginner Guide — the wall-first rule and other first-session safeguards.