Turn real places into playable Minecraft worlds

Search for a real place by name, address, landmark or current location and choose the area. We read public map data (building footprints, roads, waterways, terrain) and generate a world you can import into Minecraft. The full flow is: search a place → choose the area and spawn point → choose a gameplay template and output format → review the free map quality report → view a free low-resolution 3D preview → see the final price and estimated time → purchase → generate in the cloud (with real-time progress) → structure validation → result report → save, open in Minecraft, or deploy to a server.

Because you shouldn't pay for an unknown outcome. Map data quality varies a lot from place to place, so before charging anything we show you building, road, waterway and terrain coverage and give a clear "good to generate / adjustments suggested / not recommended" verdict. The free low-resolution 3D preview lets you rotate, look top-down, and toggle layers and day/night. The quality score is an estimate of data coverage, not a guarantee of accuracy; the preview is low-resolution and not a block-for-block copy of the final result.

Diagnosis is free; you only pay—based on the area, complexity and output format you choose—after you've confirmed the result, with an automatic refund on failure. The price confirmed at checkout doesn't change after purchase. Exact prices are shown on the in-app purchase page for your region—the in-app price is authoritative.

Usually, yes. A very common problem is a world wrapped in an extra folder, so Minecraft can't find level.dat at the root of the archive. This kind of simple structural repair is free and produces a new .mcworld. More complex corruption is handled per-job by "Advanced repair"; before you pay, we show you the specific issues, the probability of success, the expected output, the risks and the refund policy.

No. A repair always produces a new output file; your original file stays unchanged along with its hash, so the result is fully traceable. "Zero accidental overwrites" is our release red line—it's our bottom line, not marketing speak.

Yes. Java Edition → Bedrock conversion outputs an importable .mcworld. Before you pay, we show you the compatibility score, what migrates intact (terrain, blocks, containers, structures), and what may need to be replaced.

No, and we never promise it is. Java Edition and Bedrock are different formats. Some Java-only entities, blocks, behavior packs, resource packs, redstone behaviors or player data may be replaced with compatible equivalents, or moved into a separate report rather than written into the world. We show you the compatibility score up front and, once finished, give you an item-by-item readable report of exactly what was replaced or changed—no surprises.

"Monitoring only" is free and needs just the server address and port; it shows online status, version, player count and latency, and provides basic offline alerts for a single server. It doesn't read your world directory and has no write access. "Full management" (paid) requires you to explicitly authorize the connection method and world directory, adding remote snapshots, restorability verification, safe deployment, automatic health checks, one-tap rollback, resource-pack sync and an operation log. You can revoke authorization at any time.

A failed job is automatically refunded (or your credits are returned)—you never pay for a failed result. We keep the failure report and a retry option. A failed generation doesn't consume credits.

All in-app digital features are billed through Apple StoreKit. Purchases can be restored across devices, and consumable credits don't expire for no reason. Subscriptions are managed in your Apple ID settings: "Settings → your name → Subscriptions" lets you cancel at any time, after which you keep access through the end of the current paid period.