You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Mineflayer does use bot.world.raycast(eyePosition, viewDirection, maxDistance, matcher) to get block which bot is looking in function bloctAtCursor. The problem is raycaster doesnt seem to get right block is target is lever. This is maybe the case with other non-full blocks, i haven't tested them. Full blocks work very well.
It would be nice to get way to raycast also non-full blocks.
The text was updated successfully, but these errors were encountered:
DatArnoGuy
changed the title
World.raycast through mineflayer doest return lever but block behind it
World.raycast through mineflayer doesn't return lever but block behind it
Oct 31, 2021
This is a data issue. There is 2 types of shapes in minecraft: interaction and physic, we only have the second one in mcData so that is what we use for both, but as you noticed there are some differences. The fix would be to extract the interaction shapes and expose them in mcData. There is an issue about this somewhere, but I can't find it.
Mineflayer does use bot.world.raycast(eyePosition, viewDirection, maxDistance, matcher) to get block which bot is looking in function bloctAtCursor. The problem is raycaster doesnt seem to get right block is target is lever. This is maybe the case with other non-full blocks, i haven't tested them. Full blocks work very well.
It would be nice to get way to raycast also non-full blocks.
The text was updated successfully, but these errors were encountered: