Not a member of Pastebin yet?
Sign Up,
it unlocks many cool features!
- # Limited Creative - Configuration
- #
- # (YAML-Syntax: http://en.wikipedia.org/wiki/YAML)
- #
- # This configuration-file is automatically written when changed via
- # ingame-commands. So any manual added comments are removed.
- # Inventory-Feature
- #
- # http://dev.bukkit.org/server-mods/limited-creative/pages/features/inventory/
- inventory:
- # InventoryEnabled
- #
- # Use this option to disable the separated inventories feature, for example if
- # you use another Plugin handling the inventories, like
- # Multiverse-Inventories.
- #
- # default: true
- enabled: false
- # InventoryStoreCreative
- #
- # Should the creative-inventory also be stored on disk, when switching to
- # survival? If disabled, the inventory gets cleared every time on switching to
- # creative.
- #
- # default: true
- storeCreative: true
- # InventorySeparateAdventure
- #
- # When true, your players get a separate inventory when switching to adventure
- # gamemode (2). Otherwise they have the default survival inventory while in
- # adventure gamemode.
- #
- # default: false
- separateAdventure: true
- # InventoryFolder
- #
- # The folder inside the datadir-folder (plugin/LimitedCreative) where the
- # inventories are saved to. By default the inventories are saved to
- # "plugin/LimitedCreative/inventories".
- #
- # default: "inventories"
- folder: inventories
- # InventoryCreativeArmor
- #
- # When set, all creative Player automatically wears the given items as Armor.
- # So they are better seen by other Players.
- creativeArmor:
- # InventoryCreativeArmorEnabled
- #
- # When disabled, the players Armor isn't changed.
- #
- # default: true
- enabled: false
- # InventoryCreativeArmorItems
- #
- # Allows changing of the "Creative-Armor" to be wear when in creative mode
- #
- # *see Blacklist for details on Item-Types
- head: CHAINMAIL_HELMET
- chest: CHAINMAIL_CHESTPLATE
- legs: CHAINMAIL_LEGGINGS
- feet: CHAINMAIL_BOOTS
- # Creative Limits-Feature
- #
- # http://dev.bukkit.org/server-mods/limited-creative/pages/features/limit/
- limit:
- # LimitEnabled
- #
- # Prevents all players in creative-mode from: - accessing chests - dropping
- # items from "inventory" to the ground - doing PvP (wouldn't be fair, would
- # it?)
- #
- # Also if this option is disabled all other Limit-Options below are disabled
- # too. To just disable some of these limitations, use the
- # "nolimit"-permissions.
- #
- # default: true
- enabled: true
- # LimitDropsInsteadPrevent
- #
- # When enabled items that are dropped by creative players are removed (burning
- # in the hellfire or so, they just disappear). When disabled the items stay in
- # the inventory of the player.
- #
- # default: false
- removeDrops: true
- # LimitPickup
- #
- # Prevents the pickup of items while in creative mode. Either the items are
- # just stay on ground and ignore that a creative player walks over it
- # ("prevent"), or the are "remove"d when a creative player walks over it. This
- # is helpful e.g. when the creative player destroys a long line of rails.
- #
- # valid options: remove / prevent / false default: remove
- pickup: prevent
- # LimitDamageToMobs
- #
- # Prevents dealing damage to all creatures when the player is in creative
- # (friendly sheeps as well as hostile creepers).
- #
- # default: false
- damageToMobs: true
- # LimitInteraction
- #
- # Prevents players of interacting with specific blocks as addition to chests
- # in creative mode (and only in creative).
- #
- # You can use the technical name (http://tinyurl.com/bukkit-material) or the
- # id of the block/item (better use the id, if you're not sure). You may add
- # the data separated with a colon e.g.: "WOOL:11" blocks blue wool. But be
- # sure to put it in quotes, to not break yml-configuration! Named data values
- # aren't supported yet. If you don't add a data-value, all blocks of this
- # material are blocked.
- #
- # default: - SIGN - SIGN_POST - LEVER - STONE_BUTTON - WOOD_BUTTON - WORKBENCH
- # - ANVIL - ENCHANTMENT_TABLE
- interact:
- - WALL_SIGN
- - SIGN_POST
- - LEVER
- - STONE_BUTTON
- - WOOD_BUTTON
- - WORKBENCH
- - ANVIL
- - ENCHANTMENT_TABLE
- - 117
- - 379
- -
- -
- -
- -
- # LimitEntityInteraction
- #
- # Prevents players of interacting with specific entities in creative mode (and
- # only in creative).
- #
- # You can use the technical name (see http://tinyurl.com/bukkit-entity) or the
- # id of the entity (better use the id, if you're not sure).
- #
- # default: - MINECART_CHEST - MINECART_FURNACE - MINECART_HOPPER - ITEM_FRAME
- # - VILLAGER
- entityInteract:
- - MINECART_CHEST
- - MINECART_FURNACE
- - MINECART_HOPPER
- - ITEM_FRAME
- - VILLAGER
- # LimitUse
- #
- # Prevents players of using or placing specific items/blocks in creative mode
- # (and only in creative).
- #
- # You can use the technical name (see http://tinyurl.com/bukkit-material) or
- # the id of the block/item (better use the id, if you're not sure). You may
- # add the data separated with a colon e.g.: "WOOL:11" blocks blue wool. But be
- # sure to put it in quotes, to not break yml-configuration! Named data values
- # aren't supported yet. If you don't add a data-value, all blocks of this
- # material are blocked.
- #
- # default: - EXP_BOTTLE - BEDROCK
- use:
- - EXP_BOTTLE
- - bedrock
- - iron_block
- - gold_block
- - diamond_block
- - emerald_block
- - lapis_block
- - iron_ore
- - gold_ore
- - diamond_ore
- - emerald_ore
- - lapis_ore
- - redstone_ore
- - coal_ore
- - 152
- - 153
- - 147
- - 148
- - 373
- # LimitBreak
- #
- # Prevents players of destroying specific blocks in creative mode (and only in
- # creative).
- #
- # You can use the technical name (see http://tinyurl.com/bukkit-material) or
- # the id of the block/item (better use the id, if you're not sure). You may
- # add the data separated with a colon e.g.: "WOOL:11" blocks blue wool. But be
- # sure to put it in quotes, to not break yml-configuration! Named data values
- # aren't supported yet. If you don't add a data-value, all blocks of this
- # material are blocked.
- #
- # default: - BEDROCK
- break:
- - BEDROCK
- # Region GameModes-Feature
- #
- # http://dev.bukkit.org/server-mods/limited-creative/pages/features/region/
- region:
- # RegionEnabled
- #
- # Enables the feature for "creative-regions". This Feature is automatically
- # disabled, if the required plugin "WorldGuard"
- # (http://dev.bukkit.org/server-mods/worldguard/) isn't found.
- #
- # default: true
- enabled: false
- # RegionRememberOptional
- #
- # Remembers if players disables the Region-GameMode (by switching in an
- # optional region to World-Default-GameMode with /lc creative|survival). So
- # when the player re-enters the region, he keep his GameMode which he left it
- # in. Hint: This is very confusing, if MultiVerse "enforce gamemode" swaps
- # your state (default). So better don't use with Multiverse.
- #
- # default: false
- rememberOptional: false
- # RegionSafeMode
- #
- # When a player leaves a region he always will get back to the World-GameMode,
- # even if he entered the region already in the Region-GameMode. So its the
- # opposite analog to RegionRememberOptional. That means: If a GM in
- # creative-mode walks/flies through a creative-region in a survival world, he
- # will get back to survival on leaving the region.
- #
- # default: false
- safeMode: false
- # RegionMaximumFallingHeight
- #
- # When the player is more than this count of blocks above the ground, he is
- # prevented from changing the region that sets him survival which would cause
- # him falling and hurting.
- #
- # default: 3
- maximumFloatingHeight: 3
- # CommandBlocker-Feature
- #
- # http://dev.bukkit.org/server-mods/limited-creative/pages/features/command-blocker/
- cmdblock:
- # CmdBlockerEnabled
- #
- # Enables the feature for blocking certain commands in creative mode.
- #
- # default: true
- enabled: false
- # CmdBlockerList
- #
- # Defines the list of commands that are blocked while in creative mode. The
- # leading / isn't included. By default the list-item is treated as simple
- # string as typed in by the user after the /. All commands starting with this
- # string are blocked, even if more parameteres are entered by the user. If the
- # first character is ^ the entry is interpreted as a regular expression
- # (including the ^ for begin of the string). Only use regular expressions if
- # you know them!
- #
- # Examples: - home - give diamond - ^home .+ - ^chest (one|two|three) -
- # ^(lc|limitedcreative) s(urvival)?\s*$
- #
- # default: []
- commands: []
- # GameMode-Permissions-Feature
- #
- # This Feature requires Vault-Plugin to be active.
- #
- # http://dev.bukkit.org/server-mods/limited-creative/pages/features/gmperm/
- gmperm:
- # GMPermEnabled
- #
- # Activates that players are put in a special permission group while in
- # creative mode.
- #
- # default: false
- enabled: false
- # GMPermCreativeGroup
- #
- # Defines the Permission-Group which the player gets added to on entering
- # creative-mode. If this value is changed the old group won't be automatically
- # removed from players already in it. So be sure to delete the old group or
- # remove all player of it, that they don't get stuck with that permissions.
- creativeGroup: ''
- # GMPermAdventureGroup
- #
- # Like GMPermCreativeGroup but for adventure users. This is optional, so you
- # don't have to set any group.
- #
- # default: false
- adventureGroup: false
- # Metrics
- #
- # This settings allows the Addon-Author to track the Servers using this plugin.
- # It will not track any player related data like names, ips, online time or
- # such. Please do not disable the option! As more servers are using the plugin
- # and the author knows, as more he is willing to support the plugin! Its a
- # win-win for both.
- #
- # default: true
- metrics: false
- # Debug
- #
- # The debug modus spams much details about the plugin to the server-log
- # (console) which can help to solve issues.
- #
- # default: false
- debug: false
Advertisement
Add Comment
Please, Sign In to add comment