Closed PedroPF1234 closed 2 weeks ago
The answer was given in discord:
That mod is defining more 'known packs' that vanilla permits, you can change the limit with -Dvelocity.max-known-packs=XX, default is 64
After setting the max-know-packs to a higher number, it connected. I incremented the default value until it could connect.
Expected Behavior
I expected to get a simple connection like the one I get connecting with ATM8 (mc version 1.19.2). Both backend servers are running the PCF mod and both have the forwarding secret set up.
Actual Behavior
When I try to connect, I get this log on my velocity terminal:
And I get the following on the server's terminal:
Steps to Reproduce
To obtain the exact logs I initialized velocity with the following command:
I should also note that, before running this command, I simply ran:
This one produced a similar log but between the "connected" and "disconnected" lines, the output was much shorter:
Plugin List
Ambassador-Velocity-1.4.4-all.jar; ViaBackwards-5.0.3.jar; ViaRewind-4.0.2.jar; ViaVersion-5.0.3.jar
Velocity Version
Velocity 3.3.0-SNAPSHOT (git-2016d148-b436)
Additional Information
Running Ubuntu 22.04.5 LTS as OS. Unlike ATM8, ATM10 uses neoforge. My servers are running ATM8 v1.1.0 and ATM10 v0.40.0.