BuildSystem
  • BuildSystem
  • Getting started
    • Tutorials
    • Config
    • Common Issues
  • Permissions
    • Commands
    • Navigator
    • Worlds
      • Creating Worlds
      • Restricting Worlds
    • Admin/Bypass
    • Messages
  • Commands
    • /back
    • /blocks
    • /build
    • /buildsystem
    • /config
    • /day
    • /explosions
    • /gm
    • /night
    • /noai
    • /physics
    • /settings
    • /setup
    • /skull
    • /spawn
    • /speed
    • /top
    • /worlds
      • addBuilder
      • builders
      • delete
      • edit
      • help
      • importAll
      • import
      • info
      • item
      • removeBuilder
      • removeSpawn
      • rename
      • setItem
      • setCreator
      • setProject
      • setStatus
      • setPermission
      • setSpawn
      • tp
      • unimport
  • Other
    • Placeholders
    • Changelog
    • LuckPerms Context
Powered by GitBook
On this page
  • Only modify worlds owned by player
  • Modify worlds not owned by player

Was this helpful?

  1. Permissions
  2. Worlds

Restricting Worlds

BuildSystem allows server owners to restrict which worlds a player can modify when using commands.

All commands default to .self when no suffix (.self, .other) is provided.

For example: buildsystem.day = buildsystem.day.self

Only modify worlds owned by player

If you want a player to only modify worlds which belong to the player (i.e. player is creator), then use the command suffix .self.

For example: If you only want player's to change the world time to day (/day) in their own worlds, then give the player the permission buildsystem.day.self.

Modify worlds not owned by player

With the permission suffix .other, a player can also modify worlds that don't belong to the player (player is not creator)

For example: If you only want player's to change the world time to day (/day) in other worlds, then give the player the permission buildsystem.day.other.

PreviousCreating WorldsNextAdmin/Bypass

Last updated 4 months ago

Was this helpful?