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
Some items are not appearing in the slots - (Possibly resolved) #3354
Comments
So, I did a little tinkering here and there, and I was analyzing the packets being sent directly and I ended up realizing that the server is sending as expected, so much so that when I pull it directly using this method: bot._client.on('window_items', (window) => {
console.log(window)
}) it is possible to see the items that when pulled by the "Window" return of event "WindowOpen", appear only as null |
This is not valid javascript: bot.activateItem(offHand=false) What this is doing is declaring an I don't understand what you mean here: "However, the slots in the window returned by the Event are only those of the inventories and not of the chest itself." Where is the expected output coming from? Are you saying it's returning the bot inventory or one half of the chest? You can log a full object without truncation by using |
As can be seen in the previous messages and prints, whenever the bot interacts with the "Compass" item, it opens a Windows, as if it were a Chest, but, when I receive the event using the WindowOpen, it only shows the items that are present in the inventory and not those that should be in the "Chest" But if I receive it directly, using the "window_items" event from minecraft-protocol, it already shows these items as can be seen below |
Versions
Detailed description of a problem
Whenever the compass is right-clicked, it opens a custom window, similar to opening a chest. However, the slots in the window returned by the Event are only those of the inventories and not of the chest itself.
What did you try yet?
Your current code
Expected behavior
Expected Output =>
Output provided by the event =>
The text was updated successfully, but these errors were encountered: