GroupeZ Docs
Configuration

Stackable Spawners

Configuration of Stackable Spawners in zSpawner

Stackable Spawners allow multiple spawners of the same entity type to be combined into a single block, increasing spawn rates and efficiency.

How Stackable Spawners Work

  1. Place a spawner on the ground
  2. Place another spawner of the same entity type on top
  3. The spawners merge into a stack
  4. Spawn rates increase based on stack amount
  5. A hologram displays the current stack count

Configuration

Enable Stackable Spawners

stackableSpawner:
  enable: false  # Set to true to enable

Global Limit

Maximum stack amount for all entity types:

stackableSpawner:
  globalLimit: 5

Per-Entity Limits

Set specific limits for different entity types:

stackableSpawner:
  limits:
    - SKELETON: 10
    - ZOMBIE: 8
    - BLAZE: 5

Entity Blacklist

Prevent certain entities from being stacked:

stackableSpawner:
  blacklist:
    - BLAZE
    - WITHER_SKELETON

Entity Whitelist

If specified, only these entities can be stacked (empty = all allowed):

stackableSpawner:
  whitelist: []  # Empty means all entities allowed
  # Or specify specific entities:
  # whitelist:
  #   - ZOMBIE
  #   - SKELETON

Hologram Display

Configure the hologram shown above stacked spawners:

stackableSpawner:
  hologram: '&6x%amount% &f%entity%'
PlaceholderDescription
%amount%Current stack amount
%entity%Entity type name

Stack Levels

Configure spawn behavior for each stack level:

stackableSpawner:
  levels:
    - stackAmount: 1
      delay: 200
      minSpawnDelay: 100
      maxSpawnDelay: 400
      spawnCount: 5
      maxNearbyEntities: 10
      requiredPlayerRange: 16
      spawnRange: 8

    - stackAmount: 2
      delay: 200
      minSpawnDelay: 100
      maxSpawnDelay: 400
      spawnCount: 6
      maxNearbyEntities: 10
      requiredPlayerRange: 16
      spawnRange: 8

    # ... continue for higher stack amounts

A level applies from its stackAmount up to the next one, so you do not have to declare every value. With levels 1, 5 and 10, a stack of 3 uses the level 1 settings and a stack of 7 uses the level 5 settings. A stack larger than the last declared level keeps that last level.

Level Options

OptionDescription
stackAmountStack amount this level starts applying from
delayBase delay between spawns (ticks)
minSpawnDelayMinimum random delay (ticks)
maxSpawnDelayMaximum random delay (ticks)
spawnCountNumber of entities per spawn
maxNearbyEntitiesMaximum entities before spawner pauses
requiredPlayerRangeRequired player distance for spawning
spawnRangeRadius where entities can spawn

Example Configuration

Basic Setup

stackableSpawner:
  enable: true
  globalLimit: 5
  hologram: '&6x%amount% &f%entity%'

  limits:
    - SKELETON: 10
    - BLAZE: 3

  blacklist:
    - ENDER_DRAGON
    - WITHER

  whitelist: []

  levels:
    - stackAmount: 1
      delay: 200
      minSpawnDelay: 100
      maxSpawnDelay: 400
      spawnCount: 4
      maxNearbyEntities: 10
      requiredPlayerRange: 16
      spawnRange: 8

    - stackAmount: 2
      delay: 180
      minSpawnDelay: 90
      maxSpawnDelay: 360
      spawnCount: 6
      maxNearbyEntities: 12
      requiredPlayerRange: 18
      spawnRange: 8

    - stackAmount: 3
      delay: 160
      minSpawnDelay: 80
      maxSpawnDelay: 320
      spawnCount: 8
      maxNearbyEntities: 14
      requiredPlayerRange: 20
      spawnRange: 10

    - stackAmount: 4
      delay: 140
      minSpawnDelay: 70
      maxSpawnDelay: 280
      spawnCount: 10
      maxNearbyEntities: 16
      requiredPlayerRange: 22
      spawnRange: 10

    - stackAmount: 5
      delay: 120
      minSpawnDelay: 60
      maxSpawnDelay: 240
      spawnCount: 12
      maxNearbyEntities: 18
      requiredPlayerRange: 24
      spawnRange: 12

