Kandarim wrote:the mapping is done correctly, but when you try to put it in a slot that has no mapping, it simply sends the drop command for that particular slot -- I simply never encountered such a wide inventory in my testing, I think.
I remember the layout of your inventory changed at some point, the point where it started to add columns to the right after a certain row/column-ratio was exceeded (a behaviour which I btw never liked)...
Anyways, if there is a slot without a mapping, then it's not done correctly!
As you seem to know what the problem is and how the slots are handled server sided, why not just put in a check that redirects item placement into invalid slots to valid slots (at the end of the inventory)? (As an interim solution)
Then you'd only need to remember which (server side) slot it went to, and map that to the actual (client side) slot that the user clicked, easy as that?