Not working with 1.18.10 anymore on Nintendo Switch #272
Comments
|
Same issue here. |
|
Unsure if good or bad news, using the Android version of the game (albeit not really needing the server list there because you can add your own servers) connecting through the server list works without issues. I have the feeling the Switch version might have taken on a bug ... Or it's intentional by Nintendo -.- |
Wouldn't surprise me, as I am someone who quite often runs Atmosphere on my switch. Usually I would go around trying to mess around with PrismarineJS's Libary trying to replicate it there but it hasn't been updated yet. |
|
I might add that the Featured Servers also don't work when trying to connect through the server list, so it's at least not an sercer-ident Filter or something... |
|
Don't forget their either direct ips or handles it via InetAddress.getByName |
|
anyway let me update Atmosphere and try to fire up Noexes Debugger to see whats going on. |
Gladly :) |
|
~1 hour later i still have struggle using it, i am gonna look into a temporary solution for this later... |
|
Same issue, glad this was caught early on, so people can look into it :) |
|
Pretty sure featured servers like the Hive use transfer packets in some cases, such as when switching to other regioned servers with the region picker located in their hub. Upon choosing a different region, the same issue seemed to happen similar to choosing a server in the BedrockConnect serverlist, glitched out and didn't work. EDIT: On Pixel Paradise, it looks like you can't even choose some gamemodes Knowing this I'm doubting this bug is intentional, since it's affecting their official servers. Also want to add, although a bit unrelated to BedrockConnect: For anyone that urgently needs to get on a server today and already knows how to host your own DNS server, for now you can technically change the records on your hosted DNS server to the IP of the server you're trying to join instead of the IP of the BedrockConnect instance. |
|
having this happen to me as well, as soon as I try to join an external server I just get brought back to the worlds/realms/servers menu, hope it gets fixed relatively soon. |
|
Half of the users on my server just updated to 1.18.10, lost access and are fussing at me over this. |
|
Came here to see if I was alone having this issue. Glad I'm not! Hopefully we'll be able to play soon |
yea it’s more likely Mojang forgot to transfer the fix to the Nintendo switch, it’s probably gonna get fixed soon since it’s quite game breaking for those who play on featured servers, it also would’ve been very weird from Nintendo (Since Mojang would not out of nothing brother with it) to force them to blockade the transfer packet, especially knowing that things like switch lan play have been now around ~4 years now, and there has never been an attempt to blockade it. But again it would not suprise me if Nintendo actually did something. |
|
Let's for now presume that my initial suspicion against Nintendo doesn't hold true and I'm just a bit overly critical these days given the happenings in the Mario Maker-community. I can't find any info in the Mojang Bugtracker for this problem, so I wonder if Mojang as even realized this. |
|
Seems like this project is critical for everyone running on console, I'm hearing of a lot of people sitting on their hands waiting for this fix. Is there any way we could have tested this before 1.18.10 was rolled out? |
|
I don't know of any way to install a Beta Version of the game on a console, so testing would've been limited to versions where you could join the Beta program, namely Android (iOS?) and PC - which do not really need BedrockConnect. Insert rant about console providers reducing game functionality for money making reasons here |
iOS has an TestFlight here https://testflight.apple.com/join/qC1ZnReJ |
|
I have the same problem. I hope solutions can be found :)) |
|
It looks like you can opt-in to beta test on xbox If the issue is exclusive to Nintendo, it might be worth sending them threatening emails until they let someone from here in on a beta program. |
This seems to be the case, unless @Pugmatt tested if it also happens on Xbox. |
|
I have not heard of any issues from Xbox. This bug is likely a one-time occurrence (possibly something that couldn't quite be fixed on time as all other platforms fixed their issue from the beta). There's no reason having the beta in our hands specifically on Switch would solve the issue. |
|
I have at least one user on my server reporting this issue on Xbox, obviously nothing to do with the server but he still complained to me about it. Nintendo users also complaining. |
|
Don't have an Xbox on hand currently to test on Xbox, but by the sound of the reply above me, it can be possible. Seems to primarily be a Nintendo Switch issue though, I suppose mostly since Xbox users technically also have the LAN proxy bypass that they can also use instead of the DNS/BedrockConnect bypass.
Whether we had a beta test version or not, we were already technically aware a couple of days ago the issue with the transfer packets (#271). There really isn't anything we could do then, and nothing we can really do now until Mojang fixes the bug on their end, as it's an issue with the game client itself that is currently causing this. Since this is affecting featured servers, it will most likely be fixed by Mojang soon, just will need to be patient. I understand this is affecting many server owners, but BedrockConnect's hands are as tied as the servers that need it right now unfortunately. Best thing right now I think is to submit a bug report to the Bedrock Edition bug tracker to make sure Mojang is aware of the bug, while trying to avoid mentioning BedrockConnect in the report as BedrockConnect itself is not their problem, but do mention the issues on the featured servers as that very much is their problem. Could also maybe mention it as the "Transfer packet" specifically, but probably not a good idea? That's as much we can do I think, for now. I will tinker with some ideas I have when I have more free time, but hopefully by that time the bug will already be fixed by Mojang. |
|
Hi @Pugmatt. I've created a bug report on Mojang Jira. |
Thanks for posting that, much appreciated. Hopefully that will get Mojang's attention. |
|
I've found another ticket in Mojang Jira related to this issue. Not sure which one will be closed as "duplicate", so here's a link to another one, just in case. |
|
Oof, was really hoping no one would mention BedrockConnect in the bug reports. Either way, I still think the original bug report you posted will probably hold up better, and not be marked as duplicate since it more goes over the bug on official featured servers which they should be supporting. We'll see. |
Are we sure, that Mojang are not already are fully aware of BedrockConnect being a thing? Alas, my guess is they don't care and are more driven by Nintendo to not allow adding of own servers... |
They are, some literally posted an issue about bedrock connect once lol https://bugs.mojang.com/browse/MCPE-102132 |
Actually, I just did a search in the bug trackers and people have technically mentioned BedrockConnect before in the past. And the staff always just say "We don't support that, so we can't help" and nothing more. I'm sure they're well aware of the project at this point, I just don't like taking chances haha. Plus in terms of this issue, I don't want Mojang thinking this transfer packet issue is just affecting BedrockConnect, something they don't support. But hopefully the first bug report we posted will stop that confusion from happening. |
They will close the bedrock Connect issue as „invalid“, just like previous once, while the one about the one opend by @vzabawski will probably be viewed as valid as it‘s really game breaking for people who play on featured servers.
Why would Nintendo brother, it does not hurt them in anyway, see switch lan play, it allows users to bypass the Switch online even on some games without any modifications and there has never been an attempt to block/break it, so it does not make sense why they would brother about BC. If they brother with BC, then there would be attempts to break slp too, on these spesific games that don‘t need mods. |
|
And slp has been around since August 2018, it would‘ve been a strange move from Nintendo to break the one, but not the other especially the one that get‘s around Nintendo‘s services. |
|
i do understand the distrust in Nintendo, they can such insert insult here, but upper mentioned point just makes it an odd move. |
I'll stop slapping Nintendo insults around now. Promise. ;-) |
I like the wording in the ticket. :D
|
|
Hey, same issue over here since the Switch 1.18.10 update... Glad to see this is being discussed. Great project btw! |
|
Looks like they may have addressed the issue? I'll check it later https://feedback.minecraft.net/hc/en-us/articles/4424805981069 |
|
The wording sounds like it. Great news! |
|
Haven't got the update yet, also the issue on bugs.mojang.com hasn't been resolved yet https://bugs.mojang.com/browse/MCPE-152265, but from looking Mojang recognised the issue as other duplicates have been redirect to vzabawski one. |
|
** Now I got the update |
|
Closed as not a BC Issue. Thanks everyone for the awesome support! |
|
Just tested 1.18.11, the issues is fixed 🎉 |
|
I tested 1.18.11 too and work's fine now |
|
Yess! Thanks for the support everyone! |
What happened?
After updating the Nintendo Switch client to 1.18.10, I can connect to the server list but the redirection to the servers from the list doesn't work anymore.
The Switch displays Generating world but from what I see in the debug screen of my (1.18.11) Ubuntu server, the connect never gets through.
Could this be in conjuntion to @Camotoy's remark that something was wrong with the protocol?
Kai
Excepted Behaviour?
See before.
Steps to reproduce.
No response
Screenshots/Videos
No response
Minecraft Bedrock Version
1.18.10
Console
No response
Additional Context
No response
The text was updated successfully, but these errors were encountered: