Closed Kaydax closed 11 months ago
Build from the 1.20.2 branch
I wasn't using a server that was 1.20.2, so the branch being called that really didn't make me think to use it. Secondly this is an issue with the release on the modrinth page, so it being marked 1.13-1.20.2 doesn't explain much in what versions of velocity it supports, this this issue being created.
I'm having the same issue: latest.log.
I updated my velocity to 3.2.0-275. I can't connect to my forge and paper servers. Neither my forge nor my paper servers are logging any connection attempts.
Building from the 1.20.2 branch failed, because of the following issues:
getActiveSessionHandler()
doesn't exists, but getSessionHandler()
https://github.com/adde0109/Ambassador/blob/594aa4ccea6138bbea62da873f114dd37e83dd14/src/main/java/org/adde0109/ambassador/forge/VelocityForgeBackendConnectionPhase.java#L115
StateRegistry.CONFIG
doesn't exists.
https://github.com/adde0109/Ambassador/blob/594aa4ccea6138bbea62da873f114dd37e83dd14/src/main/java/org/adde0109/ambassador/forge/VelocityForgeClientConnectionPhase.java#L64
Both issues seem to be introduced by the latest commit https://github.com/adde0109/Ambassador/commit/594aa4ccea6138bbea62da873f114dd37e83dd14.
After changing those lines, the build was successful, but the issue still persists.
I'm having the same issue: latest.log.
I updated my velocity to 3.2.0-275. I can't connect to my forge and paper servers. Neither my forge nor my paper servers are logging any connection attempts.
Building from the 1.20.2 branch failed, because of the following issues:
getActiveSessionHandler()
doesn't exists, butgetSessionHandler()
StateRegistry.CONFIG
doesn't exists.Both issues seem to be introduced by the latest commit 594aa4c.
After changing those lines, the build was successful, but the issue still persists.
The velocity submodule isn't up to date. You need the set it the the commit specified in in the branch.
I reset my local branch and tried to build it again, no clue why, but this time it worked. Now my servers are reachable again. Thank you for your help!
Fixed with the release of v1.4.3-beta
Connecting to a velocity server with ambassador installed when using velocity builds 269 or higher causes the client to fail to connect, stating there was an issue with packets
The build that seems to work without this issue is 3.2.0 Build 261, so after that build seems to add a breaking change that makes ambassador break