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

Mineflayer Python - No Module Error While Requiring Pathfinder #3473

Closed
1 task
SiyahEkran opened this issue Oct 5, 2024 · 2 comments
Closed
1 task

Mineflayer Python - No Module Error While Requiring Pathfinder #3473

SiyahEkran opened this issue Oct 5, 2024 · 2 comments
Labels
possible bug Stage1 just created by someone new to the project, we don't know yet if it deserves an implementation / a f

Comments

@SiyahEkran
Copy link

  • The FAQ doesn't contain a resolution to my issue

Versions

  • mineflayer: 4.20.1
  • server: vanilla/spigot/paper 1.16.5
  • node: 20.18.0

Detailed description of a problem

Everytime i try to require "mineflayer-pathfinder", i get this error: 🌉 Error [ERR_MODULE_NOT_FOUND]: Cannot find package 'mineflayer-pathfinder' imported from C:\Users\umbal\AppData\Local\Programs\Python\Python312\Lib\site-packages\javascript\js\deps.js
But I HAVE the mineflyer-pathfinder and its version is 2.4.5. BTW I am using the python version of mineflayer

What did you try yet?

I tried reinstalling both node and nvm, test it out in another version of minecraft, etc.

Your current code

from javascript import require, On, Once, AsyncTask, once, off
import random, time
mineflayer = require('mineflayer')
pathfinder = require('mineflayer-pathfinder')

Expected behavior

I want this problem to be solved ASAP.

@SiyahEkran SiyahEkran added possible bug Stage1 just created by someone new to the project, we don't know yet if it deserves an implementation / a f labels Oct 5, 2024
@rom1504
Copy link
Member

rom1504 commented Oct 6, 2024 via email

@SiyahEkran
Copy link
Author

SiyahEkran commented Oct 6, 2024

yep i've installed it already and the problem just got fixed after a reboot

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
possible bug Stage1 just created by someone new to the project, we don't know yet if it deserves an implementation / a f
Projects
None yet
Development

No branches or pull requests

2 participants