-
Notifications
You must be signed in to change notification settings - Fork 2
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
In the 1.17 this won't work #1
Comments
It really depends on what Mojang’s new blacklist implementation is. If someone figures out how the 1.17 blacklist works, there might be a way around it. Edit: Based on some quick tests, it appears to check if the IP has an SRV prefix _minecraft._tcp in front of it, and removes it if it does. Simple, but effective. You can view the new change in the Bootstrap class in the patchy library. |
Mmmmm, I see it now. |
The only solution I can currently think of is cycling through IPs frequently, but that may not bode well with the player base. |
Yes, but I understand that in some moment you will get banned all ips from your server.. |
Theoretically, someone could make some sort of mod (maybe Fabric?) that could bypass the blacklist by modifying the isBlockedServer() method. |
Yes, but in this case you force player to user a different version of the game. This is the problem, that right now the player didn't need to use other launcher or mods to play blocked servers, but right now... I don't know. |
What if you create a modified version of the game that simply always returns true for the isServerBlocked method? (I don't deal with clients much so I may sound braindead here) then they could simply just use the same launcher just a different jar? |
Yes, it’s quite a possibility. I believe SquidHQ tried to do just that. |
Unfraternally the SRV trick doesn't seems to work in 2022. |
https://minecraft.fandom.com/wiki/Java_Edition_21w13a
See: MC-136551 bug fixed
Now what guys?
What can we do?
The text was updated successfully, but these errors were encountered: