-
-
Notifications
You must be signed in to change notification settings - Fork 865
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
1.9 support #449
Comments
Is somebody actively working on this? I'm currently trying to a proof of concept working and it would be sad to redo the work somebody else already did :) |
Lots of work has gone into this in various fork, but nothing was ever finalized. The biggest problem was handling chunks is a real pain now. Having a version of https://github.com/PrismarineJS/prismarine-chunk that works on 1.9 would go a long way to making mineflayer working on 1.9. |
I don't quite get how |
Mineflayer currently use its own 1.8 chunk implementation.
We need a 1.9 chunk implementation to update it.
It makes more sense to implement that independently from mineflayer which
is why it has been started in prismarine-chunk.
…On Sun, Dec 11, 2016, 23:43 ooxi ***@***.***> wrote:
I don't quite get how prismarine-chunk relates to mineflayer? I see
package.json lists prismarine-chunk as a dependency but nowhere inside
the mineflayer source I see a require('prismarine-chunk') (besides the
tests).
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#449 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/ACPN_qrZ1Mt-tfzrIGDX7uXEy3eX9Nxjks5rHHyBgaJpZM4J6YE1>
.
|
done |
We plan to support 1.9 once we get 1.9 chunk support (see PrismarineJS/prismarine-chunk#19)
Duplicate issues :
The text was updated successfully, but these errors were encountered: