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

Bedrock clients do not get teleported to the correct location. #386

Closed
mibby opened this issue Apr 20, 2020 · 3 comments · Fixed by #389
Closed

Bedrock clients do not get teleported to the correct location. #386

mibby opened this issue Apr 20, 2020 · 3 comments · Fixed by #389
Labels
Confirmed Bug The bug reported is confirmed and able to be replicated. Priority: Medium Work in Progress The issue is currently being worked on.

Comments

@mibby
Copy link

mibby commented Apr 20, 2020

Describe the bug
Bedrock clients do not get teleported to the correct location.

To Reproduce

  1. Hit button that teleports players away to a new location.
  2. Get sent to a different area than intended.

The client hits a button that teleports from their current location (1242, 89, -228) to a new location underground (1167, 71, -251). For some reason Bedrock clients glitch and end up half way to the new location.

Expected behavior
The client teleported being sent to the correct location.

Screenshots / Videos

Server Version
Paper dev 201 (Spigot 1.15.2)
Waterfall dev 327 (BungeeCord 1.15.2)

Geyser Version
Geyser inventory dev 24 (Using as BungeeCord Plugin)
Floodgate development dev 5 (Using as BungeeCord Plugin)

Minecraft: Bedrock Edition Version
Minecraft Bedrock 1.14.60

Additional Context
Java 11.0.7 (AdoptOpenJDK LTS)
Centos 8 (Linux)

@Redned235 Redned235 added Confirmed Bug The bug reported is confirmed and able to be replicated. Priority: Medium Work in Progress The issue is currently being worked on. labels Apr 20, 2020
@Preloading
Copy link

I can confirm this though for me the player spawns in the void and doesn't get killed by the void :( (bedwars)

@Camotoy
Copy link
Member

Camotoy commented Apr 22, 2020

The void is now its own issue - #406.

@BrianValente
Copy link

Probably related to my issue #281

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Confirmed Bug The bug reported is confirmed and able to be replicated. Priority: Medium Work in Progress The issue is currently being worked on.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

5 participants