Help Center

Search for a real place by name, address, landmark, or your current location, then pick an area. We read public map data — building footprints, roads, water, and terrain — and turn it into a world you can import.

The full flow: search a place → choose the area and spawn point → pick a gameplay template and output format → review the free map quality report → explore the free low-resolution 3D preview → see the final price and estimated time → purchase → generate in the cloud (with live progress) → structure validation → results report → save it to your world library, open it in Minecraft, or deploy it to a server.

Because you shouldn't pay for an unknown outcome. Map data quality varies enormously from place to place, so before charging anything we show you the building, road, water, and terrain coverage, with a clear verdict: 'good to generate', 'consider adjusting', or 'not recommended'.

The free low-resolution 3D preview lets you rotate, look down from above, toggle layers, and switch between day and night, so you can judge the result before you buy. The quality score is an estimate of data coverage, not a guarantee of accuracy; the preview is low-resolution, not a block-by-block copy of the finished world.

Pricing varies with the area you select, the generation complexity, and the output format, across 6 area tiers (from a neighborhood of about 0.2 km² up to a regional scale of about 500 km²). Diagnostics are free, you pay only after you've reviewed the result, and failures are refunded automatically; the price confirmed at checkout doesn't change after purchase. Exact prices are shown in the app.

You can open .mcworld, .zip, .mctemplate, .mcpack, and .mcaddon files, as well as Java Edition world ZIPs. The app copies the file into its sandbox and scans it on your device — free diagnostics, no upload required.

Usually, yes. One very common problem is a world wrapped in an extra folder, which leaves Minecraft unable to find level.dat at the root of the archive. This kind of simple structural fix is free, and it produces a new .mcworld.

More complex corruption is handled by Advanced Repair on a per-use basis. Before you pay, we show you the specific problem, the likelihood of success, the expected output, the risks, and the refund policy. Prices are shown in the app.

No. A repair always produces a new output file; your original stays unchanged, hash and all, so the result is fully traceable. 'Zero accidental overwrites' is a release red line for us — it's a product guarantee, not marketing.

Yes. Java Edition → Bedrock conversion is paid per use and outputs an importable .mcworld. Before you pay, we show you a compatibility score, what migrates cleanly (terrain, blocks, containers, structures), and what may need to be replaced. Prices are shown in the app.

No — and we never claim it is. Java Edition and Bedrock are different formats. Some Java-only entities, blocks, behavior packs, resource packs, redstone behavior, or player data may be swapped for compatible equivalents, or moved into a separate report instead of written into the world.

We show you the compatibility score up front and give you a readable, item-by-item report once it's done, explaining exactly what was replaced or changed — no surprises. The conversion feature carries a Beta label where appropriate.

You can create manual local snapshots; with a World Pro subscription you also get automatic cloud backups with version history. Every snapshot records its hash, size, source, and reason. Restoring creates a new copy by default — it never overwrites your current world. Cloud backups are verified for readability after upload.

It shrinks the file size without deleting important regions, paid per use. Before processing it estimates how much space you'll save, lets you preview the scope of the slimming, and creates a snapshot so the changes are reversible. Prices are shown in the app.

Monitoring only is free and needs just a server address and port. It shows online status, version, player count, and latency, plus 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 a connection method and world directory. It adds remote snapshots, restorability verification, safe deployment, automatic health checks, one-tap rollback, resource pack sync, and an operation log. You can revoke access at any time.

Deployment runs in a fixed order: version and space pre-checks → create a remote snapshot → verify the snapshot can be restored → upload to an isolated directory → validate the hash and world structure → atomically switch the active world → run a server health check. If the health check fails, it rolls back automatically and writes an incident report. Your pre-deployment snapshot is always kept as a rollback point.

Your first full-management connection includes a free 'snapshot restorability' verification, so you can confirm that restore actually works before you subscribe.

Yes. Credentials are stored in the iOS Keychain or an encrypted credential vault, and never appear in the interface, logs, crash reports, or analytics. You can revoke them at any time. We will never ask you to share a server password through an insecure channel.

A failed job is refunded automatically (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 use Apple StoreKit. Purchases can be restored across your devices, and consumable credits don't expire for no reason. Subscriptions are managed in your Apple ID settings: go to Settings → your name → Subscriptions to cancel at any time.

Data-loss tickets are our highest priority. Contact support via the in-app link and include the job ID, and we'll help — including providing the input/output hashes and processing report for the affected job. If a world's version genuinely isn't supported, we'll never falsely claim it was 'fixed'.