You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
Sometimes when a player talks to a Wandering Trader and it happens to have a player's head, the server lags/crashes for a moment. https://pastebin.com/h4XzxJvu
To Reproduce
Steps to reproduce the behavior:
Have lots of potential players for heads
Talk to a Wandering Trader with playerhead trades enabled
Server lags, disconnecting everyone and almost crashes
If server recovers, the head is tradeable
Expected behavior
Player head trade generated without lag.
If there are too many heads to choose from, implement some maximum search time or something.
Server Software and Version:
Vendor: git-Paper-318
Minecraft Version: 1.20.2
Additional context
We have had this issue before when running 1.19, updating server & plugin to 1.20.2 did not fix this issue. We have also attempted to limit the amount of players whose heads can be traded by only granting the permission to certain ranks. We also have Bedrock users via Geyser with a dot in front of their names.
The text was updated successfully, but these errors were encountered:
Describe the bug
Sometimes when a player talks to a Wandering Trader and it happens to have a player's head, the server lags/crashes for a moment. https://pastebin.com/h4XzxJvu
To Reproduce
Steps to reproduce the behavior:
Expected behavior
Player head trade generated without lag.
If there are too many heads to choose from, implement some maximum search time or something.
Server Software and Version:
Additional context
We have had this issue before when running 1.19, updating server & plugin to 1.20.2 did not fix this issue. We have also attempted to limit the amount of players whose heads can be traded by only granting the permission to certain ranks. We also have Bedrock users via Geyser with a dot in front of their names.
The text was updated successfully, but these errors were encountered: