Open MrRubberDucky opened 7 months ago
I have in plans to make separate plugin for velocity to resolve this
The problem is just that automodpack packets are and need to be semi-first* and it is too early for velocity to handle from backend server I guess
I have in plans to make separate plugin for velocity to resolve this
Ah aighty, good to know that it's planned! For now I just ended up going NGINX stream module route (alongside rathole) and so far it's been fine.
Lovin this mod btw it makes managing modpacks for friends and small communities a blast so thank you for creating this, it's really a game changer.
The problem is just that automodpack packets are and need to be semi-first* and it is too early for velocity to handle from backend server I guess
I learned something new today
was there ever a fix for this?
Bug description
Trying to join a server that's behind a Velocity proxy with a modded client that has Fabric & AutoModpack mod installed will result in a disconnect from backend server.
Steps to reproduce
Expected behavior
AutoModpack allows me to connect via Velocity and download the modpack
Actual behavior
Client gets disconnected with a " has not installed AutoModpack." message
Relevant logs
Back-end (Game Server)
Front-end (Velocity)
Minecraft & Mod Loader versions
1.20.1 Fabric 0.14.24, Velocity 3.2.0-SNAPSHOT-294
Minecraft launcher
Modrinth Launcher
Operating system
Windows 11 (Host), Debian Bookworm (back-end), Debian Bookworm (front-end)
AutoModpack version
3.5.2
Other information
Velocity plugins installed: SignedVelocity, VPacketEvents, Raknetify (with, or without it's the same)
Fabric mods installed: FabricProxy-Lite, CrossStitch, SignedVelocity and Raknetify
The problem might just be AutoModpack not querying back to Velocity about what mods client has, not really sure but at least a lead for where to look.
Check list