returns different value for clicking one inventory in the first and last rows, if the top inventory is a Dropper inventory typed one. I guess the problem is that the top inventory is not a Chest typed and the index checking of which inventory contains the given clicked RawIndex is miscalculated. Depending on the .getClickedInventory(), it returns the top inventory for some slots of the botton inventory's top slots.
The right result, the second/bottom inventory is returned only from the RawSlot with value of 27, the thirt row of shown PlayerInventory, the 2nd line from the bottom of InventoryView, right above the toolbar row. ---- with using a Dropper inventory on the top. Different inventory, like a HopperInventory on the top may return different results.
**I made a message showing inside an InventoryClickEvent listener, to show me in chat which Inventory object is returned for .getClickedInventory(), represented by their hashCode() in HEX form (the fastest way I know to identify objects runtime easily). It can be seen, that for the slot from the 2nd row (the upper one) returns an Inventory with #1b6c7f2, but the slot from the third row of the PlayerInventory returns an inventory with #129da8c on click. The right results would be the matching of the two object id's, because the two slots are in the same inventory (not inventory-view, inventory), but they do differ. It is checked via == (reference equal check), that the object returned for the upper slot matches the inventory object for the TopInventory of the View (as if it would be still the top inventory, while it is not already, and it seems like the border between the top and the botton inventory is 2 rows downer, than it should be).
The problem, I guess:
I think the Inventory returned is calculated from the clicked RawIndex, and that calculation must be fixed. May I guessed wrong, this is just a tip.