Describe the bug
Cannot join a Vault Hunters server using a 1.13.8 server pack and fresh 1.13.8 client instance due to failure to synchronize registry data from the server
To Reproduce
Steps to reproduce the behavior:
download the 1.13.8 Vault Hunters server pack for Minecraft version 1.16.5
run the start.ps1 powershell script with the args: -Xmx10G -Xms8G -Dfml.readTimeout=90 -jar forgeserver.jar nogui
attempt to connect to the open server with a fresh 1.13.8 installation of Vault Hunters for Minecraft 1.16.5
Expected behavior
Connection to the server to establish and for client to load in
Screenshots or Crash Report
[14:01:19] [Server thread/INFO] [minecraft/DedicatedServer]: Starting GS4 status listener
[14:01:19] [Server thread/INFO] [minecraft/RConThread]: Thread Query Listener started
[14:01:19] [Query Listener #1/INFO] [minecraft/QueryThread]: Query running on 0.0.0.0:25569
[14:01:19] [Server thread/INFO] [co.po.ne.NeonCraft/]: HELLO from server starting
[14:01:19] [Server thread/INFO] [is.is.co.IskallUtilities/]: Server is starting
[14:03:40] [User Authenticator #1/INFO] [minecraft/ServerLoginNetHandler]: UUID of player Extore is 88998f9c-0f7d-4e59-8c36-51ffc56ef7d5
[14:03:42] [Server thread/INFO] [minecraft/ServerLoginNetHandler]: com.mojang.authlib.GameProfile@7c62f4d9[id=88998f9c-0f7d-4e59-8c36-51ffc56ef7d5,name=Extore,properties={textures=[com.mojang.authlib.properties.Property@5dd28571]},legacy=false] (/192.168.56.1:49593) lost connection: Disconnected
Info (please complete the following information):
World Type: Server
The_Vault Version [e.g. 1.0.1]: 1.13.8
Additional context: see steps
Add any other context about the problem here.
I have also noticed that the configs for the server have messed up properties - perhaps really old config files? For example, purchasing dash costs 2 skill points initially in server config files, which is not what the client side says it costs.
SpokenWig620933
commented
2 years ago
Describe the bug Cannot join a Vault Hunters server using a 1.13.8 server pack and fresh 1.13.8 client instance due to failure to synchronize registry data from the server
To Reproduce Steps to reproduce the behavior:
Expected behavior Connection to the server to establish and for client to load in
Screenshots or Crash Report
[14:01:19] [Server thread/INFO] [minecraft/DedicatedServer]: Starting GS4 status listener [14:01:19] [Server thread/INFO] [minecraft/RConThread]: Thread Query Listener started [14:01:19] [Query Listener #1/INFO] [minecraft/QueryThread]: Query running on 0.0.0.0:25569 [14:01:19] [Server thread/INFO] [co.po.ne.NeonCraft/]: HELLO from server starting [14:01:19] [Server thread/INFO] [is.is.co.IskallUtilities/]: Server is starting [14:03:40] [User Authenticator #1/INFO] [minecraft/ServerLoginNetHandler]: UUID of player Extore is 88998f9c-0f7d-4e59-8c36-51ffc56ef7d5 [14:03:42] [Server thread/INFO] [minecraft/ServerLoginNetHandler]: com.mojang.authlib.GameProfile@7c62f4d9[id=88998f9c-0f7d-4e59-8c36-51ffc56ef7d5,name=Extore,properties={textures=[com.mojang.authlib.properties.Property@5dd28571]},legacy=false] (/192.168.56.1:49593) lost connection: Disconnected
Info (please complete the following information):
World Type: Server The_Vault Version [e.g. 1.0.1]: 1.13.8 Additional context: see steps Add any other context about the problem here.
I have also noticed that the configs for the server have messed up properties - perhaps really old config files? For example, purchasing dash costs 2 skill points initially in server config files, which is not what the client side says it costs.