search

Rapha149 / SignGUI

An api to get input text via a sign in Minecraft.
GNU General Public License v3.0
35 stars 12 forks source link

[Bug] Teleporting when connecting with Bedrock over Geyser #11

Open lucasfrederico opened 3 weeks ago

lucasfrederico commented 3 weeks ago

API version

2.3.3

Server software and version

Purpur 1.20.4

Steps to reproduce

1. Open the SignGui using Bedrock client

Expected behaviour

Hopefully it doesn't have this teleportation effect. Teleportation is visual only, but the bedrock player cannot be teleported. In fact, if he types, for example, /spawn, he is teleported, but only for other players seeing him, in the bedrock player's view, he does not move.

What is actually happening?

image In the bedrock player's view, you are teleported to a strange place, it seems like you were teleported to the sky after opening the sign.

Code snippets

No response

Any additional comments?

No response

Rapha149 commented 3 weeks ago

Honestly, I have no idea what could cause this bug. My API really only sends the information about the sign to the player and then prompts the client to open the sign. Of course this is different than when you normally open a sign for a player because none of it happens on the server itself but it shouldn't have this effect regardless. I don't know if I will be able to solve this issue but it could help if you provided some more information, for example:

  1. What exact setup do you use to connect with a Bedrock client to a Java server?
  2. Did you use this API in previous versions as well and if yes, did this bug happen in these versions too or is it a new bug in 1.20.4?
lucasfrederico commented 3 weeks ago
  1. I don't know if this is what you asked, but I use GeyserMC to connect Bedrock players to Java servers
  2. I'm not sure about this, maybe it's a problem with 1.20.4, because I received this report recently, when we updated our server to 1.20.4, however, we have another less busy server, which is SkyBlock, it was already on 1.20.4 . So, I'm not sure, because it's a bug in 1.20.4, or it could be that this has always existed and we never tested it.