1:4000 Earth Map for Bedrock: Variant and SMP Guide

Minecraft Bedrock · Scaled Earth world

hf2004z's 1:4000 Earth Map is a Bedrock port of MattiBorchers' Java terrain, built for players who want countries, expeditions, or an Earth-shaped SMP without continent-scale travel times. The source offers several different downloads, so the first decision is not where to found a nation—it is which world variant you are actually importing.

Project lineage and age

The Bedrock page says the port was made with MattiBorchers' permission and that its 1.16 update lines up 1:1 with the Java map. That establishes project lineage and a creator-stated port boundary. It does not give MineBrush a transferable right to host the world or gallery media.

At 1:4000 scale, the terrain is intended as a compressed representation of Earth. Do not turn the scale label into an exact coordinate formula until the specific world confirms its origin, projection, and border. The source does not publish those details in the checked text.

Six route labels are not one download

The project page currently presents:

• Download (1.16 UPDATE)
• Download (RELEASE #4 - NO BORDERS)
• Download (Backup) 1.16
• Coordinate Help
• No structures/creativity - BEES (Download)
• MAP - 1:1 with NO BORDERS, plus a no-borders backup

The visible page does not explain every difference, provide sizes, or identify a universal default. “No borders” may describe a different boundary policy, but it does not tell us what happens when players travel beyond the authored Earth terrain. The bees/creative label is also too compressed to support a clean survival or structures claim.

Before clicking, write down your goal: fixed-territory SMP, unrestricted exploration, creative planning, or historical 1.16 survival. Choose the route whose label most closely matches that goal, then preserve the downloaded filename and size. Never combine level data from two variants.

Compatibility comes before server planning

The creator fields stop at Bedrock 1.16 and 1.14. Modern Bedrock can convert older worlds, but successful import does not prove clean terrain, structures, entities, commands, achievements, or new-chunk behavior.

1. Import on a disposable profile or device with enough free space.
2. Duplicate the result before first load.
3. Record the selected variant, client version, world size, game mode, and any upgrade warning.
4. Load at spawn, save, close the app, and reopen.
5. Travel only a short controlled route before inspecting distant regions.

Use the MineBrush mobile map-import workflow for the backup steps. If the route returns an archive instead of a world file, consult the Bedrock package-format guide rather than renaming it blindly.

Calibrate coordinates with known landmarks

An Earth SMP needs a shared location model. Pick three or more easily recognizable landmarks on different continents and record their in-game coordinates. Use those observations to determine orientation, approximate scale, and whether the coordinate-help route corresponds to your exact variant.

Do not publish a capital-city coordinate copied from another edition until you visit it. Border/no-border worlds and port revisions may shift spawn or terrain. A community coordinate table should include variant label, Bedrock version, observation date, and the player's measurement method.

Test the edge before writing SMP rules

On a copied world, approach one expected boundary in Creative mode and record what happens: hard stop, void, ocean, authored continuation, or newly generated vanilla chunks. Return to the same place after a save/reopen. This test defines whether an “Earth-only” rule can be enforced by terrain or must be enforced socially.

If normal chunks generate outside the mapped area, exploration can enlarge the save and create land that defeats a geopolitical boundary. Do not test every edge on the production world; new chunks may be permanent.

Storage and load-time benchmark

The source does not display download size, extracted size, or free-space requirement. Measure rather than guessing:

1. Record the package size before import.
2. Measure the imported world folder or device storage change.
3. Time the first launch, second launch, and a load at a distant landmark.
4. Travel a fixed route using identical render and simulation distance.
5. Export after the route and compare world growth.

On mobile, also note heat, battery loss, frame drops, and delayed chunk display. On a hosted session, separate upload time from server startup and player join time. A huge download is not guaranteed, but an Earth map deserves an evidence-based capacity check.

Build a fair Earth SMP ruleset

The map supplies terrain, not governance. Decide the following before settlement:

• How claims are measured and whether coastlines, islands, and canals count.
• Whether players can settle unclaimed land outside the authored Earth area.
• How spawn protection, travel hubs, portals, and shared oceans work.
• Whether structures are regenerated, manually supplied, or unavailable.
• What happens to abandoned nations and offline players.
• Which map tools, coordinate sharing, and teleport commands are allowed.

Test survival resources before allocating countries. A terrain port may not provide modern structures, ores, biomes, or loot in the same way as a newly generated 26.x world. Do not promise balanced nations until representative regions are surveyed.

Realm and dedicated-server gate

The page makes no current Realm, server, cross-play, or player-capacity claim. First prove a local host with one joining client. Compare spawn, coordinates, terrain, inventory, block edits, sleep, portals, and reconnect behavior.

For a Realm, verify that the actual imported world fits current upload constraints and survives download/reupload. For a dedicated server, confirm the platform accepts the converted database and does not generate a fresh seed. Preserve the original and local converted exports before either move.

Structures and modern content are separate questions

One route label mentions “No structures/creativity - BEES,” but its meaning is not fully explained. The 1.16/1.14 tags also predate many modern Bedrock blocks, mobs, and generation systems. Inspect the chosen world before deciding whether structures, bees, villages, monuments, or dimensions are present.

Adding structure packs or world-generation add-ons later can create seams or modify newly generated chunks without repairing authored terrain. Test them on a copy and state exactly which regions were loaded before activation.

Failures and first responses

Rights and file-history boundary

hf2004z says MattiBorchers permitted the Bedrock port. That statement is not a license for MineBrush to mirror either edition, modify the world, or reuse creator screenshots. Players are routed to the Bedrock port page and the original Java project for attribution.

No matching Earth world or original MineBrush capture was found locally. The existing MineBrush cover is editorial artwork rather than map evidence, so the private DLE history allowlist remains empty.

Primary sources

• hf2004z 1:4000 Bedrock port
• MattiBorchers original Java project

Both project records were checked August 25, 2026. The guide preserves the historical 1.16/1.14 ceiling and does not claim a modern Bedrock, Realm, or performance result.

Browse more large worlds in the Minecraft maps hub.