I realise now that my proposed "fix" results in more load due the nature how the InventoryMoveItemEvent is (probably) used in most plugins: As an inventory move item attempt event. They only check if one inventory can move to another for protection reasons and mostly don't care about the item.

It might be better to revert this event to how it was previously, make it really clear in the documentation that this is just an attempt of a move and start deprecating the getItem method as it doesn't represent all items that could potentially be moved anyways. In the future the calling of the event could then be moved to an earlier part in the move process to avoid calling it for every item it loops over.

It would probably be good to add a new event that only gets fired when an item is actually moved later on when it checked if the target can receive the item. (Currenlty the InventoryMoveItemEvent gets also fired if the target is full and no items are actually moved like if the target is full or the inventory doesn't accept that item type)