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
If you place a book in a chiseled bookshelf with a hopper beneath it, the hopper, if it has free inv space, pulls the book out of the bookshelf and the book is visually removed from the bookshelf, the state (f3 slot_x_occupied) is set to false and the book is removed from its inv.
Observed/Actual behavior
If there already are books inside the hopper and after pulling out the book from the bookshelf the book stacks with the books inside the hopper the bookshelf is not updated correctly. But if there are for example 32 books in the last slot of the hopper and the other slots are free everything works normally because the book gets transfered into the first hopper slot and does not stack with 32 books in the last slot. The bug only occurs if the book stacks with books in the hopper. If the bug occurs the book gets pulled into the hopper but is still displayed in the bookshelf but you cannot take it out since it was already pulled out by the hopper and you also cannot put a book in that slot. In f3 you can see the info slot_x_occupied is still true. Only after you insert a book into another slot or take another book out of another slot the bookshelf gets updated
Steps/models to reproduce
place a hopper and on top a chiseled bookshelf
put a book into the first slot of the hopper
put a book into the bookshelf
the hopper pulled out the book and stacked onto the containing book but the booshelf still displays the book
empty the hopper and put one book into the last slot (or any other thats not the first)
put a book into the last slot of the hopper
put a book into the bookshelf
the hopper pulled out the book and put it into the first slot and the bookshelf is empty
Plugin and Datapack List
Server Plugins (0):
There are 3 data pack(s) enabled: [vanilla (build-in)], [file/bukkit (world)], [paper (build-in)]
There are no more datapacks available
Paper version
This server is running Paper version 1.21.1-132-ver/1.21.1@b48403b (2024-11-21-T10:14:27Z) (Implementing API version 1.21.1-R0.1-SNAPSHOT)
You are running the latest version
Previous version: 1.21.1-119-7cd4f2c (MC: 1.21.1)
Other
No response
The text was updated successfully, but these errors were encountered:
Expected behavior
If you place a book in a chiseled bookshelf with a hopper beneath it, the hopper, if it has free inv space, pulls the book out of the bookshelf and the book is visually removed from the bookshelf, the state (f3 slot_x_occupied) is set to false and the book is removed from its inv.
Observed/Actual behavior
If there already are books inside the hopper and after pulling out the book from the bookshelf the book stacks with the books inside the hopper the bookshelf is not updated correctly. But if there are for example 32 books in the last slot of the hopper and the other slots are free everything works normally because the book gets transfered into the first hopper slot and does not stack with 32 books in the last slot. The bug only occurs if the book stacks with books in the hopper. If the bug occurs the book gets pulled into the hopper but is still displayed in the bookshelf but you cannot take it out since it was already pulled out by the hopper and you also cannot put a book in that slot. In f3 you can see the info slot_x_occupied is still true. Only after you insert a book into another slot or take another book out of another slot the bookshelf gets updated
Steps/models to reproduce
Plugin and Datapack List
Server Plugins (0):
There are 3 data pack(s) enabled: [vanilla (build-in)], [file/bukkit (world)], [paper (build-in)]
There are no more datapacks available
Paper version
This server is running Paper version 1.21.1-132-ver/1.21.1@b48403b (2024-11-21-T10:14:27Z) (Implementing API version 1.21.1-R0.1-SNAPSHOT)
You are running the latest version
Previous version: 1.21.1-119-7cd4f2c (MC: 1.21.1)
Other
No response
The text was updated successfully, but these errors were encountered: