Not a member of Pastebin yet?
Sign Up,
it unlocks many cool features!
- # While the comments in here try to be helpful, the most up-to-date
- # documentation for these options can always be found on the web at:
- #
- # 'http://dev.bukkit.org/server-mods/homespawnplus/pages/config-params'
- # If you're having problems with other plugins that have registered
- # commands that you want to use with HSP (for example, CommandBook has
- # /home, /spawn and loads first alphabetically), you can uncomment the
- # below lines and HSP will then take over those commands for it's own
- # use when it loads.
- #usurpCommands:
- # - home
- # - sethome
- # - spawn
- # - setspawn
- # This defines which permission system HSP uses. Vault and WEPIF
- # (WEPIF is built into WorldEdit) are preferred, they both provide
- # a nice interface to all other permission systems. If you don't have
- # or don't want to use either of those, there is some native support
- # for a few other permission systems that you can use. These are
- # checked in the order they are listed for existence, and the
- # first one to match is used.
- permissions:
- - vault
- - wepif
- - pex
- - perm2-compat
- - superperms
- - ops
- core:
- # 0 - Ebeans storage (will go to SqlLite or MySQL, as defined
- # by bukkit.yml)
- # 1 - Cached Ebeans - currently disabled, don't use
- storage: 0
- # this is ONLY used when "ops" is used in the "permissions" section
- # above.
- # In that case, any permissions listed here are given to everyone by
- # default (ops always have full permissions)
- # defaultPermissions:
- # - hsp.command.home.use
- # - hsp.command.sethome.use
- # set to true to enable players setting their homes by clicking beds.
- # they must also have the 'hsp.home.bedsethome' permission.
- bedsethome: false
- # The default/main world. Strategies reference this as the default
- # world, you can change that here if you like.
- defaultWorld: world_main
- # set to true if you want plugin to change the spawn of the actual map
- # (ie. even if you turn this plugin off later, whatever default spawn
- # you set in various worlds will stay)
- override_world: false
- # if recordLastLogout is true, HSP will record the precise location
- # location the player logged out at and respawn them there, instead
- # of just letting Bukkit do it. This is an attempt to work around a
- # bug where people logout close to a wall and Bukkit tries to respawn
- # them in the wall
- recordLastLogout: false
- # set to true to have a bit more verbose logging in your server.log
- # about what HomeSpawnPlus is doing
- verboseLogging: false
- # set to true to have verbose logging in your server.log as
- # strategies are being evaluated - great for debugging and testing
- # your strategies when you first set them up.
- verboseStrategyLogging: false
- # Event priority; the basic assumption is that you want HSP to
- # be the final say in your onjoin/respawn event chains - if you
- # didn't want that you probably wouldn't be running HSP in the
- # first place. But you can change it here if you want to
- # for some reason.
- eventPriority: highest
- # HSP has a notion of "default home" which the player can change
- # by using /setdefaulthome. In the event that the player has
- # deleted their defaultHome and only one home is remaining on
- # a given world, this flag says to count that last home as the
- # "default" home, even if it wasn't specifically flagged as
- # the default.
- lastHomeIsDefault: true
- # localization. "en" for english, "fr" for french, etc. Will
- # use given localization if it exists, otherwise will fall
- # back to English as the default.
- locale: en
- # default color of messages. ie. %yellow%, %red%, ..
- defaultMessageColor: "%yellow%"
- # set to true if Bukkit should be forced to reload the target
- # chunk when a player teleports. This fixes "world hole" problems
- # on teleport (exactly the same as BananaChunk plugin does).
- # This option does nothing if BananaChunk is already installed.
- reloadChunkOnTeleport: true
- # Web doc reference for event strategies:
- # http://dev.bukkit.org/server-mods/homespawnplus/pages/strategy-doc/
- #
- events:
- # strategies to use when player is joining the game
- onJoin:
- - spawnNewPlayer
- - default
- # strategies to use when player is respawning after a death
- onDeath:
- - homeMultiWorld
- - spawnLocalWorld
- # strategies to use when player types "/spawn"
- onSpawnCommand:
- - spawnLocalWorld
- - spawnDefaultWorld
- # strategies to use when player types "/groupspawn"
- onGroupSpawnCommand:
- - spawnGroup
- # strategies to use when player types "/home"
- onHomeCommand:
- - homeMultiWorld
- # strategies to use when player types "/home name"
- onNamedHomeCommand:
- - homeNamedHome
- # example of world-specific strategy
- # world:
- # myworld:
- # onDeath:
- # - homeLocalWorld
- # - spawnLocalWorld
- # onHomeCommand:
- # - homeLocalWorld
- #
- # example of permission-specific strategy
- # permission:
- # entry1:
- # permissions:
- # - my.special.permission
- # onJoin:
- # - homeSpecificWorld:specialworld
- # - spawnSpecificWorld:specialworld
- # onDeath:
- # - homeMultiWorld
- # - homeAnyWorld
- # you can globally disable individual commands here, if needed
- disabledCommands:
- home: false
- sethome: false
- spawn: false
- setspawn: false
- groupspawn: false
- setgroupspawn: false
- # cooldowns for various commands can be defined here
- # A cooldown of 0 is no cooldown at all.
- cooldown:
- home: 60
- # if set, overrides "home" cooldown for named homes
- home-named: 0
- sethome: 0
- # if set, overrides "sethome" cooldown for named homes
- sethome-named: 0
- spawn: 60
- # if set, overrides "spawn" cooldown for named spawns
- spawn-named: 0
- groupspawn: 60
- # any cooldowns listed here will be on separate timers per
- # command argument. for example if "home-named" is listed,
- # then typing "/home home1" would start home1's cooldown,
- # and "/home home2" will be on a separate cooldown.
- # cooldownSeparation:
- # - home-named
- # - spawn-named
- # - sethome-named
- # example of world-specific cooldowns
- # world:
- # myworld:
- # # whether this world should have its own cooldowns
- # cooldownPerWorld: false
- # home: 120
- # spawn: 120
- #
- # example of permission-specific cooldowns
- # permission:
- # entry1:
- # # whether these permission should have their own cooldowns
- # cooldownPerPermission: false
- # permissions:
- # - my.special.permission
- # home: 30
- # spawn: 30
- warmup:
- # globally enable or disable warmups.
- enabled: false
- # set to true if movement should cancel a warmup
- onMoveCancel: false
- # set to true if receiving damage should cancel a warmup
- onDamageCancel: false
- # individual command warmup timers
- home: 5
- spawn: 5
- groupspawn: 5
- # example of world-specific warmups
- # world:
- # myworld:
- # # whether this world should have its own warmups
- # warmupPerWorld: false
- # home: 10
- # spawn: 10
- #
- # example of permission-specific warmups
- # permission:
- # entry1:
- # # whether these permission should have their own warmups
- # warmupPerPermission: false
- # permissions:
- # - my.special.permission
- # home: 15
- # spawn: 15
- # ability to raise or lower the limit of homes you allow
- # players to have. Can be defined on a per-world or
- # per-permission basis. (-1 = unlimited)
- homeLimits:
- # If singleGlobalHome is set, all other sections are ignored
- # and a single global home is enforced. This means typing
- # /sethome on any world will always work and it will always
- # overwrite whatever other home you had set. This can be
- # overridden by the permission "hsp.singleGlobalHomeExempt",
- # in which case the limits defined below still apply.
- singleGlobalHome: true
- default:
- perWorld: 1
- global: -1
- # world:
- # myworld:
- # perWorld: 5
- # permission:
- # limit1:
- # permissions:
- # - my.custom.perm
- # - group.mygroup
- # perWorld: 3
- # global: 10
- # If you have Vault installed, HSP can use that to charge prices for
- # commands using whatever economy plugin you happen to have installed.
- # Costs will not work if you do not have Vault installed.
- #
- # http://dev.bukkit.org/server-mods/vault/
- cost:
- # if verbose is true, the player will get a message stating that their
- # account has been charged whenever they use a command with a cost.
- verbose: true
- home: 500
- sethome: 0
- spawn: 0
- groupspawn: 0
- # world:
- # myworld:
- # home: 100
- # permission:
- # limit1:
- # permissions:
- # - my.custom.perm
- # - group.mygroup
- # home: 250
- # sethome: 500
Advertisement
Add Comment
Please, Sign In to add comment