-
-
Notifications
You must be signed in to change notification settings - Fork 953
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
Support 1.20.4 #3310
Support 1.20.4 #3310
Conversation
New and removed dependencies detected. Learn more about Socket for GitHub ↗︎
🚮 Removed packages: npm/[email protected] |
There was an issue with chat command params fixed with PrismarineJS/minecraft-data#850 Error: Error: crafting: non craftingTable used as craftingTable: minecraft:enchantment
at EventEmitter.craft (lib/plugins/craft.js:32:13)
at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
at async /workspaces/mineflayer/test/externalTests/crafting.js:57:3 This might be fixed by @wgaylord's recipes PR in PrismarineJS/minecraft-data#843 and playerlist playerlist header
{
header: { type: 'end', value: undefined },
footer: { type: 'end', value: undefined }
} because tag.type end isn't handled, just fixed in prismarine-chat I added some extra context to the error messages and swapped Node.js once() with a mineflayer one with a default 20s timeout (only place that needed unlimited time seems to be bot.flyTo()) to make errors more obvious. Seems that flakiness in some of the tests seems to be caused by windows not opening: https://github.com/PrismarineJS/mineflayer/actions/runs/7999230618/job/21846700577?pr=3310 1) mineflayer_external 1.13.2v
useChests:
Error: Event windowOpen did not fire within timeout of 20000ms
at onceWithCleanup (lib/promise_utils.js:62:26)
at once (lib/promise_utils.js:76:10)
at EventEmitter.openBlock (lib/plugins/inventory.js:366:28)
at EventEmitter.openContainer (lib/plugins/chest.js:19:25)
at withdrawBones (test/externalTests/useChests.js:54:29)
at /home/runner/work/mineflayer/mineflayer/test/externalTests/useChests.js:119:9
at process.processTicksAndRejections (node:internal/process/task_queues:95:5) |
After a bit of poking around this looks more like an issue in https://github.com/PrismarineJS/prismarine-windows/blob/master/index.js then with the recipes stuff itself. (I didn't actually read the error well when I suggested that my PR to fix the recipes may fix it) Looks like for some reason it thinks it opened an enchantment table instead of a crafting table. Looking at the src looks like the crafter screen was inserted into the middle of the list for some reason, we may want to look into adding a json file (or edit the existing windows one) to include the network ID of the screen / window. |
This should fix the crafting issue. PrismarineJS/prismarine-windows#105 Probably want to add a new inventory related feature now that I think about it. |
How can I help contribute and fix this error? |
lib/plugins/chat.js
Outdated
|
||
bot._client.on('playerChat', (data) => { | ||
console.log('playerChat') |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
please remove
lib/plugins/chat.js
Outdated
@@ -107,8 +107,12 @@ function inject (bot, options) { | |||
}) | |||
|
|||
addDefaultPatterns() | |||
bot._client.on('player_chat', (msg) => console.dir(msg, { depth: null })) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
debug code
hoorah when though? |
/makerelease |
No description provided.