End gateway teleports you to the obsidian end platform

Confirmed for 18w47b as well

The end cities generated when flying in creative are around 16 thousands blocks away from the central island in 18w48b, in 1.13.2 they are only around 1 thousand away.

Also occured in multiple worlds tested in version 18w49a

This has been happening to my game too..

Is there any way to get round this? It's happening for me in 18w49a

Same issue with seed: -1504342332604097644

Stronghold End Portal is at: (-1433, 30, 680)

The issue occurs in Snapshot 18w43c and thereafter, it is not present in Snapshot 18w43b and older (and not in 1.13.2).

Same problem for me as well.

Snapshot 18w50a

Seed: 6063057163609804162

Flew out in Creative to ~8500X, ~70Y, ~20Z and got an End Gate in the outer islands to spawn. It also teleports back to the obsidian spawn platform.

This is happening on 18w50a.

Just happened to me in a survival world in 18w50a... guess that's what I get for using snapshots.

Also happening to me in 18w50a. Would love a workaround if anyone has anything.

Only workaround I've found is to use commands to /setblock a new portal, which will teleport you to the outer islands. 

It happened to me on the server snapshot 18w50a version.

I didn't have the problem on a solo world yet.

Since somewhere in the 1.14 snapshots, the end gateway has fixed ExitPortal coordinates - that of the obsidian spawn platform - inserted.

Check with: /data get block ~ ~-3 ~ when you stand on top of the gateway after you killed the dragon.

In 1.13.2, there is no ExitPortal specified, until you actually entered into that gateway, leading you to the according remote end island.

As soon as you entered the gateway and head back to the main island, the main island gateway will now have the coordinates as ExitPortal inserted.

I currently don't see any Survival means to fix this, so if you want and can use commands, I suggest to change the ExitPortal coordinates of the gateway into the remote end island gateway coordinates for the time being, until this is fixed, if you really want to play a snapshot version in Survival.

When you stand on top of the gateway, run this, but change the coordinates, those are just a dummy for this example:
/data merge block ~ ~-3 ~ {ExactTeleport:1b,ExitPortal:{X:1000,Y:80,Z:100}}

So instead of 1000/80/100 insert the real coordinates of where the according gateway is on the remote end island.

Additional info: I ran a data get block on a random gateway on a remote island in 18w50a, and it points back to the obsidian spawn platform again, whereas in 1.13.2 it points to the main island gateway. So it seems currently that a general "insert coordinates of obsidian spawn platform as ExitPortal" is inserted into any gateway in the current 1.14 snapshot.

@unknown That's a nice find. If you don't know the coordinates where the specific gateway should take you or it's a little inconvinient to find out, you can also remove the ExitPortal tag. While data remove apparently cannot remove compound tags for whatever reason, we can replace a gateway using setblock. A gateway created by /setblock does not have the ExitPortal coordinates set, this seems to be only the case for natural generated ones.

