World Hosting Strategies

How an island is physically stored is a separate decision from which mode it is. Each mode in config.yml picks one of three hosting strategies, so you can run a packed grid for one mode and dedicated worlds for another.

modes:
  skyblock:
    hosting: grid
  oneblock:
    hosting: grid
  chunkblock:
    hosting: world_per_island

The three strategies

grid

Every island sits at its own cell in one big world, spaced by island.grid-spacing blocks. This is the lightest on resources because there is only one world to keep loaded per map. Ideal for Skyblock and OneBlock where islands are small and self contained.

island:
  grid-spacing: 1024   # blocks between island centers

world_per_island

Each island gets a genuinely separate world, made by copying the mode's base/template world at creation. Every island starts from identical terrain, and because it is a real separate world, it suits modes like ChunkBlock that rely on natural generation.

server_shared

The networked option: per island worlds hosted locally on each backend, sharded across the network by this server's tag. This is the strategy that pairs with Proxy Sharding and needs the same shared database.

Nether and End on a grid

When per island Nether and End are enabled, each grid map gets a shared Nether and End world grid-packed at the same cell as the overworld, so an island's Nether sits directly beneath its claim. Portals inside an island relink to that island's own cell.

island:
  environments:
    nether: true
    end: true
    platform-y: 101   # where a player lands in an empty void cell