-
Notifications
You must be signed in to change notification settings - Fork 17
/
core.yml
183 lines (141 loc) · 7.02 KB
/
core.yml
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
# 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.'
# If you will be notified of LWC updates
updateNotifier: true
# "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 interval between pinging the MySQL server to keep it alive (in seconds)
ping_interval: 300
# 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
# Set to true to prevent users from modifying a protection they own of a certain type (or any protection).
# ONLY lwc admins will be able to modify the protection
readonly-modify: false
# Set to true to prevent users from removing a protection they own of a certain type (or any protection).
# ONLY lwc admins will be able to modify the protection
readonly-remove: 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