-
-
Notifications
You must be signed in to change notification settings - Fork 61
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
MOTD "passthrough" #119
Comments
You'd only like the MOTD to passthrough while all other online status properties are overridden? |
Preferably, yes. If not, passing through other status properties can also work. |
@haveachin Is there way to do this with Bedrock edition? |
No, currently it is not possible to pass the MOTD through in Bedrock. Server list pings are totally different in Bedrock than they are in Java, since Bedrock uses RakNet on top of the UDP protocol to communicate. For whatever reason, Mojang/Microsoft decided that it would be a good idea to use RakNets build in ping mechanism to implement server list pings. The problem now is that the RakNet implementation does not communicate what FQDN was uses to reach the server, which makes it impossible to pass the right MOTD through to the client. So you can only have one MOTD per port due to how the Bedrock protocol works. |
Although I can only show one MOTD per port in Bedrock, can you add config to set which server's MOTD to passthrough for all FQDNs? |
I'll look into adding that |
I just wanted to "+1" the idea of having a separate motd option. |
Is your feature request related to a problem? Please describe.
I can't properly use dynamic MOTD solutions with Infrared.
Describe the solution you'd like
A "passthrough" feature. Infrared would take the MOTD of the backend, and it would then use said MOTD for the frontend proxy.
Describe alternatives you've considered
I've created various scripts and utilities in the past that use the backend server's MOTD for the proxy's configuration. None of these solutions have worked well, due to handicaps with decoding HAProxy-wrapped responses from the backend server.
The text was updated successfully, but these errors were encountered: