2016-03-06 14:45:26 +01:00
|
|
|
# Should ViaVersion check for updates?
|
|
|
|
|
checkforupdates: true
|
2016-03-07 00:22:45 +01:00
|
|
|
# No collide options, these allow you to configure how collision works.
|
|
|
|
|
# Do you want us to prevent collision?
|
|
|
|
|
prevent-collision: true
|
|
|
|
|
# If the above is true, should we automatically team players until you do?
|
|
|
|
|
auto-team: true
|
2016-03-07 23:55:57 +01:00
|
|
|
# When enabled if certain metadata can't be read we won't tell you about it
|
2016-03-09 13:08:21 +01:00
|
|
|
suppress-metadata-errors: false
|
|
|
|
|
# When enabled 1.9 will be able to block by using shields
|
2016-03-09 22:08:50 +01:00
|
|
|
shield-blocking: true
|
|
|
|
|
# Should we enable our hologram patch?
|
|
|
|
|
# If they're in the wrong place enable this
|
|
|
|
|
hologram-patch: false
|
|
|
|
|
# This is the offset, should work as default when enabled.
|
2016-03-09 22:30:43 +01:00
|
|
|
hologram-y: -1
|
|
|
|
|
# Enable player tick simulation, this fixes eating, drinking, nether portals.
|
2016-03-10 14:22:32 +01:00
|
|
|
simulate-pt: true
|
|
|
|
|
# Should we patch boss bars so they work? (Default: true, disable if you're having issues)
|
2016-03-10 16:17:31 +01:00
|
|
|
bossbar-patch: true
|
|
|
|
|
# If your boss bar flickers on 1.9, set this to 'true'. It will keep all boss bars on 100% (not recommended)
|
2016-03-15 20:20:39 +01:00
|
|
|
bossbar-anti-flicker: false
|
|
|
|
|
# This will show the new effect indicator in the top-right corner for 1.9 players.
|
2016-03-22 16:27:39 +01:00
|
|
|
use-new-effect-indicator: true
|
2016-04-12 13:01:37 +02:00
|
|
|
# Show the new death messages for 1.9 on the death screen
|
|
|
|
|
use-new-deathmessages: false
|
2016-03-22 16:27:39 +01:00
|
|
|
# This will suppress the following error: 'Unable to get entity for ID: xxxx'
|
|
|
|
|
# This error message means one of you plugins is sending bad packets!
|
2016-04-13 17:54:18 +02:00
|
|
|
suppress-entityid-errors: false
|
|
|
|
|
# Our patch for block breaking issue, if you have issues with block updates then disable this.
|
2016-04-17 01:52:35 +02:00
|
|
|
block-break-patch: true
|
|
|
|
|
# Should we cache our items, this will prevent server from being lagged out, however the cost is a constant task caching items
|
2016-04-17 13:55:18 +02:00
|
|
|
item-cache: true
|
|
|
|
|
# Anti-Cheat, Packets Per Second (PPS) limiter
|
|
|
|
|
# Clients by default send around 20-90 packets per second.
|
|
|
|
|
|
|
|
|
|
# What is the maximum per second a client can send
|
|
|
|
|
# Use -1 to disable.
|
|
|
|
|
max-pps: 400
|
|
|
|
|
max-pps-kick-msg: "You are sending too many packets!"
|
|
|
|
|
|
|
|
|
|
# We can also kick them if over a period they send over a threshold a certain amount of times.
|
|
|
|
|
|
|
|
|
|
# Period to track (in seconds)
|
|
|
|
|
# Use -1 to disable.
|
|
|
|
|
tracking-period: 6
|
|
|
|
|
# How many packets per second counts as a warning
|
|
|
|
|
tracking-warning-pps: 120
|
|
|
|
|
# How many warnings over the interval can we have
|
|
|
|
|
# This can never be higher than "tracking-interval"
|
|
|
|
|
tracking-max-warnings: 4
|
|
|
|
|
tracking-max-kick-msg: "You are sending too many packets, :("
|
