Kisten sichern

Dieses Thema im Forum "Server Plugins" wurde erstellt von PROgramm, 28. Juli 2012.

Status des Themas:
Es sind keine weiteren Antworten möglich.
  1. PROgramm
    Offline

    PROgramm

    Registriert seit:
    21. Juni 2012
    Beiträge:
    41
    Hi,

    da auf meinem Server nichts protected wird (LogBlock und McBans, etc.) sind vorhanden,
    kann man iwie in alle Kisten schauen -.-'
    Habe zwar LWC drauf, aber man kann trotzdem in die Kisten schauen.

    Kann man einstellen, dass die Kisten SOFORT gelockt sind, wenn man sie setzt ?
     
    #1
  2. iSmoothxD
    Offline

    iSmoothxD

    Registriert seit:
    18. Mai 2012
    Beiträge:
    57
    Wenn du OP bist kannste eh reinkucken? XDDD
     
    #2
  3. marcodie
    Offline

    marcodie

    Registriert seit:
    7. März 2012
    Beiträge:
    38
    Ort:
    Hamburg
    Minecraft:
    mdkeks
    Schau einfach mal in deine LWC configs, da kannst einstellen das Kisten beim setzten gelockt werden.
    Und als Admin oder OP kannst du immer in gelockte kisten schauen, oder wenn die permission dazu vergeben sind.
     
    #3
  4. PROgramm
    Offline

    PROgramm

    Registriert seit:
    21. Juni 2012
    Beiträge:
    41
    Danke für diese Erleuchtung ^ ^.
    Klar, das weiß ich ja ...



    Code (Text):
    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. # Controls how the updater operates
    43. updater:
    44.  
    45. # The branch to select updates from
    46. # STABLE or BLEEDING_EDGE
    47. branch: STABLE
    48.  
    49. # When to retrieve updates
    50. # Either AUTOMATIC or MANUAL
    51. method: AUTOMATIC
    52.  
    53. # "Fun" options
    54. optional:
    55.  
    56. # Protections are only active when a player is online.
    57. # So if a player is offline, anyone can access it. If the player is online, it functions normally
    58. onlyProtectWhenOwnerIsOnline: false
    59.  
    60. # Protections are only active when a player is offline
    61. onlyProtectWhenOwnerIsOffline: false
    62.  
    63. # Block IDs to automatically blocks from /lwc admin purge, /lwc admin expire, etc.
    64. exemptBlocks: []
    65.  
    66. # Opt out of the optional metrics tooling
    67. # Available online: [url]http://metrics.griefcraft.com/plugin/LWC/[/url]
    68. optOut: false
    69.  
    70. # Database information for LWC
    71. database:
    72.  
    73. # The database adapter to use, for example sqlite (default) or mysql
    74. adapter: sqlite
    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: 'lwc'
    85.  
    86. # The username LWC should use to connect to the server with (not necessary for SQLite)
    87. username: ''
    88.  
    89. # The password LWC should use to connect to the server with (not necessary for SQLite)
    90. password: ''
    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: off
    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. # If entities - such as zombies - are allowed to break down doors
    129. allowEntityBreakDoor: false
    130.  
    131. # Creation messages and protection notices will not be shown for this protection
    132. quiet: false
    133.  
    134. # Current and custom protections are defined here by their block name or id
    135. # If you use the Id, you MUST encase it in quotes, for example (chest):
    136. # '54':
    137. # enabled: true
    138. # The custom protection must also have enabled: true under it for it to function in the world
    139. blocks:
    140. chest:
    141. enabled: true
    142. autoRegister: private
    143. furnace:
    144. enabled: true
    145. autoRegister: private
    146. dispenser:
    147. enabled: true
    148. autoRegister: private
    149. sign:
    150. enabled: true
    151. autoRegister: private
    152. wooden_door:
    153. enabled: true
    154. iron_door:
    155. enabled: true
    156. trap_door:
    157. enabled: true
    158. fence_gate:
    159. enabled: true
    160.  
    161.  
    162. modes:
    163. droptransfer:
    164. enabled: true
    165. persist:
    166. enabled: true


    WO GENAU ?

    MFG
     
    #4
  5. DerHolzhacker
    Offline

    DerHolzhacker

    Registriert seit:
    24. April 2012
    Beiträge:
    360
    Ort:
    Bayern
    Minecraft:
    DerHolzhacker
    Pack das doch bitte in einen Spoiler!!!!

    Mfg DerHolzhacker
     
    #5
  6. Dean
    Offline

    Dean Administrator Entwickler

    Registriert seit:
    11. August 2011
    Beiträge:
    2.109
    Ort:
    NRW
    Minecraft:
    DeanR
    habs in Spoiler gepackt
     
    #6
  7. PROgramm
    Offline

    PROgramm

    Registriert seit:
    21. Juni 2012
    Beiträge:
    41
    Sorry, dass ich nicht gleich dran gedacht habe...

    Kann mir jetzt trotzdem bitte jemand helfen o_O
     
    #7
  8. Smuil
    Online

    Smuil

    # Settable to private, public, or off. It defines what protections are registered as when you place them on
    # the ground
    autoRegister: off


    Das ist das was du brauchst. Damit sind beim setzen der Kisten diese automatisch Protected
     
    #8
  9. little_psycho11
    Offline

    little_psycho11

    Registriert seit:
    5. Februar 2012
    Beiträge:
    641
    Minecraft:
    little_psycho11
    Du suchst Automatisches Protecten bzw. Registrieren der Kisten im Plugin. Jetzt übersetz das mal auf Englisch und schau dann in der COnfig was das wohl sein mag....
     
    #9
  10. PROgramm
    Offline

    PROgramm

    Registriert seit:
    21. Juni 2012
    Beiträge:
    41
    Ok, habs jetzt gefunden.
    Soll das auf off bleiben oder soll ich das auf on umschreiben?
     
    #10
Status des Themas:
Es sind keine weiteren Antworten möglich.