Pastebin launched a little side project called VERYVIRAL.com, check it out ;-) Want more features on Pastebin? Sign Up, it's FREE!
Guest

LWC

By: a guest on Feb 18th, 2013  |  syntax: None  |  size: 6.70 KB  |  views: 26  |  expires: Never
download  |  raw  |  embed  |  report abuse  |  print
Text below is selected. Please press Ctrl+C to copy to your clipboard. (⌘+C on Mac)
  1. # Core configurable options for LWC
  2. core:
  3.  
  4.     # The language LWC will use, specified by the shortname. For example, English = en, French = fr, German = de,
  5.     # and so on
  6.     locale: en
  7.  
  8.     # How often updates are batched to the database (in seconds). If set to a higher value than 10, you may have
  9.     # some unexpected results, especially if your server is prone to crashing.
  10.     flushInterval: 10
  11.  
  12.     # LWC regularly caches protections locally to prevent the database from being queried as often. The default is 10000
  13.     # and for most servers is OK. LWC will also fill up to <precache> when the server is started automatically.
  14.     cacheSize: 10000
  15.  
  16.     # How many protections are precached on startup. If set to -1, it will use the cacheSize value instead and precache
  17.     # as much as possible
  18.     precache: -1
  19.  
  20.     # If true, players will be sent a notice in their chat box when they open a protection they have access to, but
  21.     # not their own unless <showMyNotices> is set to true
  22.     showNotices: true
  23.  
  24.     # If true, players will be sent a notice in their chat box when they open a protection they own.
  25.     showMyNotices: false
  26.  
  27.     # If true, ops will be considered LWC admins (e.g with a Permissions plugin, considered to have lwc.admin) and thus
  28.     # will have very destructive LWC commands.
  29.     opIsLWCAdmin: true
  30.  
  31.     # If true, LWC will not log history about protections. If you are using LWC-Economy and this is disabled, you will
  32.     # NOT receive refunds for purchased protections
  33.     disableHistory: false
  34.  
  35.     # if true, LWC will only allow protections to be created inside of Towns via the Towny plugin
  36.     townyBorders: false
  37.  
  38.     # The permission node prefix that is used to match player groups when
  39.     # no supported permission plugin is found, e.g group.vip matches the player's group as vip
  40.     groupPrefix: 'group.'
  41.  
  42.     # If you will be notified of LWC updates
  43.     updateNotifier: true
  44.  
  45. # "Fun" options
  46. optional:
  47.  
  48.     # Protections are only active when a player is online.
  49.     # So if a player is offline, anyone can access it. If the player is online, it functions normally
  50.     onlyProtectWhenOwnerIsOnline: false
  51.  
  52.     # Protections are only active when a player is offline
  53.     onlyProtectWhenOwnerIsOffline: false
  54.  
  55.     # Block IDs to automatically blocks from /lwc admin purge, /lwc admin expire, etc.
  56.     exemptBlocks: []
  57.  
  58.     # Opt out of the optional metrics tooling
  59.     # Available online: http://metrics.griefcraft.com/plugin/LWC/
  60.     optOut: false
  61.  
  62.     # Blocks that cannot be placed around someone else's protection. This is most useful
  63.     blacklistedBlocks:
  64.     - 154
  65.  
  66.     # Players that are blocked from destroying any blocks protected by LWC. Mainly useful for MCPC
  67.     # where mods can remove blocks and try to break the block by sending an event first (e.g turtle)
  68.     blacklistedPlayers:
  69.     - plr
  70.  
  71. # Database information for LWC
  72. database:
  73.  
  74.     # The database adapter to use, for example sqlite (default) or mysql
  75.     adapter: MySQL
  76.  
  77.     # This is strictly for SQLite only and should be left alone. When changing to MySQL and this is left intact,
  78.     # LWC will automatically convert your protections from SQLite to MySQL
  79.     path: 'plugins/LWC/lwc.db'
  80.  
  81.     # The MySQL host. You can specify a non-default port (3306) by adding :port, e.g host: 'localhost:3307'
  82.     host: '10.10.10.11:3306'
  83.  
  84.     # The database LWC should use to store data (not necessary for SQLite)
  85.     database: '************'
  86.  
  87.     # The username LWC should use to connect to the server with (not necessary for SQLite)
  88.     username: '*************'
  89.  
  90.     # The password LWC should use to connect to the server with (not necessary for SQLite)
  91.     password: '*************'
  92.  
  93.     # The prefix for LWC tables. For example, a prefix of 'lwc_' will make
  94.     # the protections table show up as lwc_protections
  95.     prefix: 'lwc_'
  96.  
  97.     # The interval between pinging the MySQL server to keep it alive (in seconds)
  98.     ping_interval: 300
  99.  
  100. # The protections nodes allows you to define, remove and modify which blocks LWC is allowed to protect
  101. # This means that you could make any block you want protectable, or remove existing protectable blocks
  102. # (e.g trap doors, etc.)
  103. protections:
  104.     # These values serve as default values for the protections defined under blocks
  105.  
  106.     # If true, the default behaviour will be to BLOCK redstone to protections, and /credstone on (Protection Flag)
  107.     # will ALLOW redstone to the protection
  108.     # If false, the default behaviour will be to ALLOW redstone to protections, and /credstone on will
  109.     # BLOCK redstone to the protection
  110.     denyRedstone: false
  111.  
  112.     # Settable to private, public, or off. It defines what protections are registered as when you place them on
  113.     # the ground
  114.     autoRegister: off
  115.  
  116.     # Used in very specific use-cases: makes LWC ignore block destruction for the given block or all blocks, allowing
  117.     # players to remove the block and resulting protection.
  118.     ignoreBlockDestruction: false
  119.  
  120.     # If left clicking should be ignored by LWC. An example of this would be to add ignoreLeftClick under a note block
  121.     # protection to allow players to play the note block's note, but not change the note (which is done via right click,
  122.     # which would be blocked by LWC.)
  123.     ignoreLeftClick: false
  124.  
  125.     # If right clicking should be ignored by LWC.
  126.     ignoreRightClick: false
  127.  
  128.     # If LWC should ignore explosions to the protection. For example, you could allow Doors to be blown by explosions,
  129.     # but not chests.
  130.     ignoreExplosions: false
  131.  
  132.     # If entities - such as zombies - are allowed to break down doors
  133.     allowEntityBreakDoor: false
  134.  
  135.     # If entities - such as villagers - should be allowed to interact with protections (i.e doors)
  136.     allowEntityInteract: false
  137.  
  138.     # Creation messages and protection notices will not be shown for this protection
  139.     quiet: false
  140.  
  141.     # Current and custom protections are defined here by their block name or id
  142.     # If you use the Id, you MUST encase it in quotes, for example (chest):
  143.     # '54':
  144.     #     enabled: true
  145.     # The custom protection must also have enabled: true under it for it to function in the world
  146.     blocks:
  147.         chest:
  148.             enabled: true
  149.         furnace:
  150.             enabled: true
  151.         dispenser:
  152.             enabled: true
  153.         sign:
  154.             enabled: true
  155.         wooden_door:
  156.             enabled: true
  157.         iron_door:
  158.             enabled: true
  159.         trap_door:
  160.             enabled: true
  161.         fence_gate:
  162.             enabled: true
  163.  
  164. modes:
  165.     droptransfer:
  166.         enabled: false
  167.  
  168.         # allow items to be transferred across world boundaries
  169.         crossWorld: false
  170.     persist:
  171.         enabled: true
clone this paste RAW Paste Data