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

bot falls out and dies after entering server #169

Closed
spearsheep opened this issue Sep 7, 2024 · 2 comments
Closed

bot falls out and dies after entering server #169

spearsheep opened this issue Sep 7, 2024 · 2 comments
Labels

Comments

@spearsheep
Copy link

Before submitting an issue, make sure you read the FAQ.md

Briefly describe your issue

so I followed the setup and downloaded all the mod packs, manually compiled the better respawn mod at branch 1.19. However, after I enter the server with voyager.decompose_task(task=task), I would immediately encouter the following error continously:
Mineflayer process has exited, restarting
Subprocess mineflayer started with PID 36748.

So I followed one of the posts and commented out the following lines in index.js:
const collectBlock = require("mineflayer-collectblock").plugin;
const minecraftHawkEye = require("minecrafthawkeye");
I also uncommented the following lines:
// bot.collectBlock.movements.digCost = 0;
// bot.collectBlock.movements.placeCost = 0;

After this, I start to encounter the new error that directly after the bot enters it fells out of the world and dies. But the task decomposition and inference continues until the error: list out of index to some sort of events.

Please provide your python, nodejs, Minecraft, and Fabric versions here

Python 3.10.14, Minecraft 1.19, nodejs v20.14.0,

better-respawn-fabric-1.19-2.0.0.jar
completeconfig-2.0.0.jar
fabric-api-0.58.0+1.19.jar
modmenu-4.0.4.jar
Multiplayer-Server-Pause-1.19-Fabric-1.1.0.ja

Copy link

github-actions bot commented Oct 8, 2024

This issue is stale because it has been open for 30 days with no activity.

@github-actions github-actions bot added the stale label Oct 8, 2024
Copy link

This issue was closed because it has been inactive for 14 days since being marked as stale.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant