Allow Servers to Deliver Chunk Data Through HTTP(S)

For RPG, minigame, and other servers that reuse the same maps for many players, sending identical chunk data through the normal game connection wastes server bandwidth.

Servers should be able to provide an HTTP(S) URL for mostly static chunk data, allowing that data to be hosted behind a CDN. The client could download a versioned or hashed snapshot of a chunk from that URL, while the game server only sends changes made after that snapshot. If the cached version is already current, it would not need to be downloaded again.

This could greatly reduce repeated bandwidth usage for servers where thousands of players repeatedly load the same lobby, dungeon, arena, or RPG world.

The normal game connection should remain authoritative for live changes. The server could provide the URL, version/hash, and any delta data needed to bring the downloaded chunk up to date.

If supporting complete chunk state is too complex, the format could contain only blocks and block entities, while normal entities and other dynamic state continue to be transmitted normally.

This would be optional and would not change how existing servers work.