World Configuration

World Modes

Each world on your server can have its own claiming mode. This allows you to enable claiming in some worlds while disabling it in others.

worlds:
  world:
    aliase: "Overworld"
    mode: SURVIVAL

Mode	Description
`SURVIVAL`	Normal mode. Players can claim freely. Unclaimed chunks have no protection.
`SURVIVAL_REQUIRING_CLAIMS`	Players must claim chunks to build. Unclaimed chunks are protected — no one can build on them. Forces players to claim before doing anything. The protections applied to those unclaimed chunks come from the dedicated `survival_requiring_claims-mode:` block in `config.yml` (mirrors the `protected-mode:` block).
`PROTECTED`	The whole world is treated as a single read-only protected area. No new claims can be created and unclaimed chunks are fully protected against non-staff actions. Use for spawn-only worlds, build showcases, or staff-only worlds. The default protections applied to unclaimed chunks come from the dedicated `protected-mode:` block at the bottom of `config.yml`.
`DISABLED`	Claiming is completely disabled in this world. No claim commands, no protection. The world functions as vanilla.

The aliase (alias) is the display name shown in GUIs and messages instead of the internal world name.

Protected areas without player claims (2.7.0)

worlds:
  world_the_end:
    mode: SURVIVAL
    allow-player-claims: false

allow-player-claims: false keeps everything a mode already does — building outside claims stays free, existing claims stay protected — but players can no longer create or grow claims there: /claim, /claim radius, /claim addchunk, /claim merge and the matching auto-modes all answer with claims-disabled-in-world.

/parea is never affected — staff keep creating protected areas in that world. That is the point: protect the main End island with a /parea while the outer islands stay open for everyone to build on, with nobody able to claim them.
Claims that already exist keep working, and their owners can still manage or delete them (/unclaim, /claim delchunk), so enabling the switch on a populated world never traps anyone.

World Border

SCS2 includes its own world border system, independent from Minecraft's vanilla world border:

worlds:
  world:
    border:
      enabled: false
      center: 0,0
      size: 100_000

enabled — activate the world border for this world
center — X,Z coordinates of the border center
size — total diameter in blocks (from edge to edge)

Players cannot claim chunks outside the world border. When enabled, the claiming system automatically rejects any claim attempt outside the border boundaries.

Chunk Limits

Chunk limits restrict how many of specific block types or entity types can exist within a single chunk. This is a per-world performance feature, independent of the claim system — it applies to all chunks in the world, claimed or not.

worlds:
  world:
    chunk-limits:
      enabled: false
      mode: EVERYWHERE    # EVERYWHERE | CLAIMS_ONLY | OUTSIDE_CLAIMS_ONLY
      blocks:
        HOPPER: 24
        REDSTONE_WIRE: 200
        REDSTONE_TORCH: 50
        REPEATER: 150
        COMPARATOR: 80
        PISTON: 32
        STICKY_PISTON: 32
        OBSERVER: 60
        SPAWNER: 6
        TNT: 20
      entities:
        ARMOR_STAND: 12
        ZOMBIE: 12
        SKELETON: 12
        CREEPER: 12
        SPIDER: 8
        COW: 15
        SHEEP: 15
        PIG: 15
        CHICKEN: 20
        VILLAGER: 8
        WITCH: 8
        MINECART: 12
        MINECART_HOPPER: 8
        MINECART_CHEST: 8
        ITEM_FRAME: 20
        GLOW_ITEM_FRAME: 20

mode: EVERYWHERE — limits apply to every chunk in the world.
mode: CLAIMS_ONLY — limits only apply inside claimed chunks.
mode: OUTSIDE_CLAIMS_ONLY — limits only apply outside claimed chunks.

When a player tries to place a block or entity that would exceed the limit, the action is denied and a message is shown. This prevents lag machines and excessive entity counts.

Mob Stacker

The built-in mob stacker merges nearby mobs of the same type into a single entity with a count display, dramatically reducing entity counts and improving server performance.

worlds:
  world:
    mob-stacker:
      enabled: false
      excludeNamedEntities: true
      killOneByOne: false
      multiplyDrop: true
      maxStackAmount: 50
      exclusions:
        - VILLAGER
        - ENDER_DRAGON
        - PILLAGER
        - WITHER
        - ZOMBIE_VILLAGER
        - WANDERING_TRADER

Option	Description
`excludeNamedEntities`	Mobs with custom names are not stacked.
`killOneByOne`	When true, killing a stacked mob only removes one from the stack. When false, the entire stack dies at once.
`multiplyDrop`	Multiply drops by the stack size when the stack is killed.
`maxStackAmount`	Maximum number of mobs in a single stack.
`exclusions`	List of entity types that are never merged into stacks (boss mobs, traders, etc.).

The mob stacker operates per world and is independent of the claiming system. It works in all chunks, not just claimed ones.

Item Stacker

Similar to the mob stacker, the item stacker merges nearby dropped items of the same type to reduce ground clutter and improve performance.

worlds:
  world:
    item-stacker:
      enabled: false
      excludeNamedItems: true
      pickupDelay: 1000
      maxStackAmount: 512
      exclusions:
        - ELYTRA

Option	Description
`excludeNamedItems`	Items with custom display names are never merged into stacks.
`pickupDelay`	Delay (in ticks, 20 per second) before a stacked item can be picked up.
`maxStackAmount`	Maximum size of a stacked drop. Exceeds vanilla's 64-item cap — the count is displayed above the item.
`exclusions`	Item types that are never merged (e.g. `ELYTRA`, where stacking would corrupt durability).

2.7.0 — duplication fixes. A stacked pile now carries its real amount on the item entity itself instead of in the floating label, and every pickup moves an exact amount: a partial pickup (full inventory) no longer leaves the pile claiming its pre-pickup total, and items taken by a mob — gold traded to a piglin, an allay fetching a stack — are reconciled with what is really left on the ground. Both were duplication exploits; servers that had turned the item stacker off because of them can turn it back on.

2.7.1 — duplication fix for stack sizes above 64. When an item's max stack size is raised above 64 (data component, custom-stack plugins), two piles on the ground could both still be merged by vanilla. Vanilla moves items from one entity to the other without knowing about the stored amount, leaving the shrunken pile advertising items that no longer existed. Item merging is now performed by the plugin itself (ItemMergeEvent), and the stored amount is reconciled against the entity's visible count on every read, so anything that changes a stack behind the plugin's back is absorbed instead of being handed out twice. If you are running an older build, set maxStackAmount: 64 as a workaround.