Advertisement
Guest User

Giuseppe

a guest
Jan 29th, 2012
115
0
Never
Not a member of Pastebin yet? Sign Up, it unlocks many cool features!
YAML 6.37 KB | None | 0 0
  1. # Core configurable options for LWC
  2. core:
  3.     # The language LWC will use, specified by the shortname. For example, English = en, French = fr, German = de,
  4.     # and so on
  5.     locale: de
  6.  
  7.     # If set to true, LWC will automatically download new updates as they become available
  8.     autoUpdate: true
  9.  
  10.     # How often updates are batched to the database (in seconds). If set to a higher value than 10, you may have
  11.     # some unexpected results, especially if your server is prone to crashing.
  12.     flushInterval: 10
  13.  
  14.     # LWC regularly caches protections locally to prevent the database from being queried as often. The default is 10000
  15.     # and for most servers is OK. LWC will also fill up to <precache> when the server is started automatically.
  16.     cacheSize: 10000
  17.  
  18.     # How many protections are precached on startup. If set to -1, it will use the cacheSize value instead and precache
  19.     # as much as possible
  20.     precache: -1
  21.  
  22.     # The default menu style presented to players. Possible options are basic and advanced. Basic prefers to use
  23.     # aliases such as /cprivate over its advanced counterpart, /lwc -c private or /lwc create private
  24.     defaultMenuStyle: basic
  25.  
  26.     # If true, players will be sent a notice in their chat box when they open a protection they have access to, but
  27.     # not their own unless <showMyNotices> is set to true
  28.     showNotices: true
  29.  
  30.     # If true, players will be sent a notice in their chat box when they open a protection they own.
  31.     showMyNotices: true
  32.  
  33.     # If true, ops will be considered LWC admins (e.g with a Permissions plugin, considered to have lwc.admin) and thus
  34.     # will have very destructive LWC commands.
  35.     opIsLWCAdmin: true
  36.  
  37.     # If true, LWC will not log history about protections. If you are using LWC-Economy and this is disabled, you will
  38.     # NOT receive refunds for purchased protections
  39.     disableHistory: false
  40.  
  41.     # if true, LWC will only allow protections to be created inside of Towns via the Towny plugin
  42.     townyBorders: false
  43.  
  44.     # The permission node prefix that is used to match player groups when
  45.     # no supported permission plugin is found, e.g group.vip matches the player's group as vip
  46.     groupPrefix: 'group.'
  47.  
  48. # Controls how the updater operates
  49. updater:
  50.     # The branch to select updates from
  51.     # STABLE or BLEEDING_EDGE
  52.     branch: STABLE
  53.  
  54.     # When to retrieve updates
  55.     # Either AUTOMATIC or MANUAL
  56.     method: AUTOMATIC
  57.  
  58. # "Fun" options
  59. optional:
  60.     # Protections are only active when a player is online.
  61.     # So if a player is offline, anyone can access it. If the player is online, it functions normally
  62.     onlyProtectWhenOwnerIsOnline: false
  63.  
  64.     # Protections are only active when a player is offline
  65.     onlyProtectWhenOwnerIsOffline: false
  66.  
  67.     # Opt out of the optional metrics tooling
  68.     # Available online: http://metrics.griefcraft.com/plugin/LWC/
  69.     optOut: false
  70.  
  71. # Database information for LWC
  72. database:
  73.     # The database adapter to use, for example sqlite (default) or mysql
  74.     adapter: mysql
  75.  
  76.     # This is strictly for SQLite only and should be left alone. When changing to MySQL and this is left intact,
  77.     # LWC will automatically convert your protections from SQLite to MySQL
  78.     path: 'plugins/LWC/lwc.db'
  79.  
  80.     # The MySQL host. You can specify a non-default port (3306) by adding :port, e.g host: 'localhost:3307'
  81.     host: 'localhost'
  82.  
  83.     # The database LWC should use to store data (not necessary for SQLite)
  84.     database: 'mc'
  85.  
  86.     # The username LWC should use to connect to the server with (not necessary for SQLite)
  87.     username: 'root'
  88.  
  89.     # The password LWC should use to connect to the server with (not necessary for SQLite)
  90.     password: 'hiden'
  91.  
  92.     # The prefix for LWC tables. For example, a prefix of 'lwc_' will make
  93.     # the protections table show up as lwc_protections
  94.     prefix: 'lwc_'
  95.  
  96. # The protections nodes allows you to define, remove and modify which blocks LWC is allowed to protect
  97. # This means that you could make any block you want protectable, or remove existing protectable blocks
  98. # (e.g trap doors, etc.)
  99. protections:
  100.    # These values serve as default values for the protections defined under blocks
  101.  
  102.     # If true, the default behaviour will be to BLOCK redstone to protections, and /credstone on (Protection Flag)
  103.     # will ALLOW redstone to the protection
  104.     # If false, the default behaviour will be to ALLOW redstone to protections, and /credstone on will
  105.     # BLOCK redstone to the protection
  106.     denyRedstone: false
  107.  
  108.     # Settable to private, public, or off. It defines what protections are registered as when you place them on
  109.     # the ground
  110.     autoRegister: true
  111.  
  112.     # Used in very specific use-cases: makes LWC ignore block destruction for the given block or all blocks, allowing
  113.     # players to remove the block and resulting protection.
  114.     ignoreBlockDestruction: false
  115.  
  116.     # If left clicking should be ignored by LWC. An example of this would be to add ignoreLeftClick under a note block
  117.     # protection to allow players to play the note block's note, but not change the note (which is done via right click,
  118.     # which would be blocked by LWC.)
  119.     ignoreLeftClick: false
  120.  
  121.     # If right clicking should be ignored by LWC.
  122.     ignoreRightClick: false
  123.  
  124.     # If LWC should ignore explosions to the protection. For example, you could allow Doors to be blown by explosions,
  125.     # but not chests.
  126.     ignoreExplosions: false
  127.  
  128.     # Creation messages and protection notices will not be shown for this protection
  129.     quiet: false
  130.  
  131.     # Current and custom protections are defined here by their block name or id
  132.     # If you use the Id, you MUST encase it in quotes, for example (chest):
  133.     # '54':
  134.     #     enabled: true
  135.     # The custom protection must also have enabled: true under it for it to function in the world
  136.     blocks:
  137.         chest:
  138.             enabled: true
  139.             autoRegister: private
  140.         furnace:
  141.             enabled: true
  142.             autoRegister: private
  143.         dispenser:
  144.             enabled: true
  145.             autoRegister: private
  146.         sign:
  147.             enabled: true
  148.             autoRegister: private
  149.         wooden_door:
  150.             enabled: true
  151.         iron_door:
  152.             enabled: true
  153.         trap_door:
  154.             enabled: true
  155.  
  156. modes:
  157.     droptransfer:
  158.         enabled: true
  159.     persist:
  160.         enabled: true
Advertisement
Add Comment
Please, Sign In to add comment
Advertisement