General improvements to mineflayer-navigate / mineflayer-scaffold

[rom1504]

mineflayer-navigate and mineflayer-scaffold are nice but not quite perfect :

• integrate the time it takes to mine or jump/build into the length of an edge
• options about what blocks it can use, about what block it can dig
• area to avoid

This issue tracks general problems and ideas to improve it.

[demipixel]

A) Normal navigate options
B) Mine? True or False
C) Tools it has to use (take into account durability and breaking?)
D) Blocks it has to use to build with
E) Can mined blocks be added to D?
F) List of block types it shouldn't mine
G) List of specific blocks it shouldn't mine
ANd maybe some otherstuff
H) Areas the bot should avoid rather than specific blocks
I was thinking maybe G could be replaced by H and if you want specific blocks you just make them 1x1 areas on H
I) In addition to H, blacklisting, it would be cool to whitelist areas as well, places the bot can ONLY mine.

[rom1504]

also related to rom1504/rbot#26

[rom1504]

some other ideas :

• post optimization to handle diagonals (and non 90° angles)
• dynamic path recomputation (see https://github.com/roblabla/node-lpastar)
• new bounding boxes (see Handle new kinds of bounding boxes mineflayer#228)
• water