Issue type:

• 🐛 Bug

Short description:

In 1.18, 'export item predicate' aspect of the item exporter does not appear to be slot independent (at least for the predicate given below).
Also occurs in 1.19, but does not on and 1.20.

Steps to reproduce the problem:

1. setup as in the picture above
2. put an item predicate in the exporter, such as apply(relationalEquals, variableCardItem) or apply(listContains, itemListWithVariableCardItem) - note that the item stack size is respected by these, so they will only return true for stacks with a size of 1

Behaviour:

Placing 1 stack of 2 items in the left chest:

Behaviour: no items are transferred (correct)
Expected behaviour: no items are transferred

Placing 1 stack of 1 item in the left chest:

Behaviour: items are transferred (correct)
Expected behaviour: items are transferred

Placing 2 stacks of 1 item in the left chest:

Behaviour: no items are transferred (incorrect)
Expected behaviour: all items are transferred

i.e.: works correctly, unless there are multiple stacks that should be exported

Versions:

• Minecraft: 1.18.2
• Forge: 40.1.0

Log file:

N/A

Thanks for reporting!

Also occurs in 1.19, but does not on 1.20.

Huh, that's surprising. AFAIK, nothing has changed between these versions related to item transfer or operator handling.

Yeah, I went through the diff for 1.18 vs 1.20 for InTu and nothing seemed relevant. It might be a change in InDy or CyclopsCore. Have you been able to reproduce this for yourself on 1.18 vs 1.20?

Hmm, nevermind I guess; I just loaded the 1.20 test world back up for something else and it's not working there either - I'm not sure why I thought it was before but I'll put it down to misremembering rather than it actually happening and being inconsistent, at least until I see it actually happen (again?).

Might be relevant, or a separate issue; in both 1.18 and 1.20, if you specify a transfer rate and 'check stack size', then exporters work as expected (tested using the 'export item' and 'export item list' aspects). However, if you instead use an importer and interface, it seems to operate 'slot-wise' - with a transfer rate of 48 and 3 stacks of 64 initially in the chest, it transfers three lots of 48 leaving behind 3 stacks of 16, rather than transferring a fourth lot of 48 as well.