Add GeyserMC support

[walksanator]

Geyser/bedrock players can only join after a Java player has joined to start the server. I would suggest adding a option to add bedrock support so combined geyser/paper servers can be ran. This would also allow bedrock servers to use this software

[timvisee]

Thanks for mentioning this. I haven't looked into this, which is why it isn't supported.

I would definitely like to add support for this, assuming Geyser packets are very similar to Minecraft Notchian packets. I'd have to look into this at a later time though.

[Arthurmeade12]

This feature would be very useful to my server (and others, I'm sure)

[GreyBlackHat-05]

reviving this to bump it, the ability to listen for geysermc on 19132 would be very useful.

[ghost]

Bumping this thread too, found some useful information about connection protocols at https://wiki.vg/Bedrock_Protocol

[canthisbe]

Bumping thrice, please add this! I've been using SleepingServerStarter by vincss, and it used to support Bedrock connections. I have some very active Bedrock players and this would be perfect if Geyser was supported. Thank you in advance!

[NyaomiDEV]

I wonder if at the cost of running a java proxy with geyser on it you can put lazymc and the server behind it and use floodgate for everything else like online authentication and the usual stuff really

[Arthurmeade12]

@NyaomiDEV proxy behind proxy setups are unsupported, and they usually don't work. That setup being velocity in front of lazymc in front of the minecraft server.

[timvisee]

Note that lazymc does support HA proxy (or something compatible) in front of it with some additional configuration: https://github.com/timvisee/lazymc/blob/master/docs/proxy-ip.md

Though I don't think that is what this is about.

[Arthurmeade12]

I know that velocity supports haproxy. That could be viable.

[NyaomiDEV]

Where there's a will, there's a way.

You can set up the Velocity proxy in front of Lazymc proxying a Paper server. In the Velocity proxy, you can have Geyser and Floodgate installed.

As for how to set it up... it's pretty straightforward:

• Set up your Java server with Lazymc first; it's also advised to set compatibility with the PROXY protocol, which is now built in on Paper and it doesn't require any additional plugins.
• Test your Java server stand-alone!
• Modify Lazymc so it only listens to local connections (for security, also because we're setting Velocity up)
• Set Velocity up, following official instructions. Leave Lazymc out of your thought process for now, but remember to use the public Lazymc port when you set the server in Velocity.
• Test the Velocity setup as a whole. If it works, you're basically done.
• Set up GeyserMC and Floodgate to your liking, using official documentation. DO NOT forward the Floodgate data to the server behind Lazymc, as that would make it close the connection and not start the server at all.

Velocity cannot be put to sleep by Lazymc, as the limitation would surface up again; but it's less RAM/CPU to keep that one active 24/7 than a full fat MC server, so there's that.

Geyser standalone pinging Lazymc could work too, but I would advise against it as you lose Bedrock player info at the proxy level, which is required for administration.

And also, since you have Velocity as a middle-man, it means you can spin up multiple MC servers and a lobby and have all of that put to sleep by Lazymc.