Обновление компонентов
This commit is contained in:
none
parent
515aa1050c
commit
b2e131156f
BIN
BungeeCord.jar
BIN
BungeeCord.jar
Binary file not shown.
41
config.yml
41
config.yml
@ -1,4 +1,3 @@
|
||||
enforce_secure_profile: false
|
||||
listeners:
|
||||
- query_port: 25565
|
||||
motd: '&cТестовый bungee-сервер'
|
||||
@ -15,8 +14,10 @@ listeners:
|
||||
max_players: 5
|
||||
tab_size: 60
|
||||
force_default_server: true
|
||||
remote_ping_cache: -1
|
||||
network_compression_threshold: 256
|
||||
groups:
|
||||
md_5:
|
||||
- admin
|
||||
connection_throttle_limit: 3
|
||||
permissions:
|
||||
default:
|
||||
- bungeecord.command.server
|
||||
@ -27,26 +28,26 @@ permissions:
|
||||
- bungeecord.command.ip
|
||||
- bungeecord.command.reload
|
||||
- bungeecord.command.kick
|
||||
log_pings: true
|
||||
connection_throttle_limit: 3
|
||||
server_connect_timeout: 5000
|
||||
timeout: 30000
|
||||
player_limit: -1
|
||||
prevent_proxy_connections: false
|
||||
ip_forward: false
|
||||
groups:
|
||||
md_5:
|
||||
- admin
|
||||
remote_ping_timeout: 5000
|
||||
connection_throttle: 4000
|
||||
log_commands: false
|
||||
stats: 2063a89d-bf28-4bb7-a8c1-56b6dd57e241
|
||||
network_compression_threshold: 256
|
||||
timeout: 30000
|
||||
log_pings: true
|
||||
prevent_proxy_connections: false
|
||||
connection_throttle: 4000
|
||||
enforce_secure_profile: false
|
||||
online_mode: false
|
||||
forge_support: false
|
||||
disabled_commands:
|
||||
- disabledcommandhere
|
||||
stats: 2063a89d-bf28-4bb7-a8c1-56b6dd57e241
|
||||
ip_forward: false
|
||||
servers:
|
||||
lobby:
|
||||
motd: '&1Just another BungeeCord - Forced Host'
|
||||
address: 135.181.170.94:25630
|
||||
address: YOUR_ADRESS.com
|
||||
restricted: false
|
||||
reject_transfers: false
|
||||
server_connect_timeout: 5000
|
||||
forge_support: false
|
||||
disabled_commands:
|
||||
- disabledcommandhere
|
||||
remote_ping_cache: -1
|
||||
remote_ping_timeout: 5000
|
||||
player_limit: -1
|
||||
|
||||
Binary file not shown.
Binary file not shown.
Binary file not shown.
Binary file not shown.
Binary file not shown.
Binary file not shown.
@ -1,5 +1,5 @@
|
||||
#HSQL Database Engine 2.4.0
|
||||
#Sat Oct 14 15:03:44 MSK 2023
|
||||
#Sat Mar 09 14:32:18 MSK 2024
|
||||
version=2.4.0
|
||||
modified=no
|
||||
tx_timestamp=0
|
||||
|
||||
Binary file not shown.
BIN
plugins/ViaBackwards-4.9.2.jar
Normal file
BIN
plugins/ViaBackwards-4.9.2.jar
Normal file
Binary file not shown.
Binary file not shown.
BIN
plugins/ViaRewind-3.0.6.jar
Normal file
BIN
plugins/ViaRewind-3.0.6.jar
Normal file
Binary file not shown.
Binary file not shown.
@ -2,7 +2,6 @@
|
||||
# Ensure you look through all these options
|
||||
# If you need help:
|
||||
# Discord - https://viaversion.com/discord
|
||||
# viaversion.com - Discussion tab
|
||||
# Docs - https://docs.viaversion.com/display/VIAVERSION/Configuration
|
||||
#
|
||||
#----------------------------------------------------------#
|
||||
@ -10,24 +9,26 @@
|
||||
#----------------------------------------------------------#
|
||||
#
|
||||
# Should ViaVersion check for updates?
|
||||
checkforupdates: true
|
||||
# Send the supported versions with the Status (Ping) response packet
|
||||
send-supported-versions: false
|
||||
# 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
|
||||
1_13-tab-complete-delay: 0
|
||||
#
|
||||
# Force-update 1.19.4+ player's inventory when they try to swap armor in a pre-occupied slot.
|
||||
armor-toggle-fix: true
|
||||
# If the above is true, should we automatically team players until you do?
|
||||
auto-team: true
|
||||
# Change the blocked disconnect message
|
||||
block-disconnect-msg: You are using an unsupported Minecraft version!
|
||||
# Block specific Minecraft protocol version numbers.
|
||||
# List of all Minecraft protocol versions: https://wiki.vg/Protocol_version_numbers, or use a generator: https://via.krusic22.com
|
||||
block-protocols: []
|
||||
# Easier to configure alternative to 'block-protocols'. Uses readable version strings with possible '<' and '>' prefixes.
|
||||
# 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"]
|
||||
# You can use both this and the block-protocols option at the same time as well.
|
||||
block-versions: []
|
||||
# Block specific Minecraft protocol version numbers.
|
||||
# List of all Minecraft protocol versions: https://wiki.vg/Protocol_version_numbers, or use a generator: https://via.krusic22.com
|
||||
block-protocols: []
|
||||
# Change the blocked disconnect message
|
||||
block-disconnect-msg: You are using an unsupported Minecraft version!
|
||||
# If you use ProtocolLib, we can't reload without kicking the players.
|
||||
# (We don't suggest using reload either, use a plugin manager)
|
||||
# You can customise the message we kick people with if you use ProtocolLib here.
|
||||
reload-disconnect-msg: Server reload, please rejoin!
|
||||
# We warn when there's an error converting item and block data over versions, should we suppress these? (Only suggested if spamming)
|
||||
suppress-conversion-warnings: false
|
||||
# If your boss bar flickers on 1.9+, set this to 'true'. It will keep all boss bars on 100% (not recommended)
|
||||
bossbar-anti-flicker: false
|
||||
# Should we patch boss bars so they work? (Default: true, disable if you're having issues)
|
||||
bossbar-patch: true
|
||||
#
|
||||
#----------------------------------------------------------#
|
||||
# BUNGEE OPTIONS #
|
||||
@ -48,10 +49,54 @@ bungee-ping-save: true
|
||||
# The format for the following is:
|
||||
# servername: protocolversion
|
||||
# You can find protocol ids on https://wiki.vg/Protocol_version_numbers
|
||||
# It will fallback to the default option if none found.
|
||||
# It will use the default option if none found.
|
||||
bungee-servers:
|
||||
default: 47
|
||||
lobby: 763
|
||||
lobby: 764
|
||||
#
|
||||
# Caches light until chunks are unloaded to allow subsequent chunk update packets as opposed to instantly uncaching when the first chunk data is sent.
|
||||
# Only disable this if you know what you are doing.
|
||||
cache-1_17-light: true
|
||||
# Should we fix nbt for 1.12 and above clients in chat messages (causes invalid item)
|
||||
chat-nbt-fix: true
|
||||
checkforupdates: true
|
||||
# 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)
|
||||
chunk-border-fix: false
|
||||
# 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.
|
||||
disable-1_13-auto-complete: false
|
||||
# Fixes walk animation not shown when health is set to Float.NaN
|
||||
fix-1_14-health-nan: true
|
||||
# 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
|
||||
fix-infested-block-breaking: true
|
||||
# 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
|
||||
fix-low-snow-collision: false
|
||||
# Fixes 1.14+ clients on sub 1.14 servers having a light value of 0 for non-full blocks.
|
||||
fix-non-full-blocklight: true
|
||||
# When activated with serverside-blockconnections, flower parts with blocks above will be sent as stems
|
||||
# Useful for lobbyservers where users can't build and those stems are used decoratively
|
||||
flowerstem-when-block-above: false
|
||||
# Force the string -> json transform
|
||||
force-json-transform: false
|
||||
#
|
||||
# Force 1.17+ client to accept the server resource pack; they will automatically disconnect if they decline.
|
||||
forced-use-1_17-resource-pack: false
|
||||
# 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.
|
||||
hologram-y: -0.96
|
||||
#
|
||||
# Ignores incoming plugin channel messages of 1.16+ clients with channel names longer than 32 characters.
|
||||
# CraftBukkit had this limit hardcoded until 1.16, so we have to assume any server/proxy might have this arbitrary check present.
|
||||
ignore-long-1_16-channel-names: true
|
||||
# Allows 1.9+ left-handedness (main hand) on 1.8 servers
|
||||
left-handed-handling: true
|
||||
#
|
||||
# Get the world names which should be returned for each vanilla dimension
|
||||
map-1_16-world-names:
|
||||
overworld: minecraft:overworld
|
||||
nether: minecraft:the_nether
|
||||
end: minecraft:the_end
|
||||
#
|
||||
#----------------------------------------------------------#
|
||||
# GLOBAL PACKET LIMITER #
|
||||
@ -65,88 +110,15 @@ bungee-servers:
|
||||
# Use -1 to disable.
|
||||
max-pps: 800
|
||||
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-period"
|
||||
tracking-max-warnings: 4
|
||||
tracking-max-kick-msg: You are sending too many packets, :(
|
||||
#
|
||||
#----------------------------------------------------------#
|
||||
# MULTIPLE VERSIONS OPTIONS #
|
||||
#----------------------------------------------------------#
|
||||
#
|
||||
# Whether to make sure ViaVersion's UserConnection object is already available in the PlayerJoinEvent.
|
||||
# You may disable this for faster startup/join time if you are 100% sure no plugin requires this.
|
||||
register-userconnections-on-join: 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.
|
||||
hologram-y: -0.96
|
||||
# Minimize the cooldown animation in 1.8 servers
|
||||
minimize-cooldown: true
|
||||
# If this setting is active, the main hand is used instead of the off-hand to trigger the blocking of the player.
|
||||
# With the main hand the blocking starts way faster.
|
||||
# (Requires "show-shield-when-sword-in-hand" to be disabled)
|
||||
no-delay-shield-blocking: false
|
||||
# Should we disable piston animation for 1.11/1.11.1 clients?
|
||||
# In some cases when firing lots of pistons it crashes them.
|
||||
piston-animation-patch: false
|
||||
# Should we fix nbt for 1.12 and above clients in chat messages (causes invalid item)
|
||||
chat-nbt-fix: true
|
||||
# Should we use prefix for team colour on 1.13 and above clients
|
||||
team-colour-fix: true
|
||||
# 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.
|
||||
disable-1_13-auto-complete: false
|
||||
# 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
|
||||
1_13-tab-complete-delay: 0
|
||||
# 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
|
||||
fix-low-snow-collision: false
|
||||
# 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
|
||||
fix-infested-block-breaking: true
|
||||
# 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.
|
||||
truncate-1_14-books: false
|
||||
# Fixes 1.14+ clients on sub 1.14 servers having a light value of 0 for non-full blocks.
|
||||
fix-non-full-blocklight: true
|
||||
# Fixes walk animation not shown when health is set to Float.NaN
|
||||
fix-1_14-health-nan: true
|
||||
# Should 1.15+ clients respawn instantly / without showing a death screen?
|
||||
use-1_15-instant-respawn: false
|
||||
#
|
||||
# Enable serverside block-connections for 1.13+ clients - all the options in this section are built around this option
|
||||
serverside-blockconnections: true
|
||||
# When activated, only the most important blocks are stored in the blockstorage. (fences, glass panes etc. won't connect to solid blocks)
|
||||
reduce-blockstorage-memory: false
|
||||
# When activated with serverside-blockconnections, flower parts with blocks above will be sent as stems
|
||||
# Useful for lobbyservers where users can't build and those stems are used decoratively
|
||||
flowerstem-when-block-above: false
|
||||
# Vines that are not connected to blocks will be mapped to air, else 1.13+ would still be able to climb up on them.
|
||||
vine-climb-fix: false
|
||||
#
|
||||
# Ignores incoming plugin channel messages of 1.16+ clients with channel names longer than 32 characters.
|
||||
# CraftBukkit had this limit hardcoded until 1.16, so we have to assume any server/proxy might have this arbitrary check present.
|
||||
ignore-long-1_16-channel-names: true
|
||||
#
|
||||
# Force 1.17+ client to accept the server resource pack; they will automatically disconnect if they decline.
|
||||
forced-use-1_17-resource-pack: false
|
||||
# The message to be displayed at the prompt when the 1.17+ client receives the server resource pack.
|
||||
resource-pack-1_17-prompt: ''
|
||||
#
|
||||
# Caches light until chunks are unloaded to allow subsequent chunk update packets as opposed to instantly uncaching when the first chunk data is sent.
|
||||
# Only disable this if you know what you are doing.
|
||||
cache-1_17-light: true
|
||||
#
|
||||
# 1.19 chat type formats used for 1.19.1+ clients.
|
||||
chat-types-1_19:
|
||||
chat.type.text: <%s> %s
|
||||
chat.type.announcement: '[%s] %s'
|
||||
commands.message.display.incoming: '%s whispers to you: %s'
|
||||
chat.type.team.text: '%s <%s> %s'
|
||||
chat.type.emote: '* %s %s'
|
||||
#
|
||||
# Force-update 1.19.4+ player's inventory when they try to swap armor in a pre-occupied slot.
|
||||
armor-toggle-fix: true
|
||||
#
|
||||
#----------------------------------------------------------#
|
||||
# 1.9+ CLIENTS ON 1.8 SERVERS OPTIONS #
|
||||
@ -155,44 +127,64 @@ armor-toggle-fix: true
|
||||
# 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
|
||||
# When enabled if certain metadata can't be read we won't tell you about it
|
||||
suppress-metadata-errors: false
|
||||
# When activated, only the most important blocks are stored in the blockstorage. (fences, glass panes etc. won't connect to solid blocks)
|
||||
reduce-blockstorage-memory: false
|
||||
#
|
||||
#----------------------------------------------------------#
|
||||
# MULTIPLE VERSIONS OPTIONS #
|
||||
#----------------------------------------------------------#
|
||||
#
|
||||
# Whether to make sure ViaVersion's UserConnection object is already available in the PlayerJoinEvent.
|
||||
# You may disable this for faster startup/join time if you are 100% sure no plugin requires this.
|
||||
register-userconnections-on-join: true
|
||||
# If you use ProtocolLib, we can't reload without kicking the players.
|
||||
# (We don't suggest using reload either, use a plugin manager)
|
||||
# You can customise the message we kick people with if you use ProtocolLib here.
|
||||
reload-disconnect-msg: Server reload, please rejoin!
|
||||
# Should we replace extended pistons to fix 1.10.1 (Only on chunk load)
|
||||
replace-pistons: false
|
||||
# What id should we replace with, default is air. (careful of players getting stuck standing on them)
|
||||
replacement-piston-id: 0
|
||||
# The message to be displayed at the prompt when the 1.17+ client receives the server resource pack.
|
||||
resource-pack-1_17-prompt: ''
|
||||
# Send the supported versions with the Status (Ping) response packet
|
||||
send-supported-versions: false
|
||||
#
|
||||
# Enable serverside block-connections for 1.13+ clients - all the options in this section are built around this option
|
||||
serverside-blockconnections: true
|
||||
# When enabled 1.9+ will be able to block by using shields
|
||||
shield-blocking: true
|
||||
# If this setting is active, the main hand is used instead of the off-hand to trigger the blocking of the player.
|
||||
# With the main hand the blocking starts way faster.
|
||||
# (Requires "show-shield-when-sword-in-hand" to be disabled)
|
||||
no-delay-shield-blocking: false
|
||||
# If this setting is active, the shield will appear immediately for 1.9+ when you hold a sword in your main hand.
|
||||
# The shield disappears when you switch to another item.
|
||||
# (Requires "shield-blocking" to be enabled)
|
||||
show-shield-when-sword-in-hand: false
|
||||
# Enable player tick simulation, this fixes eating, drinking, nether portals.
|
||||
simulate-pt: true
|
||||
# Should we patch boss bars so they work? (Default: true, disable if you're having issues)
|
||||
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)
|
||||
bossbar-anti-flicker: false
|
||||
# This will show the new effect indicator in the top-right corner for 1.9+ players.
|
||||
use-new-effect-indicator: true
|
||||
# We warn when there's an error converting item and block data over versions, should we suppress these? (Only suggested if spamming)
|
||||
suppress-conversion-warnings: false
|
||||
# When enabled if certain metadata can't be read we won't tell you about it
|
||||
suppress-metadata-errors: false
|
||||
# Should we use prefix for team colour on 1.13 and above clients
|
||||
team-colour-fix: true
|
||||
tracking-max-kick-msg: You are sending too many packets, :(
|
||||
# How many warnings over the interval can we have
|
||||
# This can never be higher than "tracking-period"
|
||||
tracking-max-warnings: 4
|
||||
#
|
||||
# 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
|
||||
# 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.
|
||||
truncate-1_14-books: false
|
||||
# Should 1.15+ clients respawn instantly / without showing a death screen?
|
||||
use-1_15-instant-respawn: false
|
||||
# Show the new death messages for 1.9+ on the death screen
|
||||
use-new-deathmessages: true
|
||||
# Should we replace extended pistons to fix 1.10.1 (Only on chunk load)
|
||||
replace-pistons: false
|
||||
# What id should we replace with, default is air. (careful of players getting stuck standing on them)
|
||||
replacement-piston-id: 0
|
||||
# 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)
|
||||
chunk-border-fix: false
|
||||
# Force the string -> json transform
|
||||
force-json-transform: false
|
||||
# Minimize the cooldown animation in 1.8 servers
|
||||
minimize-cooldown: true
|
||||
# Allows 1.9+ left-handedness (main hand) on 1.8 servers
|
||||
left-handed-handling: true
|
||||
# Get the world names which should be returned for each vanilla dimension
|
||||
map-1_16-world-names:
|
||||
overworld: minecraft:overworld
|
||||
nether: minecraft:the_nether
|
||||
end: minecraft:the_end
|
||||
# This will show the new effect indicator in the top-right corner for 1.9+ players.
|
||||
use-new-effect-indicator: true
|
||||
# Vines that are not connected to blocks will be mapped to air, else 1.13+ would still be able to climb up on them.
|
||||
vine-climb-fix: false
|
||||
|
||||
Loading…
Reference in New Issue
Block a user