Aggressive Stacking

For servers that want faster spawning with stacks:

stackableSpawner:
  enable: true
  globalLimit: 10

  levels:
    - stackAmount: 1
      delay: 100
      minSpawnDelay: 50
      maxSpawnDelay: 200
      spawnCount: 6
      maxNearbyEntities: 15
      requiredPlayerRange: 20
      spawnRange: 10

    - stackAmount: 5
      delay: 80
      minSpawnDelay: 40
      maxSpawnDelay: 160
      spawnCount: 15
      maxNearbyEntities: 30
      requiredPlayerRange: 24
      spawnRange: 12

    - stackAmount: 10
      delay: 60
      minSpawnDelay: 30
      maxSpawnDelay: 120
      spawnCount: 25
      maxNearbyEntities: 50
      requiredPlayerRange: 28
      spawnRange: 14

Conservative Stacking

For servers that want controlled spawning:

stackableSpawner:
  enable: true
  globalLimit: 3

  levels:
    - stackAmount: 1
      delay: 300
      minSpawnDelay: 200
      maxSpawnDelay: 600
      spawnCount: 3
      maxNearbyEntities: 6
      requiredPlayerRange: 12
      spawnRange: 6

    - stackAmount: 2
      delay: 250
      minSpawnDelay: 180
      maxSpawnDelay: 500
      spawnCount: 4
      maxNearbyEntities: 8
      requiredPlayerRange: 14
      spawnRange: 7

    - stackAmount: 3
      delay: 200
      minSpawnDelay: 150
      maxSpawnDelay: 400
      spawnCount: 5
      maxNearbyEntities: 10
      requiredPlayerRange: 16
      spawnRange: 8

Tips

Balancing Spawner Stacks

  • Lower globalLimit reduces potential lag from too many entities
  • Higher maxNearbyEntities allows more mobs but may impact performance
  • Increase requiredPlayerRange to spread players across spawners

Performance Considerations

  • Each stack level should have reasonable spawnCount values
  • Consider server TPS when setting minSpawnDelay and maxSpawnDelay
  • Use blacklist to prevent stacking of resource-intensive mobs

Economy Balance

  • Premium spawners (higher stack limits) can be sold in shops
  • Per-entity limits allow different pricing tiers
  • Stack amount directly affects farm efficiency

Virtual Spawners

Configuration and usage of Virtual Spawners in zSpawner

Silk Touch Spawners

Configuration of Silk Touch spawner mining in zSpawner

On this page

How Stackable Spawners WorkConfigurationEnable Stackable SpawnersGlobal LimitPer-Entity LimitsEntity BlacklistEntity WhitelistHologram DisplayStack LevelsLevel OptionsExample ConfigurationBasic SetupAggressive StackingConservative StackingTipsBalancing Spawner StacksPerformance ConsiderationsEconomy Balance
GroupeZ MCP

Documentation in your AI

MCP lets your AI search GroupeZ documentation and read current examples to help you configure your plugins.

Read-only · No documentation API key needed

1. Copy the server URL

Transport: HTTP (Streamable HTTP). Authentication: none. Your tool uses its own model and subscription limits.

  1. Open Plugins in ChatGPT on the web, then + → Add custom MCP server.
  2. Name it ‘GroupeZ Documentation’, paste the URL above and choose ‘No authentication’. Create and install the plugin.
  3. In a conversation, type @ and select the plugin before asking. If needed, enable search, get_page and list_pages in its settings.
Official setup guide

3. Ask a question

Use GroupeZ MCP to help me create a zMenu inventory. Search relevant pages, read the examples and cite your sources.
Other clients and troubleshooting

For clients using mcpServers, adapt this example to their format:

{
  "mcpServers": {
    "groupez-docs": {
      "url": ""
    }
  }
}

Available tools are search, get_page and list_pages. Refresh the connector’s tools after updates. If your AI cannot access them, check that the connector is enabled in the conversation and your account allows custom MCP servers. Opening the URL in a browser is not an MCP test.