So to replace a end_gateway that does not sent you to the proper location, you can use /setblock <pos> minecraft:end_gateway destroy. (The destroy makes sure it actually replaces the block. Without it, it won't do it because a block with the same ID is already there)

And indeed, an end_gateway that does not have the ExitPortal set will take you to the proper location.

@unknown I was just conducting some tests in 1.13.2 and 18w50a, incl. videos, but I don't think we will need them atm.

Initially - it's what I tried yesterday as first thing - one would expect that it'd be possible to remove the data of a dataholder, but I couldn't find a way, be it a data merge, or a data modify set value with a {} at the end, it all doesn't work as I personally would have expected it, going by my old command knowledge. So that'd be certainly something to improve on, imo.

As for your suggestion with setblock: While it is true that if you setblock a gateway, it will give you a gateway with no ExitPortal specified yet, it does teleport you to a remote place though, once you get through.

While this is technically what we desire, there is an issue though: As soon as you try to get back via the remote gateway to the main island, you may end up in a tp-loop of sorts, as it seems that the remote gateway doesn't put you on solid ground. I found myself either inside the main island for 1 block, or inside the setblock'ed main island gateway or rather its surrounding bedrock itself, which resulted in the game teleporting me back to the remote gateway, and so on and so forth, and sometimes it was "Waiting for Chunk" at the remote area, and sometimes the chunk didn't load at all although I waited for a longer time, so I had to teleport back to the main island (I got video footage of everything).
I tested this several times, I also looked at the data both the main island as well as remote gateway held.

In 1.13.2, if you setblock a gateway in The End, it places you onto solid ground on the main island, when you return via the remote gateway.
At least in the few tests I could conduct so far, will have to do this a couple times more.

Given the short amount of time, I can't be 100% sure of what I just wrote, but I currently would not suggest to simply setblock a gateway in 18w50a, unless you do the following:

setblock a gateway on the main island (e.g. replacing a real one from after the dragon kill, although I'd suggest to set a separate one), and note down its coordinates
go through the setblock'ed main island gateway to the remote island
run a data get block against the remote gateway
go through the remote gateway back to the main island
in case it teleports you back to the remote gateway, it may be that it tried to teleport you either inside the main island gateway, or inside another solid block of the main island; in that case make a data merge block against the remote gateway with slightly offset-ExitPortal-coordinates compared to the setblock'ed main island gateway coordinates.

Going by the tweet you just sent me, it was no coincidence apparently that, by setblock'ing a gateway in 18w50a, it does indeed teleport you to a remote island, but it is a tiny island, not a real larger island with structures and all, as you would expect. I wanted to test this to verify it, but I'll take your idem experience as such.

Thus scratch the whole setblock-thing for now and just do the data merge with an ExitPortal you specified, it really seems that gateway-teleportd are quite broken atm 🙂

I created seperate issues for both bugs.
End gateways opposite to one at the main island loop back to itself: MC-141820
End gateways on the main end island take you to a tiny island: MC-141823

Further discussion on these issues shall be continued there 😉

Having this issue still in 18w50a. Also End Cities don't seem to be generating.

I am also having this same issue in 18w50a. Aswell as Nethan Chesshir, i have traveled about 6 thousand blocks in the end, and end cities are not generating. 

End gateways seem to be deactivated for some reason. End cities are generating but are rarer than expected. Found 2 End cities in a total area of 20,000² blocks. /locate commands teleport you most of the time in the void where no End city is found. Still those are End city areas where you can get the entering cities advancement.

Confirmed this issue still exists on 19w02a.

Generated end gateway warps you to the starting platform, and if you fly out in creative, no end cities generate.

As Brad Corbin commented, the issue still occurs in 19w02a, has been broken since 18w43c. It is commonly believed that this bug is a side effect of End Cities not generating.

This happened in my world too. I made it in 18w50a, then updated my world (after I backed it up as minecraft suggests) And updated to 19w02a and ever since I killed the ender dragon and attempted to throw an ender pearl into the end city portal that is supposed to take me to a random island outside of the 1000 block void between the dragon island and the outer islands, it only took me back to the obsidian pad that was originally spawned before I ever got to kill the dragon. This sucked obviously and I had to make a 1x1 slab bridge to the islands and guess what... Not a SINGLE end city in sight. I had to have traveled 6000+ blocks to attempt to try to find an elytra so I may have the ability fly & do big projects back in my singleplayer town. This has been such a huge disappointment, and causes lack of motivation to do ... well any sort of build. I would deeply appreciate any and all help or possible influence to help mojang fix this in any future snapshot updates. And any help in general would be appreciated by any users. I am looking forward to the future since this topic is being discussed more in general, which gives me hope! Sending nothing but positive energy! 

Confirmed for 19w03a.

@ anyone who recently commented and is looking for help, please read my comment here.

To explain it again in other words: End gateways can be dataholders. They can contain the coordinates of an ExitPortal you get teleported to.
Via commands, coordinates of the ExitPortal for end gateways can be added manually.

For some reason in the current 1.14 snapshots the gateways (which are set automatically when you kill a dragon) contain by default the obsidian spawn platform's coordinates.
This is why you get teleported to that platform each time, and unless you change the coordinates of the ExitPortal via commands, there is no other way to circumvent that. So you don't have to try and try again, those coordinates currently seem to be fix.

Correct would be that the gateway wouldn't have any coordinates inserted yet, but only as soon as you entered it / went to an outer End island. That's how it is in 1.13.2 release.

For some reason currently no outer End islands are located at around the ~1k mark like before.
Because of this, apparently MC-141823 ("End gateways on the main end island take you to a tiny island") is happening, no teleport to an End city island, as it seems they are too far out.

I am very certain that Mojang has taken or will take notice of this and will fix it before a release version, as this is vital to the Survival gameplay.
Mojira moderators are present on this bugpost, and from what is publicly known, it seems they can come in contact with the developers and will surely notify them of it, if they haven't already, so keep calm and always carry a towel with you 🙂

For those of you who mentioned they play Survival in snapshots: There have been snapshots which were hazardous to worldsaves, so you may reconsider.

You should never play a world you care about in a snapshot, ever - without backups, and always keep in mind the potential possibility that all effort and progress you achieved during your snapshot (Survival) play will be gone due to bugs, so you may have to start all over again with your backup in the last MC release version update (1.13.2), or a previous 1.14 snapshot version.

If you know of those risks and also that you may invest time without keeping its fruits, of course do as you please, but then don't be disappointed or angry if the worst case happens.
And positive energy is always welcome @unknown, also sending some to everyone 🙂

Confirmed for 18w50a, 19w02a, 19w03a/b

As Brad Corbin said, the little end gateway warps you to the starting platform, and if you fly out or construct a bridge to reach the outer islands, no end cities generate.

In response to Meri (thank you for your investigation!), the help that your describe in your comments would seem to be only applicable to cases where End Cities have generated. In my case the /locate command produces coordinates, but when /tp to the same coordinates there is nothing there but Void and death =).

As Doctor5555 and NeunEinser have indicated, /setblock is a fair workaround to get the End Gateway to do something other that put you back at the End spawn platform. But that still does not help if the End Cities have not generated.

I only add that information to highlight that it would appear that this bug and End Cities not generating are linked.

@unknown I'm not so sure that this bug - 'obsidian platform coordinates entered as default in dragonkill-generated + on outer islands naturally existing end gateways' - and 'outer islands around the ~1k mark aren't generating anymore' are linked (unless both are intentional, as speculated below), however I am fairly certain that MC-141823 and outer islands around the 1k mark not generating anymore are related.

But you raise a very good argument here - Shouldn't "outer islands around 1k mark aren't generating anymore" get an own bugpost? (Question to the moderators here.)
(As soon as that would be fixed, MC-141823 should be automatically fixed, too, potentially.)

This is only extreme speculation, but maybe they are changing up the end cities/outer islands as for their optics and/or content, and thus have intentionally entered the obsidian spawn platform as teleport destination for the time being while they are still not finished with re-coding those end cities/outer islands. Wishful thinking though, likely 😉

Let's just wait and see, if this is still not fixed in the first 1.14 prerelease, we'll somehow make sure that we know that the Devs have at least taken notice of this 🙂

Can confirm that this is still an issue in the 19w03c snapshot, the spawned portal teleports you to the start platform and a 'setblock' gateway teleports you to an island many blocks away from the end islands.
after flying around in spectator mode I can confirm that end cities are spawning though, albeit very rarely, and cities found by the /locate command sometimes are inaccurate and drop the player into the void.