Issue description:

Given a cardboard box placed into an AE system, unusual behavior occurs. To see an example of this behavior and some discussion related to the issue, refer to the issue on AE2's tracker. Also going to link in AS 1.9 megathread.

Steps to reproduce:

1. Place a cardboard box with a vanilla blaze spawner into an AE2 system, with Astral Sorcery installed.
2. Try to remove the box

Version (make sure you are on the latest version before reporting):

Forge: 2705
Mekanism: 9.4.13.349
Other relevant version: MC: 1.12.2, AS 1.9.2 (fscan confirmed on AS 1.9.3), AE2 rv6-alpha-1
No log relevant

a temporary fix i found is to extract the cardboard boxes is use an export bus a fuzzy card with a cardboard box (box has to have a block in it)

Based on fscan's analysis that's something for AS to fix. A capability should not depend solely on getMaxStacksize

It's perfectly valid behaviour as far as I'm aware for getMaxStackSize to change based on nbt as far as I know.

The javadoc states This is a ItemStack (and thus NBT) sensitive version of Item.getItemStackLimit()

Nbt changes == you cannot make any prior assumptions

I'm not sure its valid to change a Item property after the creation of the ItemStack. An easy fix on your side would be just to use the existing meta for it.

a temporary fix i found is to extract the cardboard boxes is use an export bus a fuzzy card with a cardboard box (box has to have a block in it)

I had this same issue, and your workaround helped. Thank you :)