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

Signs dissapear after relogging #4588

Open
InstantlyMoist opened this issue Apr 21, 2024 · 5 comments
Open

Signs dissapear after relogging #4588

InstantlyMoist opened this issue Apr 21, 2024 · 5 comments
Labels
Confirmed Bug The bug reported is confirmed and able to be replicated. Priority: Low

Comments

@InstantlyMoist
Copy link

Describe the bug

Existing and newly placed signs will get replaced by an empty hitbox when relogged. This means hanging and standing signs

image

To Reproduce

  1. Place a sign
  2. Relog
  3. The sign is now gone, but the hitbox is still there.

Expected behaviour

The sign should remain there, with text on it.

Screenshots / Videos

No response

Server Version and Plugins

[16:07:19 INFO]: This server is running Paper version git-Paper-1620 (MC: 1.12.2) (Implementing API version 1.12.2-R0.1-SNAPSHOT)
[16:07:19 INFO]: Previous version: git-Paper-e3bf31e5f (MC: 1.12.2)
[16:07:19 INFO]: Checking version, please wait...
[16:07:23 WARN]: java.lang.NumberFormatException: For input string: ""
[16:07:23 WARN]: at java.base/java.lang.NumberFormatException.forInputString(NumberFormatException.java:68)
[16:07:23 WARN]: at java.base/java.lang.Integer.parseInt(Integer.java:658)
[16:07:23 WARN]: at java.base/java.lang.Integer.valueOf(Integer.java:963)
[16:07:23 WARN]: at java.base/java.lang.Integer.decode(Integer.java:1448)
[16:07:23 WARN]: at org.bukkit.command.defaults.VersionCommand.getFromJenkins(VersionCommand.java:295)
[16:07:23 WARN]: at org.bukkit.command.defaults.VersionCommand.getDistance(VersionCommand.java:266)
[16:07:23 WARN]: at org.bukkit.command.defaults.VersionCommand.obtainVersion(VersionCommand.java:214)
[16:07:23 WARN]: at org.bukkit.command.defaults.VersionCommand.access$000(VersionCommand.java:37)
[16:07:23 WARN]: at org.bukkit.command.defaults.VersionCommand$1.run(VersionCommand.java:199)
[16:07:23 WARN]: at java.base/java.lang.Thread.run(Thread.java:835)
[16:07:23 INFO]: Unknown version

Geyser Dump

https://dump.geysermc.org/RAJgOc30CYC8hj7fQK7ZPn9LXgOIIJxK

Geyser Version

Geyser versie 2.2.3-SNAPSHOT (git-master-c8475d8)

Minecraft: Bedrock Edition Device/Version

latest downloaded from the launcher (pc)

Additional Context

No response

@rtm516 rtm516 added the Unconfirmed Bug/Not Currently Replicable The bug reported is unconfirmed or unable to be replicated. label Apr 21, 2024
@InstantlyMoist
Copy link
Author

current updates:

  • It doesnt appear to be caused by the environment, which was the initial thought. An empty chunk with one sign can lead to this issue too. It's not consistently reproducable within each chunk.

  • Might be missing a mapping:
    image

  • Appears to affect some chunks only, each quartz block has a sign next to them:
    image

@Camotoy
Copy link
Member

Camotoy commented Apr 21, 2024

Older Paper versions had a workaround where signs were not sent as part of the chunk data, but updated soon after. I assume this is related to that.

Do note that, while we will accept fixing this bug, because this bug exists on an older server version, a fix is lower priority.

@InstantlyMoist
Copy link
Author

Older Paper versions had a workaround where signs were not sent as part of the chunk data, but updated soon after. I assume this is related to that.

Do note that, while we will accept fixing this bug, because this bug exists on an older server version, a fix is lower priority.

How does that explain one chunk having them consistently, and one does not? I'd kind of assume none of them would have signs

@InstantlyMoist
Copy link
Author

InstantlyMoist commented Apr 21, 2024

@rtm516 rtm516 added Confirmed Bug The bug reported is confirmed and able to be replicated. Priority: Low and removed Unconfirmed Bug/Not Currently Replicable The bug reported is unconfirmed or unable to be replicated. labels Apr 21, 2024
@InstantlyMoist
Copy link
Author

#3004 seems related

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: Low
Projects
None yet
Development

No branches or pull requests

3 participants