Stránka 1 z 1

LWC Upravené zamykání !

Napsal: 31 srp 2012, 09:24
od mygameline
JDE ZAMYKAT: Obrázek
Rozhodl jsem se napsat Návod Na LWC teda nwm jestli to je pravda ale Kolují se věci že LWC není Bezpečné ale nevym Ja ho používam Již ROK a Nic semi nestalo ! Plus ktomuto návodu Dávám Upravený Config.
I. Instalace
1.Stahneme http://dev.bukkit.org/server-mods/lwc/
2. Poté přejdeme do Control Panelu na WebFTP, nebo si FTP otevřeme (což doporučuji) v Total Commanderu či FilleZille
návod k připojení na FTP přes Total Commander najdete zde: http://www.fakaheda.eu/view.php?cisloclanku=2006040011
3. Nyní přejdeme do složky /plugins, kde vložíme soubor LWC.jar
4.Nyní restartujeme server v Control Panelu
II. Konfigurace
1.Na FTP najdete složku LWC ve které jsou soubory:
Obrázek
2.Teď přejdeme k nastavení souboru core.yml a upravíme ho takto:
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: cz

# 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: []

# If MCPC / Tekkit is installed, should ic2/redpower transport pipes be blocked from being placed around LWC-protected chests that
# the player CANNOT access. If they can access said protection, they'll be able to place it.
blockTransportPipes: true

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

# 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
ender_chest:
enabled: true
autoRegister: private
furnace:
enabled: true
autoRegister: private
dispenser:
enabled: true
autoRegister: private
sign:
enabled: true
autoRegister: private
wooden_door:
enabled: true
autoRegister: private
iron_door:
enabled: true
autoRegister: private
trap_door:
enabled: true
autoRegister: private
fence_gate:
enabled: true
autoRegister: private
brewing_stand:
enabled: true
autoRegister: private
enchantment_table:
enabled: true
autoRegister: private
bed:
enabled: true
autoRegister: private
lever:
enabled: true
autoRegister: private
jukebox:
enabled: true
autoRegister: private
workbench:
enabled: true
autoRegister: private
note_block:
enabled: true
autoRegister: private
stone_button:
enabled: true
autoRegister: private


modes:
droptransfer:
enabled: true
persist:
enabled: true

3.Nastavíme Jazyk ! CZ , SK Nebo jaky chcete !

Kód: Vybrat vše

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

4.Je tu možnost Připojit K MySQLC

Kód: Vybrat vše

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.)

5.A teď mužeme nastavit Jaké Věci budeme Zamykat Já Jsme si již Dovolil Připsat Více Věcí !

Kód: Vybrat vše

    blocks:
        chest:
            enabled: true
            autoRegister: private
        ender_chest:
            enabled: true
            autoRegister: private
        furnace:
            enabled: true
            autoRegister: private
        dispenser:
            enabled: true
            autoRegister: private
        sign:
            enabled: true
            autoRegister: private
        wooden_door:
            enabled: true
            autoRegister: private
        iron_door:
            enabled: true
            autoRegister: private
        trap_door:
            enabled: true
            autoRegister: private
        fence_gate:
            enabled: true
            autoRegister: private
        brewing_stand:
            enabled: true
            autoRegister: private
        enchantment_table:
            enabled: true
            autoRegister: private
        bed:
            enabled: true
            autoRegister: private
        lever:
            enabled: true
            autoRegister: private
        jukebox:
            enabled: true
            autoRegister: private
        workbench:
            enabled: true
            autoRegister: private
        note_block:
            enabled: true
            autoRegister: private
        stone_button:
            enabled: true
            autoRegister: private

Pokud nechcete aby jse Automaticky Zamykaly Změňte toto:

Kód: Vybrat vše

enabled: true

Na:

Kód: Vybrat vše

enabled: false

III. Uprava
Pokud chcete aby jse Iron Door Zamknute nedaly Otevírat řiďte se Instrukcemi.
1.Na FTP najdete složku LWC ve které jsou soubory:
Obrázek
2.Teď přejdeme do souboru doors.yml a upravíme ho takto:
Před:

Kód: Vybrat vše

doors:
    # Enable the opening of Iron Doors when you click on them
    enabled: true
   
    # If true, double doors will open, presuming they are both protected
    # and you can access both
    doubleDoors: true

    # Actions:
    #         toggle: the door will just open if it's closed, or close if it's opened. Will not auto close.
    #   openAndClose: the door will automatically close after <interval>. If it was already opened, it will NOT re-open.
    #
    action: toggle
   
    # The amount of seconds after opening a door for it to close. No effect if openAndClose name is not being used.
    interval: 3

Na:

Kód: Vybrat vše

doors:
    # Enable the opening of Iron Doors when you click on them
    enabled: true
   
    # If true, double doors will open, presuming they are both protected
    # and you can access both
    doubleDoors: false

    # Actions:
    #         toggle: the door will just open if it's closed, or close if it's opened. Will not auto close.
    #   openAndClose: the door will automatically close after <interval>. If it was already opened, it will NOT re-open.
    #
    action: toggle
   
    # The amount of seconds after opening a door for it to close. No effect if openAndClose name is not being used.
    interval: 3


JDE ZAMYKAT: Obrázek
Pokud bude někde chyba určitě ji napište do komentářů a já jí opravím.

Re: LWC Upravené Zamikání !

Napsal: 31 srp 2012, 10:16
od Shaggy84675
Jen bych chtěl doplnit, že pokud si nastavíte jazyk na cz, tak se přeloží i nápověda k příkazům.
standartně se používá /cprivate /cremove atd.
Ale pokud si to necháte přeložit tak budete mít v nápovědě k příkazům /privatni /verejne atd. a tyto příkazy nefungují!!!

Re: LWC Upravené Zamikání !

Napsal: 31 srp 2012, 10:46
od Sejsel
A taky by nebylo od věci upravit název a první řádky tak, aby byly česky. Zamykání se píše s ypsilonem. V češtině se také nepíše tolik velkých písmen ;). Btw, ty ikony ti nefungují. LWC je bezpečné, pokud nemáš jiné pluginy, které by mohly nějak manipulovat s těmi zamknutými věcmi. Taky není od věci to napojit na MySQL, jede to pak mnohem rychleji a lépe.

Re: LWC Upravené zamykání !

Napsal: 08 pro 2014, 17:25
od MinfasCZE
Jak udělám úplně vlastní zprávy ? jinak díky. :)

Re: LWC Upravené zamykání !

Napsal: 10 pro 2014, 21:01
od MarekBurget
MinfasCZE
vlastne prikazy,spravy, všeličo možné si možeš spraviť pomocou pluginu MyCommands.

Možeš tam spraviť napr. z príkazu /warp VIP, iba /VIp, a portne ich to tam (maly priklad)

:)