This can be traced back in ResultSlot class, as under the "remove" method, the parameter p_40173_ is taking both primary and secondary (splitting) values. As seen in line 414 & 415 in AbstractContainerMenu class.
[media]
This is important because the remove method sets the removeCount as the j3 value (and since right click splits the amount, it's halved). The removeCount is later used to trigger the scoreboard achievement , so the scoreboard achievement is not accurate to what's crafted.
(removeCount being set as the min value - which is the split value)
[media]
(line 43 triggers the scoreboard increment)
[media]
I'm pretty sure this is what is happening to the drop action as well because it thinks you're only removing out 1 item count from the slot.
Astero
This can be traced back in ResultSlot class, as under the "remove" method, the parameter p_40173_ is taking both primary and secondary (splitting) values. As seen in line 414 & 415 in AbstractContainerMenu class.
This is important because the remove method sets the removeCount as the j3 value (and since right click splits the amount, it's halved). The removeCount is later used to trigger the scoreboard achievement , so the scoreboard achievement is not accurate to what's crafted.
(removeCount being set as the min value - which is the split value)
(line 43 triggers the scoreboard increment)
I'm pretty sure this is what is happening to the drop action as well because it thinks you're only removing out 1 item count from the slot.