mineflayer-statemachine
mineflayer-statemachine copied to clipboard
Moved dependencies
Moved mineflayer dependencies to devDependencies.
Addresses #173
Note: prismarine-* and vec3 dependencies were also moved since only their types are used; they are never instantiated. Since mineflayer also updates these libraries, statemachine should follow the provided version from mineflayer.
However, these seems slightly worse behavior than simply moving mineflayer and mineflayer-pathfinder, so that's just my personal suggestion.
I've also decided to remove minecraft-data as a dependency and switch to prismarine-registry, again as a devDependency. The previously loaded mcData now requires on bot.registry from prismarine-registry.
To clarifay, if the user want to use "behaviorMoveTo" need to install manually pathfinder & minecrafr-data & mineflayer? https://github.com/PrismarineJS/mineflayer-statemachine/blob/836c8693d9bf9ba66d5c07046b08debe416a0789/src/behaviors/behaviorMoveTo.ts#L4
I'm not sure if that have sense,
But I understand your vision, since on the other hand this repository is not usually updated much, this would help prevent it from becoming obsolete with new pathfinder updates
fails
New PR fails, older one works. Fixing now.
To clarifay, if the user want to use "behaviorMoveTo" need to install manually pathfinder & minecrafr-data & mineflayer?
https://github.com/PrismarineJS/mineflayer-statemachine/blob/836c8693d9bf9ba66d5c07046b08debe416a0789/src/behaviors/behaviorMoveTo.ts#L4
I'm not sure if that have sense,
But I understand your vision, since on the other hand this repository is not usually updated much, this would help prevent it from becoming obsolete with new pathfinder updates
Correct, I believe that was the intended behavior before this PR as well.
I will open a new PR for my more significant changes. I will revert this branch to just the dependency changes.