"add server" feature not saving ipv6 addresses

I can confirm this is happening, on the Windows 10 edition, version 1.14.60, anyway.

As an example, if I add servers like these (name, IP, port):

Test1, 192.0.2.10, 19132
Test2, 1234:5678::abcd, 19132
Test3, 1234::5678:abcd, 19132
Test4, 2001:db8::abcd, 19132

The game would be able to save and join them just fine while it is still open, but after closing and opening it again,

• Test1 would load just fine,

• Test2 would load as (name, IP, port)

  Test2, 1234, 5678

• Test3 and Test4 would not appear at all.

Looking at external_servers.txt , the servers appear to be stored in the format

orderAdded:name:address:port:lastJoined

so the above examples would be stored as

1:Test1:192.0.2.10:19132:x
2:Test2:1234:5678::abcd:19132:x
3:Test3:1234::5678:abcd:19132:x
4:Test4:2001:db8::abcd:19132:x

with nothing to differentiate between the the colons as separators and in ipv6 addresses.

After reloading the game, when editing a server already in the list, or adding another, these stored servers are changed to

1:Test1:192.0.2.10:19132:x
2:Test2:1234:5678:x

with Test3 and Test4 getting removed.

Thank you for your report!
However, this issue has been temporarily resolved as Awaiting Response

Is this still an issue in the latest version?

If it is, please be sure to include steps to reproduce the problem:

Steps to Reproduce:
1.
2.
3.

Observed Results:
(Briefly describe what happens)

Expected Results:
(Briefly describe what should happen)

If your ticket does not look like the example given here, then it's likely to be closed as incomplete.

This ticket will automatically reopen when you reply.

Quick Links:
📓 Issue Guidelines – 💬 Mojang Support – 📧 Suggestions – 📖 Minecraft Wiki

I can confirm that this is still an issue in Windows 10 edition, v1.16.40, still exactly as I describe above.

Steps to Reproduce:

1. Open server browser, scroll to bottom, press "Add Server"

2. Add the servers, (name, IP, port), note the different position of the double colon in Test2 and Test3:

   Test1, 192.0.2.10, 19132
   Test2, 1234:5678::abcd, 19132
   Test3, 1234::5678:abcd, 19132
   Test4, 2001:db8::abcd, 19132

1. Quit Minecraft

2. Reopen Minecraft, navigate to server browser

Observed Results:

• Test1 would load just fine,

• Test2 would load as (name, IP, port)

  Test2, 1234, 5678

• Test3 and Test4 would not appear at all.

• Open the file

%LOCALAPPDATA%\Packages\Microsoft.MinecraftUWP_8wekyb3d8bbwe\LocalState\games\com.mojang\minecraftpe\external_servers.txt

• -> Server information is separated by colons, the same separator that IPv6 addresses use:

  1:Test1:192.0.2.10:19132:1601426219
  2:Test2:1234:5678::abcd:19132:1601426233
  3:Test3:1234::5678:abcd:19132:1601426246
  4:Test4:2001:db8::abcd:19132:1601426261

Expected Results:

• All servers should be the same as when they were added.

• Servers should be stored in a different format, as to not confuse the IPv6 hextet separator colons with server information separators.

I wanted to create a ticket, but saw there was aleardy this one.
I also found MCPE-30324 and MCPE-117352, which are having the same problem.

It's exacly as Yottazoid describes (Minecraft confuses the : separators of the IPv6 address with the : separator of the port) and is still an issue in v1.16.210.

This also is a problem on all platforms, that lets you add dedicated servers.

I added two screenshots that showcase how the IPv6 address & port looks after putting it in and after restarting the game.

Same here, the server which I added gets deleted after exiting and reopening Minecraft.

mojang should definitely fix this my ISP is unsupporting IPV4 on some infastructure. I am forced to use 3G for the IPV4.

It can't even join IPV6 servers. It will just say: Connection Timed out. Please add this to your bug report.

This issue is 2 years old mojang microsoft tell me why?

The bad thing when I switch my router to IPV4 only, I cannot sign in on my Microsoft Account.

It also affects Hive(Server), Realms and others.

Ironically, the game doesn't even support IPv6 despite allowing you to save IPv6 addresses in the server list. This is something that they probably should have dealt with years ago.