|
| 1 | +# Thanks for downloading ViaVersion |
| 2 | +# Ensure you look through all these options |
| 3 | +# If you need help: |
| 4 | +# Discord - https://viaversion.com/discord |
| 5 | +# viaversion.com - Discussion tab |
| 6 | +# Docs - https://docs.viaversion.com/display/VIAVERSION/Configuration |
| 7 | +# |
| 8 | +# ----------------------------------------------------------# |
| 9 | +# GLOBAL OPTIONS # |
| 10 | +# ----------------------------------------------------------# |
| 11 | +# |
| 12 | +# Should ViaVersion check for updates? |
| 13 | +checkforupdates: true |
| 14 | +# Send the supported versions with the Status (Ping) response packet |
| 15 | +send-supported-versions: false |
| 16 | +# Block specific Minecraft protocols that ViaVersion allows |
| 17 | +# List of all Minecraft protocol versions: http://wiki.vg/Protocol_version_numbers or use a generator: https://via.krusic22.com |
| 18 | +block-protocols: [] |
| 19 | +# Change the blocked disconnect message |
| 20 | +block-disconnect-msg: You are using an unsupported Minecraft version! |
| 21 | +# If you use ProtocolLib, we can't reload without kicking the players. |
| 22 | +# (We don't suggest using reload either, use a plugin manager) |
| 23 | +# You can customise the message we kick people with if you use ProtocolLib here. |
| 24 | +reload-disconnect-msg: Server reload, please rejoin! |
| 25 | +# We warn when there's a error converting item and block data over versions, should we suppress these? (Only suggested if spamming) |
| 26 | +suppress-conversion-warnings: false |
| 27 | +# |
| 28 | +# ----------------------------------------------------------# |
| 29 | +# GLOBAL PACKET LIMITER # |
| 30 | +# ----------------------------------------------------------# |
| 31 | +# |
| 32 | +# |
| 33 | +# Packets Per Second (PPS) limiter (Use -1 on max-pps and tracking-period to disable) |
| 34 | +# Clients by default send around 20-90 packets per second. |
| 35 | +# |
| 36 | +# What is the maximum per second a client can send (Use %pps to display their pps) |
| 37 | +# Use -1 to disable. |
| 38 | +max-pps: 800 |
| 39 | +max-pps-kick-msg: You are sending too many packets! |
| 40 | +# |
| 41 | +# We can also kick them if over a period they send over a threshold a certain amount of times. |
| 42 | +# |
| 43 | +# Period to track (in seconds) |
| 44 | +# Use -1 to disable. |
| 45 | +tracking-period: 6 |
| 46 | +# How many packets per second counts as a warning |
| 47 | +tracking-warning-pps: 120 |
| 48 | +# How many warnings over the interval can we have |
| 49 | +# This can never be higher than "tracking-period" |
| 50 | +tracking-max-warnings: 4 |
| 51 | +tracking-max-kick-msg: You are sending too many packets, :( |
| 52 | +# |
| 53 | +# ----------------------------------------------------------# |
| 54 | +# MULTIPLE VERSIONS OPTIONS # |
| 55 | +# ----------------------------------------------------------# |
| 56 | +# |
| 57 | +# Should we enable our hologram patch? |
| 58 | +# If they're in the wrong place enable this |
| 59 | +hologram-patch: false |
| 60 | +# This is the offset, should work as default when enabled. |
| 61 | +hologram-y: -0.96 |
| 62 | +# Should we disable piston animation for 1.11/1.11.1 clients? |
| 63 | +# In some cases when firing lots of pistons it crashes them. |
| 64 | +piston-animation-patch: false |
| 65 | +# Should we fix nbt for 1.12 and above clients in chat messages (causes invalid item) |
| 66 | +chat-nbt-fix: true |
| 67 | +# Should we use prefix for team colour on 1.13 and above clients |
| 68 | +team-colour-fix: true |
| 69 | +# 1.13 introduced new auto complete which can trigger "Kicked for spamming" for servers older than 1.13, the following option will disable it completely. |
| 70 | +disable-1_13-auto-complete: false |
| 71 | +# The following option will delay the tab complete request in x ticks if greater than 0, if other tab-complete is received, the previous is cancelled |
| 72 | +1_13-tab-complete-delay: 0 |
| 73 | +# For 1.13 clients the smallest (1 layer) snow doesn't have collision, this will send these as 2 snowlayers for 1.13+ clients to prevent them bugging through them |
| 74 | +fix-low-snow-collision: false |
| 75 | +# Infested blocks are instantly breakable for 1.13+ clients, resulting in them being unable to break them on sub 1.13 servers. This remaps them to their normal stone variants |
| 76 | +fix-infested-block-breaking: true |
| 77 | +# In 1.14 the client page limit has been upped to 100 (from 50). Some anti-exploit plugins ban when clients go higher than 50. This option cuts edited books to 50 pages. |
| 78 | +truncate-1_14-books: false |
| 79 | +# Fixes 1.14+ clients on sub 1.14 servers having a light value of 0 for non full blocks. |
| 80 | +fix-non-full-blocklight: true |
| 81 | +# Fixes walk animation not shown when health is set to Float.NaN |
| 82 | +fix-1_14-health-nan: true |
| 83 | +# Should 1.15+ clients respawn instantly / without showing a death screen? |
| 84 | +use-1_15-instant-respawn: false |
| 85 | +# |
| 86 | +# Enable serverside block-connections for 1.13+ clients - all of the options in this section are built around this option |
| 87 | +serverside-blockconnections: true |
| 88 | +# When activated, only the most important blocks are stored in the blockstorage. (fences, glass panes etc. won't connect to solid blocks) |
| 89 | +reduce-blockstorage-memory: false |
| 90 | +# When activated with serverside-blockconnections, flower parts with blocks above will be sent as stems |
| 91 | +# Useful for lobbyservers where users can't build and those stems are used decoratively |
| 92 | +flowerstem-when-block-above: false |
| 93 | +# Vines that are not connected to blocks will be mapped to air, else 1.13+ would still be able to climb up on them. |
| 94 | +vine-climb-fix: false |
| 95 | +# |
| 96 | +# Ignores incoming plugin channel messages of 1.16+ clients with channel names longer than 32 characters. |
| 97 | +# CraftBukkit had this limit hardcoded until 1.16, so we have to assume any server/proxy might have this arbitrary check present. |
| 98 | +ignore-long-1_16-channel-names: true |
| 99 | +# |
| 100 | +# Force 1.17+ client to accept the server resource pack; they will automatically disconnect if they decline. |
| 101 | +forced-use-1_17-resource-pack: false |
| 102 | +# The message to be displayed at the prompt when the 1.17+ client receives the server resource pack. |
| 103 | +resource-pack-1_17-prompt: '' |
| 104 | +# |
| 105 | +# ----------------------------------------------------------# |
| 106 | +# 1.9+ CLIENTS ON 1.8 SERVERS OPTIONS # |
| 107 | +# ----------------------------------------------------------# |
| 108 | +# |
| 109 | +# No collide options, these allow you to configure how collision works. |
| 110 | +# Do you want us to prevent collision? |
| 111 | +prevent-collision: true |
| 112 | +# If the above is true, should we automatically team players until you do? |
| 113 | +auto-team: true |
| 114 | +# When enabled if certain metadata can't be read we won't tell you about it |
| 115 | +suppress-metadata-errors: false |
| 116 | +# When enabled 1.9+ will be able to block by using shields |
| 117 | +shield-blocking: true |
| 118 | +# If this setting is active, the main hand is used instead of the off hand to trigger the blocking of the player. |
| 119 | +# With the main hand the blocking starts way faster. |
| 120 | +# (Requires "show-shield-when-sword-in-hand" to be disabled) |
| 121 | +no-delay-shield-blocking: false |
| 122 | +# If this setting is active, the shield will appear immediately for 1.9+ when you hold a sword in your main hand. |
| 123 | +# The shield disappears when you switch to another item. |
| 124 | +# (Requires "shield-blocking" to be enabled) |
| 125 | +show-shield-when-sword-in-hand: false |
| 126 | +# Enable player tick simulation, this fixes eating, drinking, nether portals. |
| 127 | +simulate-pt: true |
| 128 | +# Should we patch boss bars so they work? (Default: true, disable if you're having issues) |
| 129 | +bossbar-patch: true |
| 130 | +# If your boss bar flickers on 1.9+, set this to 'true'. It will keep all boss bars on 100% (not recommended) |
| 131 | +bossbar-anti-flicker: false |
| 132 | +# This will show the new effect indicator in the top-right corner for 1.9+ players. |
| 133 | +use-new-effect-indicator: true |
| 134 | +# Show the new death messages for 1.9+ on the death screen |
| 135 | +use-new-deathmessages: true |
| 136 | +# Should we cache our items, this will prevent server from being lagged out, however the cost is a constant task caching items |
| 137 | +item-cache: true |
| 138 | +# Should we replace extended pistons to fix 1.10.1 (Only on chunk load) |
| 139 | +replace-pistons: false |
| 140 | +# What id should we replace with, default is air. (careful of players getting stuck standing on them) |
| 141 | +replacement-piston-id: 0 |
| 142 | +# Force the string -> json transform |
| 143 | +force-json-transform: false |
| 144 | +# Minimize the cooldown animation in 1.8 servers |
| 145 | +minimize-cooldown: true |
| 146 | +# Allows 1.9+ left-handedness (main hand) on 1.8 servers |
| 147 | +left-handed-handling: true |
0 commit comments