1. Es freut uns dass du in unser Minecraft Forum gefunden hast. Hier kannst du mit über 130.000 Minecraft Fans über Minecraft diskutieren, Fragen stellen und anderen helfen. In diesem Minecraft Forum kannst du auch nach Teammitgliedern, Administratoren, Moderatoren , Supporter oder Sponsoren suchen. Gerne kannst du im Offtopic Bereich unseres Minecraft Forums auch über nicht Minecraft spezifische Themen reden. Wir hoffen dir gefällt es in unserem Minecraft Forum!

LWC Problem

Dieses Thema im Forum "Server Plugins" wurde erstellt von fs626, 21. Dezember 2012.

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

  1. fs626
    Offline

    fs626

    Registriert seit:
    24. Juli 2012
    Beiträge:
    193
    Ich habe ein Problem mit LWC. Ich möchte es, wenn jemand eine Truhe hinbaut, damit diese sich nicht automatisch protected. ich habe diese Einstellung:
    # Settable to private, public, or off. It defines what protections are registered as when you place them on
    # the ground
    autoRegister: off

    ... geht aber trotzdem nicht!

    Ich hoffe, ihr könnt mir helfen!

    MfG
     
  2. Werbung
    Online

    Werbung

  3. Oregano
    Offline

    Oregano Gesperrt

    Registriert seit:
    17. Oktober 2012
    Beiträge:
    91
    Minecraft:
    REgoran
    hmm.... voll config bitte
     
  4. fs626
    Offline

    fs626

    Registriert seit:
    24. Juli 2012
    Beiträge:
    193
    # Core configurable options for LWC
    core:

    # The language LWC will use, specified by the shortname. For example, English = en, French = fr, German = de,
    # and so on
    locale: de

    # How often updates are batched to the database (in seconds). If set to a higher value than 10, you may have
    # some unexpected results, especially if your server is prone to crashing.
    flushInterval: 10

    # LWC regularly caches protections locally to prevent the database from being queried as often. The default is 10000
    # and for most servers is OK. LWC will also fill up to <precache> when the server is started automatically.
    cacheSize: 10000

    # How many protections are precached on startup. If set to -1, it will use the cacheSize value instead and precache
    # as much as possible
    precache: -1

    # If true, players will be sent a notice in their chat box when they open a protection they have access to, but
    # not their own unless <showMyNotices> is set to true
    showNotices: true

    # If true, players will be sent a notice in their chat box when they open a protection they own.
    showMyNotices: false

    # If true, ops will be considered LWC admins (e.g with a Permissions plugin, considered to have lwc.admin) and thus
    # will have very destructive LWC commands.
    opIsLWCAdmin: true

    # If true, LWC will not log history about protections. If you are using LWC-Economy and this is disabled, you will
    # NOT receive refunds for purchased protections
    disableHistory: false

    # if true, LWC will only allow protections to be created inside of Towns via the Towny plugin
    townyBorders: false

    # The permission node prefix that is used to match player groups when
    # no supported permission plugin is found, e.g group.vip matches the player's group as vip
    groupPrefix: 'group.'

    # "Fun" options
    optional:

    # Protections are only active when a player is online.
    # So if a player is offline, anyone can access it. If the player is online, it functions normally
    onlyProtectWhenOwnerIsOnline: false

    # Protections are only active when a player is offline
    onlyProtectWhenOwnerIsOffline: false

    # Block IDs to automatically blocks from /lwc admin purge, /lwc admin expire, etc.
    exemptBlocks: []

    # Opt out of the optional metrics tooling
    # Available online: http://metrics.griefcraft.com/plugin/LWC/
    optOut: false

    # Blocks that cannot be placed around someone else's protection. This is most useful
    blacklistedBlocks:
    - 166

    # Players that are blocked from destroying any blocks protected by LWC. Mainly useful for MCPC
    # where mods can remove blocks and try to break the block by sending an event first (e.g turtle)
    blacklistedPlayers:
    - plr

    # Database information for LWC
    database:

    # The database adapter to use, for example sqlite (default) or mysql
    adapter: mysql

    # This is strictly for SQLite only and should be left alone. When changing to MySQL and this is left intact,
    # LWC will automatically convert your protections from SQLite to MySQL
    path: 'plugins/LWC/lwc.db'

    # The MySQL host. You can specify a non-default port (3306) by adding :port, e.g host: 'localhost:3307'
    host: '***'

    # The database LWC should use to store data (not necessary for SQLite)
    database: '***'

    # The username LWC should use to connect to the server with (not necessary for SQLite)
    username: '***'

    # The password LWC should use to connect to the server with (not necessary for SQLite)
    password: '***'

    # The prefix for LWC tables. For example, a prefix of 'lwc_' will make
    # the protections table show up as lwc_protections
    prefix: 'lwc_'

    # The protections nodes allows you to define, remove and modify which blocks LWC is allowed to protect
    # This means that you could make any block you want protectable, or remove existing protectable blocks
    # (e.g trap doors, etc.)
    protections:
    # These values serve as default values for the protections defined under blocks

    # If true, the default behaviour will be to BLOCK redstone to protections, and /credstone on (Protection Flag)
    # will ALLOW redstone to the protection
    # If false, the default behaviour will be to ALLOW redstone to protections, and /credstone on will
    # BLOCK redstone to the protection
    denyRedstone: false

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

    # Used in very specific use-cases: makes LWC ignore block destruction for the given block or all blocks, allowing
    # players to remove the block and resulting protection.
    ignoreBlockDestruction: false

    # If left clicking should be ignored by LWC. An example of this would be to add ignoreLeftClick under a note block
    # protection to allow players to play the note block's note, but not change the note (which is done via right click,
    # which would be blocked by LWC.)
    ignoreLeftClick: false

    # If right clicking should be ignored by LWC.
    ignoreRightClick: false

    # If LWC should ignore explosions to the protection. For example, you could allow Doors to be blown by explosions,
    # but not chests.
    ignoreExplosions: false

    # If entities - such as zombies - are allowed to break down doors
    allowEntityBreakDoor: false

    # If entities - such as villagers - should be allowed to interact with protections (i.e doors)
    allowEntityInteract: false

    # Creation messages and protection notices will not be shown for this protection
    quiet: false

    # Current and custom protections are defined here by their block name or id
    # If you use the Id, you MUST encase it in quotes, for example (chest):
    # '54':
    # enabled: true
    # The custom protection must also have enabled: true under it for it to function in the world
    blocks:
    chest:
    enabled: true
    autoRegister: private
    furnace:
    enabled: true
    autoRegister: private
    dispenser:
    enabled: true
    autoRegister: private
    sign:
    enabled: true
    autoRegister: private
    wooden_door:
    enabled: true
    iron_door:
    enabled: true
    trap_door:
    enabled: true
    fence_gate:
    enabled: true

    modes:
    droptransfer:
    enabled: true

    # allow items to be transferred across world boundaries
    crossWorld: false
    persist:
    enabled: true
     
  5. ST. Bigbuild
    Offline

    ST. Bigbuild

    Registriert seit:
    4. Oktober 2012
    Beiträge:
    8
    Hay probier mal bei core.yml bei blocks:
    chest:
    enabled: true
    autoRegister: private


    enable auf false umzustellen evtl klappt es dann.
     
Status des Themas:
Es sind keine weiteren Antworten möglich.