okrádání hráčů "hopper"

[ON2X]

mám tam tyhle textový dokumenty ale záleží jakej chcete

Kód: Vybrat vše

 backups   
 lib   
 core.yml   6.7 KB 17. 02. 22:02
 doors.yml           623 B 17. 02. 22:02
 limitsv2.yml   366 B 17. 02. 22:02
 lwc.db   9 MB 16. 04. 14:35
 magnet.yml   372 B 17. 02. 22:02
 worldguard.yml   613 B 09. 03. 09:10


[Cernokneznik]

Dej sem core.ym prosím. Tam to určitě bude-
-Pro jistotu prosím ještě lwc.db.
trololololo

[nejento]

@Cernokneznik lwc.db ti bude na nic. Tam jsou jenom listy těch zamčených truhel.
Stačí jenom core.yml do Code a Spoileru.

[Cernokneznik]

Já vím, ale vytáhnu z toho jména hráčů, a o ty mi šlo potřebuju je...

[SNOBcrazy]

core.yml

Kód: Vybrat vše

# 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: en

    # 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.'

# Controls how the updater operates
updater:

    # The branch to select updates from
    # STABLE or BLEEDING_EDGE
    branch: STABLE

    # When to retrieve updates
    # Either AUTOMATIC or MANUAL
    method: MANUAL

# "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: sqlite

    # 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: 'localhost'

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

    # 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


Spoiler: zobrazit

# 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: en

# 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.'

# Controls how the updater operates
updater:

# The branch to select updates from
# STABLE or BLEEDING_EDGE
branch: STABLE

# When to retrieve updates
# Either AUTOMATIC or MANUAL
method: MANUAL

# "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: sqlite

# 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: 'localhost'

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

# 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

[nejento]

Do Code a Spoileru je míněno jako

Kód: Vybrat vše

[spoiler][code]SEM :D[/code][/spoiler]

ono to potom udělá něco takového:

Spoiler: zobrazit

Kód: Vybrat vše

SEM :D

Příjde mi, jako bys měl starý config. Nebo mám ten starý config já. Smaž core.yml a restartuj server. Vygeneruje se nový a ten sem zkopíruj.

[SNOBcrazy]

Spoiler: zobrazit

Kód: Vybrat vše

# 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: en

    # 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.'

# Controls how the updater operates
updater:

    # The branch to select updates from
    # STABLE or BLEEDING_EDGE
    branch: STABLE

    # When to retrieve updates
    # Either AUTOMATIC or MANUAL
    method: MANUAL

# "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: sqlite

    # 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: 'localhost'

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

    # 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


hotovo, smazal jsem to, vygenerovalo se nový a vložil jsem to sem

[nejento]

A aktualizoval jsi LWC?