-
Notifications
You must be signed in to change notification settings - Fork 60
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
implement findBlock here #154
Comments
find block would be better implemented at the world level, since the iterators can cross chunks boundaries (and are already packaged in pworld) |
We really need both. Chunks need to be allowed to search themselves (as they best know how, based on palette consideration). Then those facilities can be used by pris-world to do general purpose search |
Is anything blocking here or just waiting for an implementation? |
PrismarineJS/mineflayer#334 (comment) is blocking because mineflayer findBlock relies on mineflayer blockAt which has features (eg block entities) that pchunk getBlock do not |
there are some version handling things in https://github.com/PrismarineJS/mineflayer/blob/04665d1c757a9eaf6433cabd3b2fa62d39d88ad5/lib/plugins/blocks.js#L51 with signs, not sure how this could be implemented inside pchunk since it seems like a mineflayer level abstraction, as pchunk needs to be able to load block entities and also dump them back. So maybe it would make sense to add some form of block entity abstraction on the mineflayer side and keep the block entity data pure on the pchunk side (as in we just |
#134 (comment) we have a plan for block entities there, we want to move them to pchunk to be able to move the state from mineflayer to pworld/pchunk |
will be possible when PrismarineJS/mineflayer#334 is done
will enable PrismarineJS/prismarine-world#89
The text was updated successfully, but these errors were encountered: