Will It Host? / Google Earth Pro
Can you run a Minecraft server in Google Earth?
Not inside it. Google Earth cannot run code, so this is the one episode where the application is not the process on port 25565. The server is a standalone Go binary and Google Earth is its second client: every block you place lands on the real planet at the coordinates you are standing on, and Earth draws it within two seconds.
How it works
Google Earth Pro has no plugins and no scripting runtime, but it will fetch a KML network link on a timer. The server hands it a link to its own live endpoint with a two second refresh, and each fetch returns the whole world. Spawn is anchored to a real wonder at one metre per block, a local tangent plane conversion turns Minecraft positions in to latitude and longitude, and every block is reverse geocoded offline so chat tells you which city and country it landed in.
The part that nearly stopped it
There was no host to get inside. Every other episode is about persuading an application to hold a socket, and Google Earth only ever makes outbound requests, which also means nothing done in Earth can reach Minecraft.
What got it over the line
Making Earth the client. After that the work was geography: 242 country borders and 10,567 cities embedded in the binary, a point in polygon test that handles holes so Lesotho does not come back as South Africa, and the seven wonders built at their real coordinates so /warp can take you from Giza to Rome and the blocks you place there land in Italy.
What it cannot do
Minecraft 1.8.9, the same target as the rest of the series. One way only, from Minecraft to Earth. One player, a world sixteen blocks tall, and nothing is saved. It needs Google Earth Pro on desktop, which Google stops offering as a new download on 25 June 2027.
Why this is possible at all
A Minecraft Java server is a smaller thing than its reputation suggests. It is a socket, a packet codec and a game loop. The client opens one TCP connection, sends a handshake naming its protocol version, moves through login into the play state, and from then on both sides exchange length-prefixed packets describing chunks, entities and movement. None of that needs a game engine. It needs something that can hold a socket open and put the right bytes on it in the right order, which is why Google Earth Pro can be made to do it. In every episode the host is the hard part.
Every build in this series targets Minecraft 1.8.9 for one specific reason. In 1.8 a chunk is a flat byte array you can send uncompressed. From 1.9 onward chunk data is palette-encoded into bit-packed longs and the connection expects zlib, which is not something you can hand-write in VBA. 1.8.9 is the last release where the whole protocol is within reach of a scripting runtime that was never meant for it.
We have written both halves of that up properly: how the Minecraft server protocol works covers the wire format, and what a Minecraft server actually needs to run covers the four things a real one cannot do without.
Questions
Does Google Earth really host the server?
No, and the episode says so. Google Earth has no way to run code, so a standalone Go server holds port 25565 and Earth polls it for a KML feed every two seconds. What makes it part of the series is that the world sits on the actual planet. The full source is on GitHub.
Where do the blocks end up?
At real coordinates. Spawn is the Great Pyramid of Giza, one block is one metre, and every block placed appears on the globe where you built it, named with the nearest city and the country it falls in. Warp to another wonder and you are building in another country.
The rest of the series
Or just host it properly
Google Earth Pro is not where your survival world should live. AMD Ryzen 9700X, hard-reserved RAM, NVMe, online in under a minute with a free address, DDoS protection and a 7-day money-back guarantee.