Closed LurgenAU closed 1 year ago
I did manage to get BungeeForge working, and that allows me to connect but messes up the player UUID instead of passing it through correctly from the proxy.
You have Ambassador on the (legacy mode) Velocity proxy and BungeeForge and Proxy Compatible Forge on the backend, correct? That's the setup I need to get Forge ≥1.13 working. Although I've never used any "Bukkit on Forge" software, as they tend to break in strange ways.
ATM7 version 1.0.0 via Velocity with modern forwarding has a similar issue on Magma. I'd probably say though it's probably some combination of Magma and Velocity that causes issues here. Not Ambassador itself. This is based upon us using Forced Hosts on Velocity and it still not working.
I'd open a Gitlab/Discord tickets to Magma, especially since plain forge connection worked on ATM7 version 1.0.0 with Magma. Please note that there are no active devs on Magma that do Tickets anymore though. I was a dev there until I decided it felt like too much of a job.
Thank you, I'll consider opening a ticket but as you say not a whole lot is likely to happen there. Time to fire up ArcLight!
BTW, I appreciate your work on Ambassador. It's a desperately needed tool that appears to work extremely well. Thank you.
When connecting via Velocity 3.2.0 snapshot 265 to a Magma 1.18.2 back-end (version b3448c1f) using Legacy Authentication clients reach the "downloading world" stage, then are immediately disconnected. The first time this happens we get this console message:
Subsequent attempts don't see any messages at all. I've tried using proxy-compatible-forge without success, and bungeeforge just tells me I haven't enabled BungeeCord in the config (I have). I'm keen to utilise Legacy authentication in my setup since I have some 1.12.2 boxes lingering around.
Any ideas where I can start? I've removed any optimisation mods, and anything unusual that I can see without success.