Docs

Cells

Personal plots pasted from a single template. Every player who claims a cell gets their own copy on a grid and can only build inside the area you defined.

Configurationcells.yml
Datadata/cells.yml, templates/cell.schem, templates/cell.yml
Modulecells

Requires WorldEdit or FastAsyncWorldEdit. WorldGuard is optional: PulsePrison protects cells on its own and, when WorldGuard is installed, mirrors the protection into regions.

Setting up the template

text
1. /cell world cells          creates an empty world and takes you to 0, 0
2. build or //paste the cell design around 0, 0
3. /cell area                 golden axe: left-click one corner, right-click the other
                              or /cell area pos1 and /cell area pos2
4. sneak + right-click        confirms the area (or /cell confirm)
5. /cell define               blaze rod: mark where the owner can build (inside the area)
6. sneak + right-click        confirms the buildable area (or /cell confirm)
7. /cell spawn                standing where players should appear
8. /cell finish               shows the summary
9. /cell finish confirm       saves the template and runs setup.finish-actions (/spawn by default)

Cells are pasted from grid.start-x and grid.start-z (1000, 1000) towards positive X and Z, away from where you build the template. If the template overlaps the grid, /cell finish confirm warns you. Only change it before anyone claims a cell.

/cell claim pastes the cell and takes you there. With claim.claim-on-go: true, /cell go without a cell claims one right away.

/cell cancel abandons the setup. Running it again changes the template for cells claimed afterwards.

Commands

CommandDescription
/cell claimClaim a cell for the configured price
/cell homeGo to your cell
/cell visit <player>Visit another cell, if it is open or you are trusted
/cell trust <player> · /cell untrust <player>Who can build in your cell
/cell open · /cell closeAllow or block visitors
/cell infoThe cell you stand in, or yours
/cell listCells you can build in
/cell unclaimRelease your cell (asks for a timed confirmation)
/cell world|area|define|confirm|spawn|finish|cancelAdmin: template setup
/cell delete <player>Admin: release someone's cell

Aliases: /cells, /celda, /celdas. Permissions: pulseprison.cell.use (everyone), pulseprison.cell.admin (op).

Default configuration (cells.yml)

yaml
world: cells
grid:
  gap: 16            # blocks between cells
  columns: 100
  start-x: 1000      # where the first cell is pasted
  start-z: 1000
claim:
  cost: 10000        # money
  max-trusted: 5
  reset-on-unclaim: true
  open-by-default: false
  claim-on-go: true  # /cell go without a cell claims one
setup:
  finish-actions:
    - "[player] spawn"
worldguard:
  plot-flags:        # the whole plot
    build: deny
    pvp: deny
    mob-spawning: deny
    tnt: deny
    fire-spread: deny
    lava-flow: deny
    water-flow: deny
  build-flags:       # buildable area
    use: allow
    chest-access: allow

Protection

  • In the cell world, blocks can only be placed or broken inside a cell's buildable area, and only by its owner or trusted players.
  • Walls, floors, decoration and the space between cells can't be touched by anyone without pulseprison.cell.admin.
  • Buckets are covered too.
  • A closed cell can't be entered with ender pearls or other non-command teleports.
  • With claim.reset-on-unclaim, released cells are restored from the clean template, so the next owner never inherits a build.

With WorldGuard installed, each cell also gets a plot region and a build region with the flags from cells.yml, and trusted players are synced as members.

Cells | PulsePrison Core Docs