Tal

This is now fully functional - feel free to review this. (although, I'm not exactly done with code cleanup yet, will do that ASAP!)

Yeah I do agree, I also think other fields such as `transparent` or `empty` could be exported, along with `newBreakInfo`, `newSmeltInfo`, etc.

I am pretty positive this is an issue with Dragonfly - using a custom provider and setting a direction seems to work fine consistently.

What exactly do you mean by that?

The issue here is the fact that there is no boundary between "definite drops" and "survival drops", both are grouped into the same drops portion of `BreakInfo`.

I agree.

I agree, since there may want to be player-specific functionality. (for example, player one can trample crops but player two cannot)

Any update on this?

As Sander suggested on Discord, a good alternative is probably some sort of `entity.Mount(some Entity, on Entity)` function.

Would it be best to add a function for something like this to movement computer? It's pretty specific functionality (only occurs in experience orbs and items from my knowledge) but...