[POMOC] Blokada lwc dla graczy

[PhoenixD123]

Siema jak zablokować możliwość blokowania skrzyń graczom ?

[JodaMinecraft]

Usuń im z permission:

- lwc.protect

[Shоgun]

Skasuj im permissions do lwc, albo jeżeli chodzi o automatyczne zabezpieczanie to je wyłącz.

[PhoenixD123]

Jak wyłączyć automatyczne blokowanie ?

[Shоgun]

Daj congif LWC to Ci pokaże

[PhoenixD123]

Daj congif LWC to Ci pokaże

To chyba to:

# 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: AUTOMATIC
# "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
# 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
   # 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
modes:
   droptransfer:
    enabled: true
   persist:
    enabled: true

[TheApek424]

# Core configurable options for LWCcore:	# 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 operatesupdater:	# The branch to select updates from	# STABLE or BLEEDING_EDGE	branch: STABLE	# When to retrieve updates	# Either AUTOMATIC or MANUAL	method: AUTOMATIC# "Fun" optionsoptional:	# 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# Database information for LWCdatabase:	# 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	# 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		furnace:			enabled: true		dispenser:			enabled: true		sign:			enabled: true		wooden_door:			enabled: true		iron_door:			enabled: true		trap_door:			enabled: truemodes:	droptransfer:		enabled: true	persist:		enabled: true

 

Proszę bardzo, wystarczyło pousuwać linijkę z "autoRegister: private"

Pozdrawiam, Apek424

[PhoenixD123]

Ok juz nie blokuje automatycznie ale w permission w randze gracz nic nie mam a nadal gracze moga używać /cprivate

[PhoenixD123]

pomocy

[Lexton]

napisze ktoś w końcu rozwiazanie tego?

[patryk1653]

sprawdz czy oprocz lwc.protect nie masz tez jakichs incyh lwc.(*) w permissions:

np tego:

lwc.create

[Lexton]

nie mam.

Używam essential Groupmenager 2.9.1 oraz LWC v4.1.1

[Flliko]

To może być problem bo LWC działa bez permissions. Testowałem.

[Lexton]

Czyli co mam zrobić. A da się zrobić jakiś limit bo kiedyś wiem ,że się dało ?

[Noobel]

plugin.yml zmien z default na false przy lwc.protect

[Lexton]

Gdzie tego mam szukac?

[Lexton]

odpisze ktoś w końcu?

[K4P1K]

blocks:
	    chest:
			    enabled: true
			    autoRegister: private
	    furnace:
			    enabled: true
			    autoRegister: private
	    dispenser:
			    enabled: true
			    autoRegister: private
	    sign:
			    enabled: true
			    autoRegister: private

 

jeśli tego nie zrobiłeś, to pozamieniaj wszystkie "true" na "false". Zrobiłem to za ciebie, skopiuj i zobacz, czy chodzi.

 

blocks:
	    chest:
			    enabled: true
			    autoRegister: false
	    furnace:
			    enabled: true
			    autoRegister: false
	    dispenser:
			    enabled: true
			    autoRegister: false
	    sign:
			    enabled: true
			    autoRegister: false

[Lexton]

Dzięk, że odpisałeś.

Tak tylko co mi da to ,że automatycznie skrzynia się nie zablokuje ale gracz se wpisze crpivate i będzie miał zablokowaną ;-(