[SMP] Extraction Module sending whole stack when it doesn't need to resulting in lost items

[rux616]

I have an ore doubling machine on my server that uses relocators as its method of transporting things around and I have been noticing that I've only been getting roughly half the output from it that I should be.

Here is the layout of the machine:

It has an input chest on the far left, connecting via two relocators to four IndustrialCraft2 macerators and to a buffer chest in the center, connecting via two more relocators to four IndustrialCraft2 electric furnaces, with the output chest on the right.

The module setup:

• Extraction Module that is pulling from the input chest (left)
  • Delay: Two seconds
  • Active: Always
  • Maximum Extracted Stack Size: 64
• Filter Module that is connected to buffer chest (center)
  • Whitelist: All Crushed Ores
• Extraction Module that is pulling from the buffer chest (center)
  • Delay: Two seconds
  • Active: Always
  • Maximum Extracted Stack Size; 64
• Filter Module that is connected to output chest (right)
  • Whitelist: All Ingots

Now, with these settings, once a macerator is done crushing the ore and outputs to the relocator network, the extraction module attached to the input chest is supposed to send ONE ore to replace the one that was just consumed. Instead it sends an entire stack which just vanishes into the ether once it gets to the macerator (after replenishing the one missing ore in the stack). I have confirmed that this only happens in multiplayer by replicating this setup exactly in single player and watching the extraction module only sending one ore to replace the one used.

The workaround for this is to set the max extracted stack size to one, but it would be nice if we could get a bug fix for this, especially since the default max stack size is 64.

[Dynious]

Thanks for the awesome bug reports! Reports like this really help me to find issues more quickly! I'm (hopefully) fixing this now! Sorry for the wait, I've been quite sick the last couple of weeks :(

[Dynious]

Thanks again! 1.0.6c will have a fix for this issue!