forked from LOOHP/Limbo
-
Notifications
You must be signed in to change notification settings - Fork 1
Open
Labels
enhancementNew feature or requestNew feature or requestgood first issueGood for newcomersGood for newcomers
Description
When players using the NeoForge mod loader attempt to connect to LimboService as a limbo/fallback server (via Velocity), their connection is immediately rejected with the following message:
You are trying to connect to a server that is not running NeoForge, but you have mods that require it. A connection could not be established.
NeoForge clients should be able to remain connected to the network via the Limbo/fallback server, or at least a compatibility/fallback handshake should allow them not to be kicked until they return to the main modded server.
Additional Info
- Velocity forwarding and all proxy settings are set up correctly.
- The problem occurs only with NeoForge (and likely Forge) clients, not with vanilla or non-modded clients.
- There is currently no Velocity plugin, LimboService plugin that can spoof a compatible NeoForge handshake to keep the client connected.
- The issue relates to the fact that the LimboService does not implement the Forge/NeoForge handshake protocol, so the client sees the server as incompatible and disconnects.
Suggested Solution
- Implement optional support for responding to NeoForge/Forge handshake requests within LimboService, to spoof minimum compatibility and prevent modded clients from being kicked immediately.
Metadata
Metadata
Assignees
Labels
enhancementNew feature or requestNew feature or requestgood first issueGood for newcomersGood for newcomers