Skip to content
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

1.21+ support? #257

Open
Reishimanfr opened this issue Jun 21, 2024 · 9 comments
Open

1.21+ support? #257

Reishimanfr opened this issue Jun 21, 2024 · 9 comments

Comments

@Reishimanfr
Copy link

Currently mcsleepingserver for minecraft 1.21+ is broken, it's impossible to start the server on this version. Is it possible to bring support to 1.21+ or is it not planned/impossible for now?

@GamerNation12
Copy link

fr

@Gamogamer
Copy link

I am running bungeecord on 1.21.1 and it does kind of work for me, albeit the messages on refused connections are only errors now. Instead of the "server starting now" messages

@JamesDAdams
Copy link

same doesn't work with 1.21+

@vincss
Copy link
Owner

vincss commented Oct 30, 2024

I know, I opened a bug on minecraft-protocol side :
PrismarineJS/node-minecraft-protocol#1340

@AdriPlaysz
Copy link

Same. Im on 1.21.1 PaperMC and it doesn't work :(

@Her0brineCreeper
Copy link

A temporary workaround for the issues with newer Minecraft versions is to change/add the following lines in your "sleepingSettings.yml" while we wait for an official fix:

serverOnlineMode: false
useLegacyLogin: true

This works for me on 1.21.1.

@sepiisagun
Copy link

sepiisagun commented Jan 21, 2025

@vincss would it be fine to ask if you can at least update the java version of Docker? Trying to use 1.21+ on docker seems to be causing an issue since it needs java version 20+ to run even with the mentioned workaround. Thanks!

@vincss
Copy link
Owner

vincss commented Jan 22, 2025

@vincss would it be fine to ask if you can at least update the java version of Docker? Trying to use 1.21+ on docker seems to be causing an issue since it needs java version 20+ to run even with the mentioned workaround. Thanks!

I think this is not relevant to this ticket. Isn't it Can you create another one ?

@sepiisagun
Copy link

I wasn't sure either if a new ticket was needed too cause its kinda in line with the suggested solution here. But I will be more than glad to do so..

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

8 participants