|
| 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 | +# Docs - https://docs.viaversion.com |
| 6 | +# |
| 7 | +#----------------------------------------------------------# |
| 8 | +# GLOBAL OPTIONS # |
| 9 | +#----------------------------------------------------------# |
| 10 | +# |
| 11 | +# Should ViaVersion check for updates? |
| 12 | +check-for-updates: false |
| 13 | +# Send the supported versions with the Status (Ping) response packet |
| 14 | +send-supported-versions: true |
| 15 | +# Easier to configure alternative to 'block-protocols'. Uses readable version strings with possible '<' and '>' prefixes. |
| 16 | +# An example to block 1.16.4, everything below 1.16, as well as everything above 1.17.1 would be: ["<1.16", "1.16.4", ">1.17.1"] |
| 17 | +# You can use both this and the block-protocols option at the same time as well. |
| 18 | +block-versions: [] |
| 19 | +# Block specific Minecraft protocol version numbers. |
| 20 | +# List of all Minecraft protocol versions: https://minecraft.wiki/w/Protocol_version, or use a generator: https://via.krusic22.com |
| 21 | +block-protocols: [] |
| 22 | +# Change the blocked disconnect message |
| 23 | +block-disconnect-msg: You are using an unsupported Minecraft version! |
| 24 | +# Whether to log more info about kicks due to blocked protocol versions to the console. |
| 25 | +log-blocked-joins: false |
| 26 | +# If you use ProtocolLib, we can't reload without kicking the players. |
| 27 | +# (We don't suggest using reload either, use a plugin manager) |
| 28 | +# You can customize the message we kick people with if you use ProtocolLib here. |
| 29 | +reload-disconnect-msg: Server reload, please rejoin! |
| 30 | +# We warn when there's an error converting item/block or component/nbt data over versions, should we suppress these? (Only suggested if spamming) |
| 31 | +suppress-conversion-warnings: false |
| 32 | +# This can be disabled for debugging purposes if text in chat/entities/items shows an error tag. |
| 33 | +suppress-text-component-conversion-warnings: true |
| 34 | +# |
| 35 | +#----------------------------------------------------------# |
| 36 | +# GLOBAL PACKET LIMITER # |
| 37 | +#----------------------------------------------------------# |
| 38 | +# Packets Per Second (PPS) and kilobyte packet size limiters. |
| 39 | +# Setting 'max-per-second' or 'sustained-max-per-second' to -1 will disable the individual limit. |
| 40 | +# Kick messages may include the %pps or %bps placeholders respectively, though they are more intended for debugging purposes. |
| 41 | +# |
| 42 | +# Limits the amount of packets sent per second. |
| 43 | +# Clients by default send around 20-90 packets per second. |
| 44 | +packet-limiter: |
| 45 | + enabled: true |
| 46 | + # The maximum packets a client can send per second. |
| 47 | + max-per-second: 500 |
| 48 | + max-per-second-kick-message: You are sending too many packets! |
| 49 | + # |
| 50 | + # We can also kick them if they repeatedly send too many packets over a longer period of time. |
| 51 | + # E.g. if a player sends over 150 packets per second for 4 out of 7 seconds, we kick them. |
| 52 | + # The maximum packets per second a client can send over a longer period of time. |
| 53 | + sustained-max-per-second: 150 |
| 54 | + # Period to track in seconds. |
| 55 | + sustained-period-seconds: 7 |
| 56 | + # The number of seconds within the interval that the client can exceed the limit before being kicked. |
| 57 | + sustained-threshold: 4 |
| 58 | + sustained-kick-message: You are sending too many packets! |
| 59 | +# Limits the size of packets in kilobytes sent per second. |
| 60 | +packet-size-limiter: |
| 61 | + enabled: false |
| 62 | + max-per-second: -1 |
| 63 | + max-per-second-kick-message: You are sending too large packets! |
| 64 | + sustained-max-per-second: -1 |
| 65 | + sustained-period-seconds: 5 |
| 66 | + sustained-threshold: 3 |
| 67 | + sustained-kick-message: You are sending too large packets, :( |
| 68 | +# |
| 69 | +#----------------------------------------------------------# |
| 70 | +# MULTIPLE VERSIONS OPTIONS # |
| 71 | +#----------------------------------------------------------# |
| 72 | +# |
| 73 | +# Should we enable our hologram patch? |
| 74 | +# If they're in the wrong place, enable this |
| 75 | +hologram-patch: false |
| 76 | +# This is the offset, should work as default when enabled. |
| 77 | +hologram-y: -0.96 |
| 78 | +# Should we disable piston animation for 1.11/1.11.1 clients? |
| 79 | +# In some cases, when firing lots of pistons, it crashes them. |
| 80 | +piston-animation-patch: false |
| 81 | +# Should we use prefix for team color on 1.13 and above clients? |
| 82 | +team-colour-fix: true |
| 83 | +# 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. |
| 84 | +disable-1_13-auto-complete: false |
| 85 | +# 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 |
| 86 | +1_13-tab-complete-delay: 0 |
| 87 | +# For 1.13 clients the smallest (1 layer) snow doesn't have collisions, this will send these as 2 snowlayers for 1.13+ clients to prevent them bugging through them |
| 88 | +fix-low-snow-collision: false |
| 89 | +# 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 |
| 90 | +fix-infested-block-breaking: true |
| 91 | +# 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. |
| 92 | +truncate-1_14-books: false |
| 93 | +# Fixes 1.14+ clients on sub 1.14 servers having a light value of 0 for non-full blocks. |
| 94 | +fix-non-full-blocklight: true |
| 95 | +# Fixes walk animation not shown when health is set to Float.NaN |
| 96 | +fix-1_14-health-nan: true |
| 97 | +# Should 1.15+ clients respawn instantly / without showing a death screen? |
| 98 | +use-1_15-instant-respawn: false |
| 99 | +# |
| 100 | +# Enable serverside block-connections for 1.13+ clients - all the options in this section are built around this option |
| 101 | +serverside-blockconnections: true |
| 102 | +# When activated, only the most important blocks are stored in the blockstorage. (fences, glass panes etc. won't connect to solid blocks) |
| 103 | +reduce-blockstorage-memory: false |
| 104 | +# When activated with serverside-blockconnections, flower parts with blocks above will be sent as stems |
| 105 | +# Useful for lobbyservers where users can't build and those stems are used decoratively |
| 106 | +flowerstem-when-block-above: false |
| 107 | +# Vines that are not connected to blocks will be mapped to air, else 1.13+ would still be able to climb up on them. |
| 108 | +vine-climb-fix: false |
| 109 | +# |
| 110 | +# Ignores incoming plugin channel messages of 1.16+ clients with channel names longer than 32 characters. |
| 111 | +# CraftBukkit had this limit hardcoded until 1.16, so we have to assume any server/proxy might have this arbitrary check present. |
| 112 | +ignore-long-1_16-channel-names: true |
| 113 | +# |
| 114 | +# Force 1.17+ client to accept the server resource pack; they will automatically disconnect if they decline. |
| 115 | +forced-use-1_17-resource-pack: false |
| 116 | +# The message to be displayed at the prompt when the 1.17+ client receives the server resource pack. |
| 117 | +resource-pack-1_17-prompt: '' |
| 118 | +# |
| 119 | +# Caches light until chunks are unloaded to allow later chunk update packets as opposed to instantly uncaching when the first chunk data is sent. |
| 120 | +# Only disable this if you know what you are doing. |
| 121 | +cache-1_17-light: true |
| 122 | +# |
| 123 | +# Get the world names which should be returned for each vanilla dimension |
| 124 | +map-1_16-world-names: |
| 125 | + overworld: minecraft:overworld |
| 126 | + nether: minecraft:the_nether |
| 127 | + end: minecraft:the_end |
| 128 | +# |
| 129 | +# If disabled, tamed cats will be displayed as ocelots to 1.14+ clients on 1.13 servers. Otherwise, ocelots (tamed and untamed) will be displayed as cats. |
| 130 | +translate-ocelot-to-cat: false |
| 131 | +# |
| 132 | +# Determines the value sent to 1.19+ clients on join if currently not accessible by ViaVersion. |
| 133 | +# It is not recommended to fake this value if your server is running 1.19 or later, as 1.20.5 have stricter chat handling and may get kicked otherwise. |
| 134 | +enforce-secure-chat: false |
| 135 | +# |
| 136 | +# Handles items with invalid count values (higher than max stack size) on 1.20.3 servers. |
| 137 | +handle-invalid-item-count: false |
| 138 | +# |
| 139 | +# Hides scoreboard numbers for 1.20.3+ clients on older server versions. |
| 140 | +hide-scoreboard-numbers: false |
| 141 | +# |
| 142 | +# Fixes 1.21+ clients on 1.20.5 servers placing water/lava buckets at the wrong location when moving fast, NOTE: This may cause issues with anti-cheat plugins. |
| 143 | +fix-1_21-placement-rotation: true |
| 144 | +# |
| 145 | +# If enabled, cancel swing packets sent while having an inventory opened on 1.15.2 and below servers. This can cause false positives with anti-cheat plugins. |
| 146 | +cancel-swing-in-inventory: true |
| 147 | +# |
| 148 | +#----------------------------------------------------------# |
| 149 | +# 1.9+ CLIENTS ON 1.8 SERVERS OPTIONS # |
| 150 | +#----------------------------------------------------------# |
| 151 | +# |
| 152 | +# No collide options, these allow you to configure how collision works. |
| 153 | +# Do you want us to prevent collision? |
| 154 | +prevent-collision: true |
| 155 | +# If the above is true, should we automatically team players until you do? |
| 156 | +auto-team: true |
| 157 | +# When enabled if certain entity data can't be read, we won't tell you about it |
| 158 | +suppress-metadata-errors: false |
| 159 | +# When enabled, 1.9+ will be able to block by using shields |
| 160 | +shield-blocking: true |
| 161 | +# If this setting is active, the main hand is used instead of the off-hand to trigger the blocking of the player. |
| 162 | +# With the main hand, the blocking starts way faster. |
| 163 | +# (Requires "show-shield-when-sword-in-hand" to be disabled) |
| 164 | +no-delay-shield-blocking: false |
| 165 | +# If this setting is active, the shield will appear immediately for 1.9+ when you hold a sword in your main hand. |
| 166 | +# The shield disappears when you switch to another item. |
| 167 | +# (Requires "shield-blocking" to be enabled) |
| 168 | +show-shield-when-sword-in-hand: false |
| 169 | +# Enable player tick simulation, this fixes eating, drinking, nether portals. |
| 170 | +simulate-pt: true |
| 171 | +# Should we patch boss bars so they work? (Default: true, disable if you're having issues) |
| 172 | +bossbar-patch: true |
| 173 | +# If your boss bar flickers on 1.9+, set this to 'true'. It will keep all boss bars on 100% (not recommended) |
| 174 | +bossbar-anti-flicker: false |
| 175 | +# This will show the new effect indicator in the top-right corner for 1.9+ players. |
| 176 | +use-new-effect-indicator: true |
| 177 | +# Should we replace extended pistons to fix 1.10.1 (Only on chunk loading)? |
| 178 | +replace-pistons: false |
| 179 | +# What id should we replace with, default is air. (careful of players getting stuck standing on them) |
| 180 | +replacement-piston-id: 0 |
| 181 | +# Fix 1.9+ clients not rendering the far away chunks and improve chunk rendering when moving fast (Increases network usage and decreases client fps slightly) |
| 182 | +chunk-border-fix: false |
| 183 | +# Allows 1.9+ left-handedness (main hand) on 1.8 servers |
| 184 | +left-handed-handling: true |
| 185 | +# Tries to cancel block break/place sounds sent by 1.8 servers to 1.9+ clients to prevent them from playing twice |
| 186 | +cancel-block-sounds: true |
0 commit comments