Finally actually fixed decrementing bug

VERY lengthy explanation: it would EITHER decrement the inputs one too
many times when shift clicking or not decrement the inputs at all if you
normally remove the output,the way i had it set up, it couldnt tell the
difference between the two really
OmegaJak: and so whenever i made a condition trying to discern one from
the other keeping it from going from the client to the server saying
"set the output to null and then do whatever else you see fit"
OmegaJak: it would ruin the other
OmegaJak: and the heart of the problem lay in that thing being called
telling the server to do its thing
OmegaJak: because the server would already be doing its thing properly
for whatever reason when you shift clicked, but not when you simply
pulled it out, which is why i set up that thing to go from client to
server
OmegaJak: so when you shift clicked the server would be doing its thing
properly, but then on top of that, because i couldnt really tell shift
clicking from normal extracting, the client would call the method that
tells the server to decrement the inputs when it sets the output to null
OmegaJak: so it would do the normal server decrementing + 1 from the
client
Solution: i set up a boolean that was set to true when the method was
called for when you shift click
OmegaJak: and when that boolean was true, it would make the condition
allowing the message to go to the server to fail
OmegaJak: and then what i was doing, was i would set that back to false
right after the stack was set
OmegaJak: which didnt work, because the method was called multiple times
on both server and client for each shift click
OmegaJak: i did not know this until like half an hour ago
OmegaJak: and it was being called on each side once to set the output to
null, and then once for each decrement of the inputs
OmegaJak: meaning that if you have four stacks to be compacted, it would
be called 36 times for the inputs and once to set the output to null
OmegaJak: unless that method for going to the server was called, in
which case it would output 4 but decrement each stack five times
OmegaJak: so i set up a counter that would increase until it equalled
(the limiting number of inputs * 9), and once it got there, then, and
only then, would it set that boolean that disabled the message to false,
allowing that message to be sent for the future actions